Project features

Environment variables & secrets

Set config and secrets per project. They're injected at build and runtime, encrypted at rest, masked in the UI, and never returned in plaintext over the API.

Set variables

Add and edit variables in the project's Environment tab, or push a local .env from the CLI:

shell

orizon env push .env       # set variables from a file
orizon env pull            # print the current NAME=VALUE pairs

Or over the API (replaces the full set and redeploys):

shell

curl -X PUT https://api.orizon.ng/api/v1/projects/proj_123/env \
  -H "Authorization: Bearer orz_pk_your_key" \
  -H "Content-Type: application/json" \
  -d '{"variables":{"NODE_ENV":"production","DATABASE_URL":"..."}}'

Changes trigger a redeployUpdating variables kicks off a new deployment so the new values take effect in your running app.

The environment variables vault

A global Environment Variables page lets you browse and search variables across every project at once (values masked) — useful for auditing which projects use a given key or rotating a shared secret.

Secure .env export

You can export a project's full .envwhen you need it — gated behind an email one-time-code re-authentication, so a stale session can't exfiltrate secrets. Values are decrypted only for that authorised export.

Connecting databases

Store connection strings as env vars.

Deployments & rollback

How env changes roll out.