using projects as deployments
We are getting about to deploy Convex, switching from Neon, and honestly there are a lot of things to love about Convex, but Neon's system of managing deployments and branching seems way more straightforward. We would rather just have different named environments that we can easily create and deploy to. But Convex only allows one "prod" deployment per project apparently, and preview deployments behave oddly, e.g. changing their URL and deleting your data each time you push to your branch. So we are thinking about just using lots of projects and mostly using one deployment per project (except maybe for dev environments, but even for them it would be nice if dev environments were not linked to developers but each developer could just use whichever dev environments they wanted whenever they wanted and they would work similarly to prod environments). Have others encountered these issues? Any chance Convex will release a less opinionated deployment system that doesn't force its particular way of working on us?
3 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
Any chance Convex will release a less opinionated deployment system that doesn't force its particular way of working on us?If I recall correctly, the Convex team has acknowledged that users want more deployment flexibility, and I believe those pleas will be addressed. How soon, though, is unknown. They haven't announced (even vaguely) where that falls on the roadmap. I'll add a thread in #faq about this and update it whenever I hear more news.
Hey @splon, short answer is yes, we're going to change the deployments model to be more flexible.
The changes will likely be incremental, starting with allowing you to have more than one dev deployment and give dev deployments their own names. These changes should be out early 2026
The future after that isn't as set in stone right now, but you can expect more conveniences like customizing the behavior of deployments, more ACLs on individual projects/deployments, etc
For now, we've seen folks have success with using multiple projects to maintain multiple Production-like deployments (e.g. sharding or staging)