Environment variables

Environment variables are injected into your builds and running app. They're encrypted at rest — Vorynza only decrypts a value when you explicitly reveal, copy, or export it.

Adding a variable

From your app's Environment tab, enter a key and value and choose a target:

Keys must be valid identifiers: letters, numbers, and underscores, starting with a letter or underscore (API_KEY, DATABASE_URL, not api-key).

Viewing and copying values

Values are masked by default. Click the eye icon on a row to reveal it, or the copy icon to copy it directly — copying doesn't require revealing it on screen first. Show values in the toolbar reveals every row at once.

Editing a value

Click the pencil icon on a row to edit it in place. This updates the same variable (same key and target) — to move a value to a different target, delete it and re-add it with the new target.

Importing from a .env file

Click Import, then either paste the contents of a .env file or upload one directly. Vorynza parses it and shows a preview before anything is saved:

• Keys already set for the target you choose are flagged and will be overwritten.
• New keys are added.
• Invalid lines (missing =, invalid variable names) are skipped and listed so you can fix your file if needed.

Choose which target the whole batch applies to, then confirm the import.

Exporting

Click Export to download every variable as a .env file, with real values decrypted into the file. Treat the downloaded file like any other secret — Vorynza doesn't keep a copy of the export itself.

When changes take effect

Setting or changing a variable does not restart or redeploy your app automatically. Trigger a new deployment (push a commit, or redeploy manually) for the updated values to be used — this matters especially for Next.js's NEXT_PUBLIC_* and Vite's VITE_* variables, which are baked into your build output at build time.