Heroku taught a generation of developers the best deployment experience ever shipped: git push heroku main, wait forty seconds, get a URL. Vercel refined it for the frontend era. The experience was never the problem. The problem is the bill that arrives when your side project grows up — dyno pricing that makes a hobby cost like a habit, function invocations metered like taxi fare, and the quiet realization that your app runs on hardware you'll never see, under limits you don't set.
Meanwhile, the humble VPS became absurdly good value: $10–20 a month buys enough compute to run a dozen small apps. What it doesn't buy is the experience — until you put a self-hosted platform layer on top. That's the deal this post is about: keeping the git-push workflow, owning the server underneath.
What you're actually buying from a PaaS
Strip the branding and Heroku/Vercel sell five things: build-from-git, process management with restarts, HTTPS and routing, environment/config handling, and rollback when a deploy goes wrong. All five are automatable on your own hardware — the open-source world proved it years ago with Dokku, and a newer generation (Coolify, and DeployCloud among them) turned it into a product with a UI, previews, and team features rather than a weekend of YAML.
DeployCloud's version of the pitch: run the platform yourself, git push to deploy any language, and get the full PaaS loop — zero-downtime deploys, preview environments per branch, add-ons, cron jobs, one-click rollback — on infrastructure you own. Their comparison pages against Heroku, Vercel and Dokku are honest about the trade-offs, which is rarer than it should be.
The economics, concretely
A typical indie stack — two web apps, an API, a worker, Postgres, Redis — costs roughly:
- Managed PaaS: $25–50/dyno-equivalent × several services, plus managed database pricing. Real-world small-team bills routinely land at $100–300/month.
- Self-hosted: one $20 VPS (or two, for peace of mind), everything on it. The platform layer is free or flat-priced. Total: the price of lunch.
The gap widens with every app you add, because your marginal cost of "one more service" drops to zero. That's the structural difference: PaaS meters convenience per app; a self-hosted platform makes convenience a fixed cost.
What it costs you (the honest part)
You become responsible for the box: OS updates, disk space, backups, and the 2 a.m. question when the host's data center hiccups. Modern platforms shrink this burden dramatically — health checks, automatic restarts, one-command backups — but they don't make it zero. The fair framing:
- Stay on managed PaaS if downtime costs you real revenue per minute, compliance demands managed everything, or nobody on the team wants to own a server. Convenience is worth money; sometimes a lot of it.
- Go self-hosted for side projects, internal tools, client work, staging environments, and honestly most production apps under serious-scale traffic — the category where the PaaS premium buys you almost nothing you'd miss.
Migrating without drama
- Move the stateless things first — web apps and workers redeploy anywhere in minutes; databases deserve care and a rehearsed restore.
- Run parallel for a week: deploy to both, point a test domain at the new box, compare. DNS is your instant rollback.
- Rehearse the rollback and the backup-restore once before you need either. This is 90% of "ops competence" for a small app.
- Then consolidate: every app you move after the first one is nearly free — which is exactly when self-hosting starts feeling like a superpower. (The DeployCloud docs cover the full path.)
The deployment experience Heroku invented was worth copying. The pricing model wasn't. In 2026 you can keep the first and skip the second — and the tools to do it are a git push away.