Guides
Staging vs Production
Understand the two deployment environments and when to use each.
Odyn uses two deployment environments: staging and production.
Staging
- Deploys immediately on each build.
- URLs use the
stagingalias and are not cached. - Use staging to test changes before they go to production.
- Staging embed codes point to the latest staging deployment.
Production
- Deploys when you click Deploy to Production. Odyn publishes your current editor files.
- URLs are immutable and versioned. Each production deployment gets a unique version number.
- Production deployments create a file snapshot for rollback.
- The
@latestalias always resolves to the most recent production deployment.
Deploy Flow
- Deploy to staging and verify.
- Click Deploy to Production in the deployment panel.
- The production version increments and the
@latestalias updates.
When to Use Each
| Environment | Use Case |
|---|---|
| Staging | Testing changes, development iteration |
| Production | Live sites, client-facing deployments |
Free plan users can deploy to staging only. Production deployments require the Beta, Individual, or Team plan. See Plans and Limits.