Draft, not yet published
Render vs Railway vs Hetzner: cost and control compared for a growing app
7 July 2026· 5 min read · by Stackbastion
Your app works. Now the hosting bill is starting to sting, or you’re worried it will soon. You’ve heard Render is easy, Railway is nice, and Hetzner is cheap but scary. Which one actually fits an app that’s growing past its first users? Here’s an honest look at all three.
What each one actually is
These three are not the same kind of thing, and that’s the first thing to get straight.
- Render and Railway are platform-as-a-service (PaaS). You push code, they build it, run it, and keep it online. You pay a premium so you don’t have to think about servers.
- Hetzner sells you a raw server (a VPS or a dedicated box). You get a blank Linux machine and root access. Nothing is set up. You do all of it.
So the real trade is money versus time. PaaS costs more per month but saves you hours. Hetzner costs less but hands you the whole job.
The monthly cost, roughly
Prices below are approximate public pricing as of mid-2026. Treat them as ballpark, not quotes. Assume a small app: one web service, one Postgres database, modest traffic.
| Setup | Compute | Database | Rough monthly total |
|---|---|---|---|
| Render | ~$7 starter web service, ~$25 for a standard instance under load | ~$7 to $95 depending on tier | ~$15 to $120 |
| Railway | Usage-based, ~$5 minimum plus what you burn; ~$20 credit on the Hobby-to-Pro range | Postgres billed by usage, often ~$10 to $40 | ~$20 to $80 |
| Hetzner | CX22 VPS ~€4/mo, CX32 ~€7/mo, a dedicated AX line from ~€40/mo | Postgres you run yourself on the same box: €0 extra | ~€5 to €45 |
The gap looks huge, and at the raw-infrastructure level it is. A Hetzner CX32 gives you 4 vCPU and 8 GB RAM for about 7 euros. Getting close to that on Render or Railway is more like 40 to 80 dollars once you add a real database tier.
But the Hetzner number is misleading if you stop there. That 7 euros buys you a machine, not a running app with backups and monitoring. Keep reading.
The part the price table hides
PaaS bundles things you’d otherwise build yourself:
- Deploys. Push to Git, it builds and ships. On Hetzner you set up your own deploy path (a Docker build, a systemd service, or a tool like Coolify).
- TLS certificates. Render and Railway hand you HTTPS automatically. On Hetzner you run Caddy or Certbot and renew certs yourself (Caddy makes this nearly automatic, but you still own it).
- Managed database. Render and Railway keep Postgres patched and take backups. On Hetzner you install Postgres, configure it, and set up your own backups with something like pgBackRest.
- Restarts and health checks. PaaS restarts a crashed process for you. On Hetzner that’s your systemd config or Docker restart policy.
None of this is hard on its own. Added up, it’s a real weekend of setup and a small ongoing tax of patching, cert checks, and backup verification. If your time is worth 60 euros an hour, ten hours of setup is 600 euros. That erases a lot of the monthly saving in year one.
When each one is the right call
Pick Render if you want the least surprise. Fixed instance sizes, clear pricing, a decent free tier for testing, and a managed Postgres that just works. The downside is you pay a steady premium and you can hit a wall on cost once you scale up to bigger instances.
Pick Railway if you like a clean developer experience and don’t mind usage-based billing. The trade-off is that usage-based pricing can spike in a bad month, and it’s harder to predict the bill in advance. Great for prototyping and small production apps.
Pick Hetzner if you’re comfortable on a Linux box, or willing to learn, and the monthly saving is worth the setup and upkeep. The downside is real: you own backups, security patches, uptime monitoring, and the 2am restart when something falls over. There’s no support line that fixes your app. For more on when this shift makes sense, see when DIY hosting stops making sense.
The honest summary: Render and Railway sell you time. Hetzner sells you control and a lower bill, and charges you back in hours and responsibility.
Or, we do it for you
We run apps on Hetzner and give you the Hetzner bill without the Hetzner homework: tested backups, monitoring, a named human on call, and patches handled. You get the low infrastructure cost and skip the weekend of setup. See our pricing for what that costs.
FAQ
Is Hetzner really that much cheaper, or is it a trick?
The raw server really is that cheap. A capable VPS is a few euros a month. The catch is that the price only covers the metal. Backups, monitoring, deploys, and security are your job, and those cost time or money elsewhere. Cheaper server, more work.
Can I start on Render and move to Hetzner later?
Yes, and lots of people do exactly that. Start on a PaaS to get moving fast, then move to Hetzner when the bill outgrows the convenience. The move is easiest if your app is in a Docker container and your data is standard Postgres, both of which keep you portable.
Will Railway’s usage billing blow up my budget?
It can if you get a traffic spike or leave something running. Railway bills for what you use, so a runaway process or a viral day costs more than a fixed plan would. Set spending limits and alerts, and check your usage weekly for the first month so you learn your baseline.
What about scaling to lots of users?
All three can scale, but the cost curves differ. PaaS gets expensive fast as you add bigger instances. A single Hetzner dedicated box (from ~€40/mo) can handle far more load than an equivalent PaaS bill, but you manage the scaling yourself. For most growing apps, one well-sized server goes a long way before you need anything fancy.