Skip to main content

Vercel

Connect an Envshed project to a Vercel project once. Every deploy pulls fresh secrets from Envshed — no manual environment-variable updates in the Vercel dashboard, no drift between staging and production.

On the roadmap — target Q3 2026

The native Vercel integration ships in Q3 2026. Until then, the workaround below covers the same use case using the CLI.

How it will work​

  • Connect once — install the Envshed app from the Vercel marketplace and pick which Envshed environment maps to each Vercel target (development, preview, production).
  • Sync on every deploy — Envshed pushes the current values into Vercel before each build, so the Vercel runtime reads them as native env vars.
  • One source of truth — rotate a secret in Envshed, redeploy, done. No more "did anyone update Vercel?" in Slack.
  • Audit trail intact — every push is logged in Envshed, so you keep one timeline of who changed what across both systems.

Workaround today​

You can already deploy to Vercel with secrets sourced from Envshed using a service token and the CLI. Two patterns work today.

Option 1 — envshed run in the build command​

Wrap the Vercel build command with envshed run so secrets exist in the build environment without ever being copied into the Vercel dashboard.

In vercel.json:

{
  "buildCommand": "envshed run -e production -- pnpm build"
}

Add a single ENVSHED_TOKEN env var to the Vercel project (use a service token with read access to the target environment). The CLI uses it to fetch every other secret on each build.

Option 2 — script that calls the REST API​

If you would rather not install the CLI on the Vercel build image, hit the REST API directly from a build script and write the values to .env.production.local before next build. See the pull command and the underlying API for the exact shape.

Either pattern keeps secrets out of the Vercel UI and gives you the same rotate-once behavior the native integration will have.

Want this sooner?​

The native integration is sequenced behind a couple of other items on the public roadmap. If Vercel is the integration that would unblock you, email hello@envshed.com with a one-liner about your setup — every reply moves it up the queue.