Hosting personal projects in 2026: from €0 to production

Deploying an app in 2026 is almost trivial: one git push and it’s live. What isn’t trivial is opening the billing dashboard at the end of the month and finding a three-figure surprise for a project that hasn’t made its first euro yet.

A lot of people still build enterprise-grade architecture for personal projects and end up with over-infrastructure. This post is the practical version: how to run a solid, secure stack that can handle growth for less than a specialty coffee.

The graveyard of unnecessary bills

I still see developers running their logic on Azure Functions or AWS Lambda and connecting to a database on Supabase. Serverless makes sense for big load spikes, but for services that need to be up 24/7 it usually gets expensive. You pay for every execution, and the latency between different providers ends up showing in the user experience.

Then there’s the opposite extreme: spinning up an oversized EC2 instance just to make sure the backend stays “alive”. It’s like renting a truck to move a shoebox. You pay for CPU and RAM that sit idle 99% of the time and hand your money to Jeff Bezos.

The traffic trap: the “wallet DDoS”

The real danger isn’t compute, it’s network usage (egress fees). Providers like Vercel made deploying accessible to everyone, but what they charge for data transfer can get out of hand. A badly handled DDoS attack, or just a bot that decides to scrape your site aggressively, can generate millions of requests in minutes.

If your spend limits aren’t set up properly, you can wake up owing money just because your provider billed you for traffic you never asked for.

The 2026 hosting map: where does the code go?

To find your way through all the options without losing money, I find it useful to sort tools by how much responsibility they leave with you. Knowing whether they’re good isn’t enough; you need to know how much control they ask for in exchange for the price.

1. PaaS: convenience costs money

If you want something that works without any setup, PaaS is still the first option. It fits MVPs where your time is worth more than a few dollars’ difference.

• Vercel is the reference for frontend and serverless. Its Next.js integration is excellent, but keep an eye on the free tier limits once traffic starts growing.
• Railway is probably the most balanced platform for backends. You can deploy Docker containers or services from GitHub in seconds. The credit model is fair, but for a 24/7 service the meter never stops.

2. The VPS comeback: full control, fixed cost

In 2026, the biggest trend among indie hackers is going back to the virtual private server (VPS). The difference from a few years ago is that you no longer need to be a terminal expert to run one.

• Hetzner is still the best performance-for-price option in Europe. For the price of a dinner you get more than enough machine for 10 small projects.
• DigitalOcean is the most popular choice if you’d rather use a US provider. It usually gives credits to new users, so you can experiment without early surprises.
• Coolify is the missing piece: an open-source Heroku alternative you install on your own VPS. It gives you a visual interface for databases, deployments and SSL certificates without writing a line of Bash.
• Dokploy is a very lightweight alternative that’s gained a lot of ground this year. If you want something simple, Docker-based and with a clean interface, it’s a good pick.

3. Databases that scale to zero

• Neon: plain Postgres that “shuts down” when there’s no traffic and wakes up in milliseconds.
• Turso: based on SQLite, a good fit if your app runs at the edge. Very generous free tier.
• Supabase: more than a database, it’s a full backend-as-a-service. Handy for moving fast, with auth and storage included.

Which stack should you pick?

Scenario A: an MVP as fast as possible

You want to validate an idea in under 48 hours without opening a terminal.

• Frontend: Vercel.
• Backend and database: Supabase + Railway.

It’s the fastest route and the upfront cost is €0.

Scenario B: an indie hacker with several projects

You have 5 or 6 ideas and want to pay the same amount every month.

• Infrastructure: a VPS on Hetzner or DigitalOcean.
• Orchestrator: Coolify or Dokploy.

You pay a flat ~€5-10 a month for all your projects.

Scenario C: a high-performance app on the edge

You need excellent SEO and minimal latency anywhere in the world.

• Framework: Next.js or Astro.
• Deployment: Cloudflare Pages.
• Database: Turso.

It scales without you having to think about it, and network transfer is almost free.

Coolify or Dokploy?

In 2026 we don’t install Docker by hand anymore; we use control panels. Between the two I mentioned:

• Coolify if you’re coming from Heroku and want every convenience: automatic deployments, one-click backups and a large community. It’s the one that does the most.
• Dokploy if you’d rather have something more minimal and fast. It uses fewer resources and its approach to Docker Compose is very straightforward.

Checklist before you launch anything

1. Spend limits. Turn on alerts in Vercel or AWS. Set a warning at €5 and an automatic shutdown at €20.
2. Backups. If you use Coolify or Dokploy, that’s on you. Send daily backups to external storage like S3 or Cloudflare R2.
3. Firewall and SSH. Disable password login, use SSH keys only and move off port 22. Use ufw to restrict traffic.
4. DDoS protection. Put Cloudflare in front as a proxy. It’s the best free barrier for your wallet.
5. Monitoring. Set up UptimeRobot or Better Stack. Don’t find out from a user that your server is down.

Wrapping up

Infrastructure doesn’t have to be a money pit. Today an independent developer can control the whole thing without going through the complexity of the big providers.

What keeps a personal project alive for years isn’t the trendiest stack, it’s one whose running costs don’t end up killing it.

What do you use for your projects: serverless, or have you moved to your own server?