Staging
Staging that saves back.
Branch production, change what you need, then save it back as a draft. Nothing deploys on its own.
- RATE_LIMIT
- 100
- NEW_CHECKOUT
- true
Stays in each environment
- Replicas
- 3
- Domain
- acme.com
- Git branch
- main
- postgres
- real data
- RATE_LIMIT
- 500
- NEW_CHECKOUT
- true
Stays in each environment
- Replicas
- 1
- Domain
- web-staging.acme-x7q2.ployz.app
- Git branch
- develop
- postgres
- own, started empty
Save is a draft
Save to production stages changes in production. Nothing deploys until you click Deploy.
Update warns on clashes
Update brings in what production deployed. If both sides changed a setting, you see amber first.
Data never moves
A copied database starts empty, and a setup command like pnpm db:seed fills it.
Pick what staging copies.
Copy a service, give it a new empty volume, or share production's. A shared database shows in amber.
See what's waiting.
The branch button says 1 to save, 1 update, or Up to date. Save shows every setting as Current and New, with × to leave one out.
Compared with the platforms.
| What you need | Heroku Pipelines, Render, Railway | Ployz on your server |
|---|---|---|
| Settings back to production | Heroku promotes the build only | Saved per setting as a draft |
| Changes from production | Railway syncs. Render: by hand | Update, as staged changes |
| Both sides changed a setting | Railway's docs don't say | Amber warning both ways |
| New secrets | Set per app or environment | Asks for production's own value |
| Price | Heroku bills each staging dyno | RAM on your own server |
Good to know.
- Save carries settings. Code reaches production through your Git merge.
- Replicas, limits, domains and the Git branch stay per environment.
- An unkept branch closes after 7 days without a deploy.
- No backups and no rollbacks yet: fix forward or branch again.
- GitHub only, and no team roles yet.
Questions
What is a staging environment?
A copy of your app that runs apart from production, where you try changes before users see them. In Ployz it's a branch of production with its own services and https addresses.
Does Save to production deploy anything?
No. Save stages the changes in production, like a draft. You review them and click Deploy. Save never moves data and never deletes anything in production.
Does staging get a copy of production's data?
No. Ployz never copies data. A copied database starts empty, and a setup command can fill it before the service first starts. Sharing production's database is shown in amber.
Is there a Heroku Pipelines alternative that syncs config?
Heroku Pipelines promote the build and leave config vars to you. Railway's Sync and Ployz's Save both stage changes for review. Ployz also warns when both sides changed a setting.
Can I have more than one staging?
Yes. Branch production as many times as you like, or branch a branch. Save goes back to its parent.
What does it cost?
Free on your own servers, including every environment and branch. Staging uses RAM on servers you rent. Custom domains are $9 a month per organization.
Your servers. The whole platform. Free on your own servers.
Deploy your appFacts checked 2026-10-02.