Vercel Is Great Until You See the Bill

If you've shipped anything on Vercel, you know the feeling. Push a branch, it deploys in two minutes, you get a preview URL, it just works. That experience is genuinely good and worth acknowledging before we talk about leaving it behind.

Then you add a teammate, or your app gets real traffic, or you need an endpoint that runs longer than a few minutes. You open the billing page. And there it is.

Vercel charges per seat on the Pro plan (around €18/month per member), plus usage-based fees for bandwidth and serverless function invocations. On the free tier, functions time out at 60 seconds. Pro bumps that to 300 seconds. If you're doing anything that breathes a little, like data processing, generating PDFs, or calling a slow external API, you're managing around those limits and paying for the privilege.

There's a way to keep the same workflow without the per-use billing or the timeout clock. A VPS running Coolify.

What Coolify is

Coolify is a self-hosted PaaS. It's what Vercel, Heroku, and Railway would look like if you ran them yourself on your own server. You get a web dashboard, automatic SSL via Let's Encrypt, Traefik for reverse proxying, Docker under the hood, and the part that makes this relevant: automatic git deploys.

Connect your GitHub repo, set a branch, and Coolify rebuilds and redeploys your app on every push. Same workflow as Vercel. The server is just yours.

The numbers

A Hetzner CX22 runs about €3.92 per month. Two vCPUs, 4GB RAM, 40GB SSD. It handles several small apps at once without breaking a sweat. The CX32 (4 vCPUs, 8GB RAM) is €7.53.

Vercel Pro starts at around €18/month per member. Two people on the team and you're at €36 before a single request gets served.

The VPS wins on price pretty fast. And if you're running multiple projects on the same server, you split that single fixed cost across all of them. Vercel charges per project deployment.

Setting it up

This is the honest part: setup takes longer than Vercel. Vercel is zero-configuration. Coolify is maybe an afternoon the first time. Here's what you're actually doing:

1. Spin up a VPS on Hetzner, Linode, or wherever you prefer
2. Run the Coolify installer script (one command, it handles Docker and Traefik)
3. Point a domain at the server, configure your firewall
4. Add your GitHub repo in the Coolify dashboard
5. Set environment variables through the UI
6. Deploy

The installer handles most of the complexity. You don't write Docker Compose files by hand or configure nginx. The dashboard takes care of routing, SSL certificates, and service isolation. For multiple apps on one server, Coolify manages the domains and inter-service routing automatically.

You do that once, and then every new app you put on the server costs you nothing extra to deploy.

No function timeouts

On a VPS there are no serverless function timeouts, because there are no serverless functions. Your app runs as a persistent process. A request that takes 10 minutes? Fine. An endpoint streaming data for an hour? Also fine.

This matters a lot for certain types of work: background jobs, heavy data processing, WebSocket connections, PDF generation pipelines, long AI API calls. On Vercel you'd be splitting these into queues or fighting with the timeout limit and paying for workarounds. On a VPS you just let the process run.

Auto-deploy still works

Coolify connects to GitHub via webhooks. Push to your configured branch, Coolify pulls the code, runs your build command, and swaps the container. If the build fails, the previous version stays live. It's not meaningfully different from what Vercel does, just running on hardware you control.

Preview deployments work too. You can point separate branches at separate subdomains and get the same PR preview workflow.

If you stick Cloudflare in front of your server, you also get caching, DDoS protection, and a global CDN layer that covers most of the edge-network advantage that Vercel's infrastructure provides.

What you're giving up

Vercel is genuinely better at some things and it's worth being straight about that.

The global edge network is real. Vercel serves from nodes close to your users worldwide. A single Hetzner server in Helsinki adds latency for visitors in Singapore. For a marketing site serving a global audience, that gap shows up in the numbers. For an internal tool or a regionally focused business, it mostly doesn't matter.

You're also taking on maintenance. OS updates, disk space, monitoring uptime. Coolify handles the application layer but the underlying machine is yours. If the server goes down, you bring it back. A monthly health check takes maybe 20 minutes. That's the full overhead for most setups.

When Vercel is still the right call

Use Vercel if you genuinely need global edge performance and you're optimising for every millisecond to users worldwide. Or if you're a solo developer staying comfortably within the free tier limits and not hitting timeouts. Or if you have no interest in touching infrastructure at all and the price is fine.

For everything else, a VPS with Coolify covers the same ground for much less money, with no per-use billing surprises, no timeout gymnastics, and a git-push workflow that behaves identically to what you already know.

The setup cost is real but one-time

The first time you configure Coolify takes longer than clicking through Vercel's onboarding. That's true. But you do it once, and then it's done. Every app after that takes about as long to deploy as it does on Vercel. The cost stays flat no matter how many projects you add or how many team members are pushing code.

We run our own VPS this way. Client projects that would rack up Vercel invocation charges live on it. Our internal tools are there too. The overhead is low and the monthly bill is predictable to the cent.

If you're hitting Vercel's limits or want to get off per-use pricing without changing your deployment workflow, Coolify is worth the afternoon it takes to set up.

If you'd like help getting this running for your own stack, get in touch. The setup is straightforward when you've done it before.