Environment variables

Add project-specific settings (API key, feature flag, third-party connection info) as environment variables — they're injected into the container as runtime env on your next deploy.

How to add one

Open your project in the dashboard and switch to the Env tab. Fill in the "Key" and "Value" fields; for multiple variables, add a new row with + Add row, then click Save. What you type is masked by default; use Show values to temporarily see plain text while typing (only for what you're currently typing — you can never see a saved value again afterward, see below).

If you save an existing key again, it's overwritten (upsert) — there's no separate "update" step.

Write-only: values aren't shown back

Values are stored encrypted with AES-256 in the database, and no API endpoint ever returns them decrypted. In the list of saved variables, only the key name and last-updated time are shown. To change a value, save the key again with a new value — there's no "view previous value" option.

This is a pattern used by many deploy platforms (write-only secret) — the goal is to prevent a value from accidentally appearing via screen sharing, logs, or browser history.

Reserved keys

You can't set the following keys by hand — the request is rejected if you try to save them:

PORT, HOSTNAME — managed by the container runtime.
DATABASE_URL, REDIS_URL — if your project has a managed database attached, they're injected automatically at deploy time.

Redeploy for the change to take effect

New or updated env variables do NOT affect the currently running deploy — you need to redeploy your project for them to take effect (see Deploy).

Right now you can only manage env variables from the dashboard — there's no env command in the CLI.