Docs/Overview
Docs/Environment Variables & Secrets

Environment Variables & Secrets

Enterprise secret management for serverless applications. Sensitive credentials such as database URLs, API tokens, and encryption keys are encrypted at rest with AES-256 GCM in Secret Manager and mounted ephemerally in container memory without ever touching build logs or public source control.

System-Reserved Environment Variables

Exovon automatically injects standard platform variables into your container runtime environment:

VariableDefault ValueDescription
PORT8080The port your server must bind to for Edge Router ingress and health checks.
DATABASE_URLpostgres://...Automatically mounted when an ExoStore database cluster is provisioned.
EXOVON_REGIONasia-south1The geographic cloud region where your container instance executes (Mumbai, India).
EXOVON_DEPLOY_IDdpl_9a2f1b...Unique immutable deployment identifier for observability and audit tracking.
NODE_ENVproductionDefaults to production in live deployments to trigger framework optimizations.

Runtime Secrets vs. Build-Time Public Variables

Understanding how variables are evaluated prevents inadvertent client-side credential exposure:

Server Runtime Secrets

Variables without public prefixes (e.g. STRIPE_SECRET_KEY, DATABASE_URL, JWT_SECRET) are stored in Secret Manager and decrypted into memory (process.env) at launch.

Instant Hot Restart: Updating runtime secrets spins up fresh container instances in <2s without triggering a full Git recompilation.

Build-Time Public Variables

Variables with framework prefixes are baked directly into client-side JavaScript bundles during compilation:

Next.js: NEXT_PUBLIC_API_URL
Vite: VITE_AUTH_DOMAIN
Astro: PUBLIC_PROJECT_ID

Because public variables are embedded in client bundles, changing them initiates a new build pass to rebuild static assets.

Managing Secrets via CLI & Dashboard

Manage your project secrets locally from terminal or through the web dashboard:

terminal
# 1. Add or update a production secret (encrypted immediately)
npx exovon env add STRIPE_SECRET_KEY "sk_live_..." --project my-app

# 2. List all configured keys (values remain securely masked)
npx exovon env ls --project my-app

# 3. Pull production variables into your local development environment
npx exovon env pull .env.local --project my-app

# 4. Remove a secret
npx exovon env rm OLD_TOKEN --project my-app

Frequently Asked Questions

Are environment secrets visible in build logs?

No. Exovon automatically redacts all configured variable values from stdout and stderr logs during both container compilation and runtime execution to eliminate credential leaks.

How many environment variables can I store?

Variable quotas are structured by plan: Hobby includes up to 6 variables per project, Starter includes 15, Pro includes 25, and Heavy includes unlimited variables with dedicated Customer-Managed Encryption Keys (CMEK).

Was this documentation page helpful?