Environment variables
Store API keys, tokens, and secrets in Rocket.new environment variables so credentials stay out of your source code and version history.
Environment variables let you store API keys, database URLs, and other secrets without hardcoding them in your app. Rocket keeps separate values for staging (while you build) and production (when you launch).
The Environment settings panel is only available for web build tasks, which use a .env file. For mobile tasks, variables are stored in env.json - update them directly in that file or inside the connector's value field.
Open Environment settings
Click your task name in the top-left corner of the editor, then click Settings.


In the Settings sidebar under Task, click Environment. The panel opens showing your existing variables across Staging and Production tabs.


Staging and Production
The Environment panel has two tabs:
- Staging - values used while you are building and testing inside Rocket.
- Production - values used when your app is live and publicly launched.
Make sure both tabs are filled in so your app behaves correctly in each environment.
If you set a value directly in your code or in a connector's value field instead of using this panel, Rocket treats it as a staging value by default.
Add a variable
New environment variables are added through your .env file in code, not through the Settings UI.
Click Code in the editor toolbar to open the file explorer.
Use placeholder values (like your-key-here) in code files. Set your real secrets only in the Environment panel. Never commit actual keys to a repository.
Open .env at the root of your project and add your variable:
OPENAI_API_KEY=your-key-here
NEXT_PUBLIC_SUPABASE_URL=https://your-project.supabase.coSave the file. The variable is now available to your app and will appear in the Environment panel under the relevant tab.
For mobile tasks, variables are stored in env.json instead. Open it in the Code tab and add your key-value pairs there directly.
Edit an existing variable
To update the value of an existing variable, open the Environment panel (Settings > Environment) and click the edit icon on the right side of any variable row. Make your change and save.
Changes take effect on the next build or generation in that environment.
Use variables in your app
Reference variables in server-side code using standard patterns:
process.env.OPENAI_API_KEY
process.env.NEXT_PUBLIC_SUPABASE_URLYou can also ask Rocket to wire them up directly in chat:
Use the OPENAI_API_KEY environment variable to set up the AI chat feature.Common variables
Variables prefixed with NEXT_PUBLIC_ are exposed to the browser (client side). All others stay server-side only. Never put secrets in NEXT_PUBLIC_ variables.
Client-side variables (safe to expose)
These variables are designed to be public and are safe to prefix with NEXT_PUBLIC_:
| Variable | Service | Why it's safe |
|---|---|---|
NEXT_PUBLIC_SUPABASE_URL | Supabase | Public project URL; security relies on row-level policies |
NEXT_PUBLIC_SUPABASE_ANON_KEY | Supabase | Anonymous key with limited permissions; security relies on row-level policies |
NEXT_PUBLIC_GA_MEASUREMENT_ID | Google Analytics | Measurement ID is meant to be public |
NEXT_PUBLIC_ADSENSE_ID | Google AdSense | Publisher ID is meant to be public |
Server-side variables (keep secret)
These variables contain sensitive credentials and should never have the NEXT_PUBLIC_ prefix:
| Variable | Service | Why it's secret |
|---|---|---|
STRIPE_SECRET_KEY | Stripe | Can charge cards and access all account data |
OPENAI_API_KEY | OpenAI | Can make API calls and incur charges |
GEMINI_API_KEY | Google Gemini | Can make API calls and incur charges |
ANTHROPIC_API_KEY | Anthropic | Can make API calls and incur charges |
RESEND_API_KEY | Resend | Can send emails on your behalf |
What's next?
APIs
Import and integrate API endpoints that use your environment variables.
Connectors
Connect services like Supabase, Stripe, and OpenAI with dedicated integrations.
Custom code
Inject scripts and styles that reference your environment configuration.
Chat interface
Ask Rocket to use your variables when building features.

