Stage Environments

Stage gives you an isolated copy of Production to test updates, customizations, or restores before touching your live system.

Why use Stage

Validate an ERP update before applying it to Production
Test custom modules or configuration changes safely
Inspect an old backup in isolation with --restore-as-stage
Train users without affecting live data

Problems in Stage do not take down Production.

How Stage is isolated

Each Stage has:

Its own runtime containers
Its own database
Its own filestore (attachments)
Its own hostname (for example stage.example.com)
Resource limits appropriate to your server

Entitlement (Annual Technical Support)

Standalone Stage License sales are retired. Active Annual Technical Support includes:

Product Updates
Customer Support Tickets
Up to 3 active Stage Environments per supported Production License

Stage creation is also subject to available server resources. The commercial ceiling of 3 does not guarantee that every server can safely run three Stages.

When Annual Technical Support expires:

New Stage operations (create, clone, refresh, rebuild) are blocked
Existing Stages are not automatically stopped or deleted

You can still list, status, start, stop, back up, and delete existing Stages. Support expiry does not delete Stage data on its own.

Limits

Limit	Behavior
Commercial	Up to 3 active Stages per supported Production License (`STAGE_LIMIT_REACHED` if exceeded)
Resources	Host disk/memory admission may deny with `STAGE_INSUFFICIENT_RESOURCES` even below 3

If resources are insufficient, Production is not modified. Increase server capacity and try again.

Retention

Setting	Value
Default lifetime	14 calendar days
Maximum	60 days from original creation