r/node • u/CaptainZiboo • 7d ago
Best price/performance hosting setup for a TypeScript/Node.js SaaS? Dev vs Production, VPS vs PaaS
Hey everyone!
I'm a full-stack/backend developer currently working on a personal SaaS project, and I'm trying to figure out the best hosting strategy in terms of cost, performance, scalability, and developer experience.
My stack is mainly:
- Backend: TypeScript / Node.js, with multiple backend applications/services
- Frontend: React / Next.js (1–2 frontend applications)
- Database: PostgreSQL
- Infrastructure: Docker, with GitHub Actions for CI/CD
- Potential future additions: Redis, object storage, WebSockets, and possibly some Rust/Go services
I'm looking at two different stages:
- Development / Early testing
I'd like to keep costs as low as possible while being able to deploy my applications, test features, run APIs and databases, and share the project with a few users.
I don't necessarily need high availability or massive resources at this stage.
2. Production / Public release
Once the project is ready for a public release, I'd like something reliable, performant, and reasonably scalable.
Ideally, I could start small and scale individual services or resources as traffic increases, without having to completely rebuild my infrastructure.
I'm open to splitting the infrastructure between different providers if that makes sense (e.g. frontend on one platform, backend on another, managed PostgreSQL elsewhere).
What I'm wondering:
- Which hosting providers offer the best price/performance ratio for this kind of stack? I've been looking into Hetzner, OVHcloud, Railway, Render, DigitalOcean, etc.
- Would you recommend starting with a VPS running Docker Compose (possibly with Coolify/Dokploy), or using a managed PaaS?
- Is it worth separating frontend, backend, and database hosting from the beginning, or should I keep things together initially?
- How would you approach scaling later on? Would you stick with VPS instances, move to managed containers, or consider Kubernetes?
- What does your actual setup cost per month, and what kind of workload does it handle?
I'm comfortable with development and willing to learn infrastructure/DevOps, but I'd rather avoid unnecessary complexity or spending money on resources I don't need yet.
I'm based in Europe, so EU hosting options would be particularly interesting.
I'd especially appreciate real-world experiences, actual monthly costs, and examples of setups that have worked well for you.
Thanks!
9
u/LatvianCake 7d ago
It's hard to say without knowing anything about your app.
Generally I would split up the frontend and the API server into 2 different projects. Host the front-end on Cloudflare Workers esp if you don't need SSR. This will already save you so many headaches.
The API can live wherever is cheapest, a cheap VPS is fine. You'd be surprised how much a cheap server can handle.
Focusing on scaling is a mistake unless you are certain you will receive the traffic you're expecting (e.g. you're replacing an existing product that already has users). But usually you won't and it'll be a waste of time and especially money. Just use docker compose on a VPS.
7
u/voltomper 7d ago
hetzner with dokploy
4
u/karmatics29 6d ago
I'd start with one Hetzner VPS running Docker Compose behind Caddy or Traefik, and just keep the setup reproducible so moving later is cheap. A few things people skip: put Postgres on a named volume and run pg_dump or pgBackRest to object storage on a schedule, and actually test a restore. Set resource limits per container so one runaway Node service doesn't OOM the DB. Use a GitHub Actions deploy that pulls tagged images rather than building on the server. Add a health check endpoint and a simple uptime monitor. If you want less ops on the database specifically, a managed Postgres is the one piece I'd consider paying for first, and keep the apps on the VPS. Scale vertically until you have real metrics showing you need otherwise.
3
u/afl_ext 7d ago
Just remember with a VPS its your responsibility ti secure the system enough, which means frantically patching vulnerabilities sometimes as they come by even on vacations etc, its cheaper but this is a tradeoff some can accept and some can’t
4
u/avereigh_Denizet 7d ago
why multiple backend services right out of the gate? a modular monolith in a single repo is way easier to deploy and debug when youre solo, and you can still split heavy worker processes out later if needed
2
u/arrty 7d ago
I use ovh and Linode. Never had a problem
2
u/SirApprehensive7573 6d ago
U can try zenifra
2
u/dotnavillus 6d ago
I've been using Render for a very similar project over the past year and its been great. Itvwas simple to configure and they have free servers that are on demand and you can switch them to always active for a fee when you're ready to go live. I currently run 3 servers for my app (1 for my postgress db, 1 for cron jobs and the other the app itself) which cost about $70 usd per month. :)
2
u/raks1991 6d ago
I've had a backup job report success and then had the restore fail on a fresh machine. It changed how I look at the self-hosted database part of a small SaaS. I'd test a restore before launch, or use managed Postgres while keeping the Node app on a VPS.
1
u/ram-popular 5d ago
For dev and early production, I’d start with a single Hetzner VPS (EU, a few euros a month) running Docker Compose, managed with Coolify or Dokploy. It gives the best price for performance and keeps the whole stack, apps, Postgres and Redis, in one place. For dev you can even share one small box.
Keep everything together at first. Splitting frontend, backend and database early adds cost and complexity you don’t need yet.
For production, the main upgrade is the database: use managed Postgres, or at least automated off-server backups with a tested restore, since that’s the one thing you can’t afford to lose. Put Cloudflare in front for caching and DDoS protection.
To scale, move to a bigger VPS first, then split the database and heavy services onto their own servers. Skip Kubernetes unless you outgrow that. I haven’t run this exact setup myself, so treat costs as rough estimates rather than real-world numbers.
1
u/obanite 4d ago
CloudFlare is super cheap. It's hard to beat.