Alternatives
Compare
Every way of running services has trade-offs. Here is where the platform wins, where it does not, and what moving over looks like.
Comparisons
Pick the setup that fits your team
Honest side-by-side comparisons with the ways teams usually run services before they move here.
- vs DIY Kubernetes
Platform vs DIY Kubernetes
Keep the power of containers without running clusters, upgrades, and on-call for the control plane.
Read the comparison - vs Legacy PaaS
Platform vs Legacy PaaS
The same push-to-deploy workflow, with private networking, preview environments, and pricing that scales down.
Read the comparison - vs Traditional VPS
Platform vs Traditional VPS
Stop patching servers and writing deploy scripts. Keep the predictable bill.
Read the comparison
01Do I have to move everything at once?
No. Most teams start with one service or a staging environment, point a subdomain at it, and move the rest once they trust the setup.
02Can I keep my existing database during the move?
Yes. Services connect to any database you can reach over the network. Move the data later with a dump and restore, or keep it where it is.
03Is there help with migration?
Team and Enterprise workspaces get a migration review with an engineer, who checks your services, environment variables, and cutover plan.
04What if the platform is not the right fit?
Your code stays in your repository and runs from a standard build. You can export your configuration and leave at any time.