For Vercel Deployments

Secrets that don't require redeployment

Vercel environment variables are baked into your build. When you need to rotate a key, you redeploy. With Kevorax, you update once and all deployments fetch the new value instantly.

The Vercel environment variable workflow

1

Add STRIPE_SECRET_KEY to Vercel project settings

2

Variable is baked into the build at deploy time

3

Stripe says you need to rotate the key

4

Update in Vercel dashboard → trigger redeploy → wait for build → hope you didn't break anything

The Kevorax workflow

1

Add KEVORAX_TOKEN to Vercel (one time, never changes)

2

App fetches STRIPE_SECRET_KEY at runtime from Kevorax

3

Need to rotate? Update in Kevorax

4

All deployments instantly get the new value. No rebuild.

// Your Vercel function
export default async function handler(req, res) {
  // Fetch fresh on every request
  const secretRes = await fetch(
    'https://app.kevorax.com/api/runtime/secrets/STRIPE_SECRET_KEY',
    { headers: { 'Authorization': `Bearer ${process.env.KEVORAX_TOKEN}` } }
  );
  const { value: stripeKey } = (await secretRes.json()).data;
  
  const stripe = new Stripe(stripeKey);
  // Now using the latest key, always
}

Why Vercel developers use Kevorax

Instant rotation

Update a secret, all deployments see the new value immediately. No waiting for builds.

One source of truth

Stop copying the same Stripe key to 5 different Vercel projects. Store once, fetch everywhere.

Preview deployments work

Same project token works across production, preview, and development. No environment-specific configuration.

Edge-compatible

Plain HTTP fetch works in Vercel Edge Functions, Serverless Functions, and Edge Middleware.

Stop redeploying to rotate secrets

$5/month flat. 7-day free trial. No credit card required.

Start Free Trial