Originally published at devtoolpicks.com
A tweet blew up this week asking a simple question: why do developers still pay for Vercel when a €3.79/month Hetzner VPS exists? Nine thousand developers had opinions. Most of them missed the point entirely.
The answer isn't "Vercel is a scam" or "self-hosting always wins." The honest answer is: it depends on what you're building, how much your time is worth, and what stage your project is at.
I've deployed on all four of these platforms. Here's the actual breakdown.
Quick verdict: If you're shipping a Next.js frontend or a simple SaaS MVP, Vercel is genuinely worth the money. If you're running a full Laravel or Node backend past early validation, Hetzner with Coolify makes you look silly for not switching. Railway and Render sit in between and serve a specific type of developer well.
Quick Comparison
| Platform | Starting Price | Best For | Free Tier |
|---|---|---|---|
| Vercel | Free / $20/month | Next.js, frontend, JAMstack | Yes (non-commercial only) |
| Railway | $5/month | Full-stack apps, fast iteration | $5 trial credit |
| Render | $7/month | Predictable costs, background workers | Yes (static + limited web services) |
| Hetzner | From €3.79/month | Backend-heavy apps, maximum value | No |
Vercel
Vercel is the platform Next.js was built for. Literally. Vercel created Next.js. If you're building anything in that ecosystem, the integration is unmatched.
What it actually costs:
The Hobby plan is free, but it comes with a hard restriction: no commercial use. The moment your project generates revenue, you're required to upgrade. Pro costs $20 per user per month, with a $20 usage credit included. Add a co-founder and you're at $40/month before you've written a line of code.
Beyond the base fee, you pay for overages. Bandwidth beyond 1 TB costs $0.15/GB. Serverless function execution is billed by CPU time. Image optimization costs extra past the included limit. For most solo projects, these limits are generous. For anything with real traffic or AI workloads, bills can surprise you.
The real pros:
- Zero-config deploys from GitHub. Push and it's live
- Automatic preview URLs for every pull request, which is genuinely useful for client work
- Global edge CDN with zero configuration required
- Incremental Static Regeneration and Edge Functions work natively with Next.js
- Best-in-class Next.js support without workarounds or surprises
The real cons:
- $20/user/month adds up fast for a bootstrapped project with no revenue yet
- Hobby plan commercial restriction is enforced via Terms of Service. Vercel does act on violations
- Vendor lock-in is real. Some Next.js features only work properly on Vercel
- Usage-based billing means costs get unpredictable at scale
- It's the wrong tool for full-stack apps that need persistent storage and background workers
Who should NOT use Vercel:
If you're building a Laravel app, a Node backend with queues, or anything needing persistent storage and background processes, Vercel is the wrong choice. It's a frontend-first platform. Forcing a full-stack backend onto Vercel's serverless model creates complexity and cost that simply doesn't exist on a VPS.
Railway
Railway is what Heroku should have become. It's a modern PaaS that gives you the deployment simplicity of Vercel but for full-stack apps: backends, databases, workers, and cron jobs in one place.
What it actually costs:
The Hobby plan is $5/month, which includes $5 of resource usage. For very light projects, it's effectively free. Pro is $20/month with a $20 usage credit. Railway bills by the minute for actual compute used. If your app idles, you pay almost nothing. The visual project canvas showing all your services connected together is one of the nicest developer interfaces available right now.
The real pros:
- Fastest deploy experience of any platform on this list
- Visual canvas shows your entire architecture (app, DB, workers) at a glance
- Usage-based billing means low-traffic side projects cost almost nothing
- Supports any language via Docker or Nixpacks
- Excellent for Laravel, Node backends, Python APIs, anything full-stack
The real cons:
- Pricing gets unpredictable as usage scales. Hard to budget to an exact number
- Less mature than Render for multi-region setups
- Free tier is a one-time $5 trial credit, not a permanent option
- Documentation is thinner than Render's
Who should NOT use Railway:
If you need predictable fixed monthly costs, Railway's usage-based model requires active monitoring to avoid surprises. It's also not ideal for static site hosting. Use Vercel or Netlify for that. And if you're running a high-traffic production app needing multi-region redundancy, Railway isn't ready for that yet.
Render
Render is the most Heroku-like option on this list. Fixed pricing tiers, a permanent free option for static sites, and a platform that's been reliable for years. It's not the cheapest or the most exciting, but it causes the least drama.
What it actually costs:
Static sites are free forever. Web services start at $7/month for the Starter tier (512MB RAM, 0.5 CPU). Standard is $25/month (2GB RAM, 1 CPU). For a solo dev running a web service plus a PostgreSQL database, expect to pay roughly $20-35/month depending on database size.
The real pros:
- Permanent free tier for static sites, no 30-day expiry
- Predictable pricing makes monthly budgeting straightforward
- Built-in background workers, cron jobs, and PostgreSQL without extra configuration
- More mature documentation than Railway
- Better multi-region support than Railway
The real cons:
- $7/month minimum for always-on backend services
- Free PostgreSQL databases expire after 30 days. This catches people out more often than it should
- Slower deployments than Railway in head-to-head tests
- The interface feels more enterprise-y and less modern than Railway's
Who should NOT use Render:
If deploy speed and iteration pace matter most (frequent changes, lots of preview environments), Railway feels sharper day-to-day. And if your primary workload is a Next.js frontend, just use Vercel. Render adds nothing in that scenario.
Hetzner
This is the option that started the Twitter debate. For the right developer at the right project stage, it's not even close.
What it actually costs:
The CX22 gives you 2 vCPU, 4GB RAM, 40GB NVMe SSD, and 20TB monthly traffic for €3.79/month. The CX32 gives you 4 vCPU, 8GB RAM, and 80GB storage for €6.80/month. These aren't cloud credits with usage surprises. They're fixed specs that stay yours as long as you're paying.
Pricing heads-up: Hetzner has confirmed a price increase effective April 1, 2026. Some plans will increase. Check the current pricing at hetzner.com/cloud before signing up. Even after the adjustment, Hetzner remains significantly cheaper than comparable specs on most platforms.
For comparison: a DigitalOcean 2 vCPU / 4GB droplet costs $24/month, roughly 4-6x more than Hetzner for equivalent specs. DigitalOcean wins on US-based support, better beginner documentation, and a larger tutorial ecosystem. If you're new to self-hosting and based in the US, DigitalOcean is a gentler entry point. If you know what you're doing, Hetzner is the obvious value choice.
The real pros:
- Best price-to-spec ratio in the VPS market, full stop
- 20TB monthly traffic included in EU regions. Competitors charge extra for this
- GDPR-compliant EU data residency out of the box, relevant for EU founders
- Pair it with Coolify and you get a self-hosted PaaS for about €4-7/month total
- No vendor lock-in, no serverless limits, no surprise bills
The real cons:
- You manage the server. Security patches, updates, monitoring are all on you
- No managed database, no formal uptime SLA
- Support is ticket-based only for cloud products. No live chat, no phone
- US datacenter traffic drops to 1TB/month compared to 20TB in EU regions
- Setup takes a few hours to go from fresh VPS to production-ready. Not minutes
Who should NOT use Hetzner:
If you're shipping a Next.js frontend and iterating fast, the time saved with Vercel's zero-config deploys is real. Hetzner is not for developers who want to avoid thinking about servers. If nginx configs make you uncomfortable, use a managed platform. Also not ideal if your users are primarily in the US and latency matters.
Head-to-Head: The Decision That Actually Matters
Most comparisons get this wrong by treating everyone as the same type of developer. The question isn't "which platform is best" but "which platform is right for where you are right now."
For a Next.js SaaS MVP in the first six months:
Vercel wins. Zero-config deploys, preview URLs, and native ISR save real time when you're iterating daily. At $20/month, it's cheaper than the hours you'd spend configuring a VPS for a frontend-heavy app. Reassess when you hit $1-2K MRR and the cost starts to feel meaningful.
For a full-stack Laravel or Node app:
Railway or Hetzner. Vercel is genuinely the wrong tool here. It's built for serverless frontends, not persistent backends. Railway gets you to production faster. Hetzner gets you there cheaper once you've validated the idea.
For a bootstrapped SaaS past early validation:
Hetzner with Coolify. I covered the full setup in Laravel Forge vs Ploi vs Coolify. A €6.80/month CX32 running your app, database, queue worker, and reverse proxy is genuinely hard to justify moving away from. The Vercel equivalent would cost 4-5x more.
For a solo dev who hates DevOps:
Render. Not the cheapest or most exciting, but it's the most reliable "just works" platform for full-stack apps if you don't want to think about servers.
Final Recommendation
Use Vercel if you're building a Next.js app, developer experience matters more than cost right now, and you're in early validation mode where $20/month is irrelevant.
Use Railway if you want the managed PaaS experience for a full-stack app, you prefer paying for actual usage over a flat fee, and you value a modern, fast deploy workflow.
Use Render if you want predictable monthly costs, you're running background workers or cron jobs, and you value platform stability and clear documentation over cutting-edge features.
Use Hetzner if you're past early validation, comfortable with Linux, want the best raw compute value on the market, and are running a backend-heavy app that doesn't need Vercel's serverless features.
The viral debate framed this as "Vercel is wasteful." That's not quite right. Vercel is expensive for the wrong use case. For a Next.js app in early growth, it earns its cost. The mistake most indie hackers make is staying on Vercel well past the point where switching makes obvious financial sense.
FAQ
Is Vercel free for commercial use?
No. Vercel's Hobby plan is free but explicitly restricted to personal, non-commercial projects. Any project that generates revenue requires the Pro plan at $20/user/month. Vercel enforces this through their Terms of Service.
Is Hetzner good for beginners?
Hetzner is a raw VPS. You configure it yourself. It's not beginner-friendly out of the box. Pairing it with Coolify gives you a GUI for deployments, SSL, and database management that makes self-hosting far more approachable. DigitalOcean is also a gentler starting point if you're new to servers.
What's the cheapest way to host a Laravel app in 2026?
A Hetzner CX22 (check current pricing after the April 1 increase) with Coolify installed for free is the cheapest production-ready option. A CX32 handles most small-to-medium Laravel SaaS workloads comfortably for under €7/month.
Can Railway replace Vercel?
For Next.js apps specifically, no. Vercel's native integration is too deep. For everything else, including Node backends, Laravel, Python, and Go, Railway is a legitimate and often better alternative with a great developer experience.
Does Hetzner have US data centres?
Yes. Hetzner has US servers in Ashburn, Virginia and Hillsboro, Oregon. The included monthly traffic drops from 20TB to 1TB in US regions compared to EU, which is worth factoring in for bandwidth-heavy applications.
Conclusion
This isn't a fight between "Vercel is overpriced" and "self-hosting always wins." It's a question of stage, stack, and how you want to spend your time.
Use managed platforms early. They buy you speed when speed matters most. Switch to Hetzner when the savings become real money and your setup has stabilised. The tweet that went viral this week wasn't wrong. But the 9,000 replies proved that context matters more than any single verdict.
Most indie hackers make that switch too late. Don't be one of them.
Top comments (0)