I have a question about when to use a development environment and when to use a branch, what the cases are for each, what differentiates them, and if there are any practical examples. Thank you.
A development deployment is a separate backend (its own database, secrets, and URL). Use it when:
- Testing a migration or schema change against throwaway data
- Experimenting with a new integration or API key
- Letting teammates try a feature without polluting production data
- Key trait: the database starts empty (nothing copied from production, unless you clone it manually).
A branch is a full copy of your app (code + isolated backend) that you can merge back into main. Use it when:
- Testing a risky change or large rework before it reaches your main app
- Letting the Agent work on a feature in the background while you keep building on main
- Running several efforts in parallel, each on its own branch
- Testing against a copy of your real data (via “Replicate production data”)
Key trait: changes are mergeable back into main; if you don’t like them, just close the branch.
More info:
1 Like
Luis - great question. We are deprecating"deployments". We strongly recommend you use branches for most things instead. Deployments was always a temporary thing until we got branches live.
The way it will work is there will be a prod, staging, and dev environment. And we will have one deployment for prod, one for staging, and unlimited for dev (branches).
Let me know if this makes sense!
Feel free to email us about your workflow. I’d love to learn more
1 Like
Hi, I think this is a great idea, and along with the recently released tests, this will make software releases safer and reduce errors in production. Thanks, team! 
Awesome!