Doppler and Vercel. Better Together.

Vercel’s environment variable management UI is fine for standard CRUD operations. What’s missing are the features needed by growing development teams such as Git-style activity log history with rollback support, greater security with user access controls at the project and environment level, SAML SSO, secret rotation reminders, and more.

Environment variables are the best way to configure Node.js applications and should be used as much as possible because they keep secrets out of source code. They also allow you to have complete control over how your application is configured in every environment.

Once an environment variable has been added via Doppler or the Vercel UI, you can then access that value using the Node.js `process.env` object.

Check out our tutorial on configuring Node.js applications using environment variables at https://blog.doppler.com/environment-variables-node-js.

Doppler is designed to sync secrets to every environment, including local development. So goodbye .env files!

Ensure a secrets sync is configured for your Development environment in Doppler, then use the vercel dev command to inject the synced secrets from Vercel into your application locally.

Doppler supports syncing environment variables to any number of Vercel teams, even on our free developer plan.

Project and workplace admins can configure integration connections from Doppler to Vercel which when combined with user access controls on our Team plan, allow access to be tightly controlled by specifying which team members can access specific projects and environments within those projects.

The Vercel integration is free to use and always will be.

Doppler is free for up to 5 accounts on the developer plan an no credit card is required when signing up.

You can also start a free 7 day trial on our Team plan to unlock features such as user access controls, SAML SSO, and Slack activity notifications.

For an Enterprise trial, get in touch.

‍

Absolutely! As enterprise organizations often have very specific requirements and workflows for managing secrets and environment variables at scale, we’d love for you to book a time to chat with us so we can give you a tailored plan for getting started. Just head to https://doppler.webflow.io/demo to schedule a time.

Usually, the problem will be that the environment variable hasn’t been defined for the environment in which your code is running.

For example, you’ve defined a `STRIPE_API_KEY` in the Preview environment, but not Production. If you’re still stuck and on our Developer plan, head over to https://community.doppler.com where you’ll likely find one of our Support Engineers or Developer Advocates ready to answer your questions.

If you’re on the Team plan, our in-product support is the fastest way to get your issue resolved.