Forgeon Docs

Documentation, guides, and patterns to help you build on Forgeon — from your first deploy to running serious infrastructure.

Environments

How prod, uat, qa, staging, dev, and preview behave and how env vars map to each.

Last updated: 2026-03-17

Forgeon uses environment scopes to separate deploys, domains, and configuration. Each environment is isolated by design.

Environment settings

Default environments

prod — live customer traffic
uat — stakeholder acceptance testing
qa — dedicated test environment
staging — pre‑prod validation
dev — internal development
preview — branch/PR previews

Environment variables

Each environment has its own env set:

prod env vars are not shared with preview
preview can have minimal secrets for safety

Scale‑to‑zero

Environments can scale to zero after inactivity. Forgeon shows:

Warm vs cold state
Last request time
Scale‑to‑zero timeout

Environment policy recommendation

preview: fast iteration, minimal secrets.
staging: production-like config and test data shape.
prod: strict change control and full monitoring.

Troubleshooting

Deploy fails with missing envs

Add env vars for the selected environment before deploy

Preview works, prod fails

Ensure prod has its own env vars and domain mapping

Project appears offline but URL still works

Check status source (runtime vs edge render state) and latest runtime heartbeat.