Staging clones on Managed Cloud
One-click clone of production to a staging URL; promote when ready.
3 min read
Staging clones on Managed Cloud work like the shared-hosting equivalent but with an extra layer: code is pinned to a Git branch, so you can deploy a feature branch into staging without manual file copying.
Create a clone from your app's page: Environments → New environment → Clone of production. Pick a branch; staging tracks that branch and rebuilds on every push to it.
Database semantics: by default staging gets its own copy of the production database at clone time. The two diverge afterward. You can opt into a 'read-only proxy' mode where staging reads from production but writes go to a separate staging-only database; useful for visual review without touching production data.
Promote when ready. Promotion merges the staging branch into the production branch (or whatever you've configured) and triggers a deploy. Database changes need explicit migration; we don't auto-merge schema diffs.