r/webdev • u/Chinglee007 • 17h ago
Render vs Railway vs Cloudflare Workers
Which hosting platform would you pick for a small production app: Render vs Railway vs Cloudflare Workers?
I’m building something like a inventory management app and website — authenticated users, a Node/TypeScript API, PostgreSQL, background jobs/cron, and potentially a few thousand users over time.
Currently considering **Render, Railway, and Cloudflare Workers**.
For a production app where reliability, scaling, DB latency, and predictable costs matter, which one would you choose and why?
Would you recommend something else like **Fly.io, AWS, or Vercel + another backend** instead?
Curious to hear from people who’ve actually run production workloads on these.
24
u/Tarazena 16h ago
Hetzner VPS
1
1
u/TheNumber42Rocks 1h ago
Except Hetzner is not even cheap anymore. We tried switching to a VPS from a PaaS and it was a nightmare. We tried Caprover, Dokku, Coolify, etc. All of them would randomly crash and it wasn’t worth it to save like 10% at the end of the day. How much is your peace of mind worth?
15
u/xegoba7006 16h ago
I’m using Railway and I love it. It ticks all my boxes: easy to use (very!), it allows me to set a hard spending limit, I can deploy a Dockerfile with whatever I want (a traditional app, not serverless bullshit workers whatever), it sleeps apps when unused to save money and it supports persistent local file system storage.
Some people here will recommend hetzner which I used in the past (with Dokku)... those services are cheaper, or not, depending on the price you put to your own time.
8
u/viky109 16h ago edited 16h ago
We’ve been using Railway on my current project for a while now - no complaints whatsoever. It’s extremely simple to set up, and you just pay for what you use.
I absolutely wouldn’t use AWS for a personal project as deploying there is practically a separate project in and of itself.
3
u/itgforlife 12h ago edited 10h ago
I only have experience with Render and Hetzner.
Render is super easy. But it comes at a price. I switched to a Hetzner VPS because I wanted access to webhooks. And webhooks is currently only available in Render's $20/mo plan. My VPS costs less than half that and supports everything I want. But I had to spend a ton of time setting it up. So you just have to make a decision on whether money or convenience is more important to you.
1
3
u/Sibexico 11h ago
I'd experimented with many different functions hosting (kind off "serverless apps"), but didn't completely understand the idea. Yes, if you have less than 100k, CF Workers looks interesting, but make them without JS is pain. If you can just buy VPS with 2 cores for less than $5/month, I rly cant understand the idea...
1
u/thekwoka 36m ago
I rly cant understand the idea
Mainly just simplicity.
It's very easy to spin up an app and toss it on Cloudflare and just know it will work and have basically 100% uptime.
2
u/strongpa 17h ago
I've been using Railway for a similar stack and a hundred users for a few months and it's been solid for me - I've only tried Railway as far as developer cloud platforms go but I have a disaster recovery plan that would involve porting to Vercel which also seems to tick all the boxes (and as I use Node.js it's an obvious choice)
1
2
2
u/Remote_Camera9626 15h ago
I am using Cloudflare worker for static site hosting. I turned paid when my host hit 100 users. Mainly I chose it cause I am long time user of Cloudflare and love its reliability and security.
2
u/HelloXhale 13h ago
Depending on where your database is located, Render uses AWS data centers which could improve latency with an AWS-hosted database (plus private link is pretty cool)
It might be worth profiling to double check if that passable latency makes a difference for you app (it might not)
2
u/Big_Boss_Bob_Ross 11h ago
Cloudflare is great as long as you aren't trying to do anything outside the ordinary. If its not at huge scale a VPS is probably the best though. Extremely predictable
1
u/Chinglee007 3h ago
I am currently using workers and I am sure it'll soon reach 1k users. That's why I wanted to know if around 10k users will workers (with hyperdrive) be a problem ?
1
u/thekwoka 35m ago
There's no reason it would be a problem.
Unless whatever your thing is starts to but up against free or paid included limits.
2
u/Bob-Tech-Builder 7h ago
I'd pick the first option for this setup. Keeping the Node API, Postgres, cron jobs, and workers in one region avoids needless database latency, and fixed plans make the bill easier to forecast. The usage-priced option is convenient, but its bill can wander. An edge runtime adds connection constraints this app probably doesn't need. I'd only take on raw cloud infrastructure if its extra controls were already a requirement.
2
u/namesandfaces 5h ago
Cloudflare will be the most cost efficient but also idiosyncratic when you take advantage of all their offerings, meaning you’ll have to do work to port your code to another platform.
This is assuming you’re willing to shove your app into the shape of Cloudflare offerings.
2
u/0xdeveshb 5h ago
for that stack (node api + postgres + cron) i'd skip workers, you end up reshaping the whole app around their runtime and postgres latency gets annoying without hyperdrive. railway or render both run it as-is. just know render's free tier cold boots will betray you mid-demo. ask me how i know
1
u/Chinglee007 3h ago
I started with render , but due to their cold starts I shifted to workers with hyperdrive. But still my DB is neon postgres only , for that free tier is not sufficient if I run cron jobs.
Soon I'll take workers 5$ plan as well. But before that I just wanted to see if there anything more better for my requirement.
2
u/NiceFirmNeck 4h ago
You would check out Supabase as a backend. Since you already use PostgreSQL, I don't think it'll be hard for you to migrate. You also get Auth, API, Serverless, S3 and more. You might be able to get away with free tier.
(I don't work for Supabase)
2
u/Longjumping_Ad_9510 16h ago
Railway is quite cheap and easy to setup. Lately have had a couple major outages that took hours to resolve. Workers are neat depending on your use case. I use a combo of both but am moving off railway to AWS. Check out light sail too. It’s quite affordable and not too hard to setup.
1
1
u/Kooky_Difference3104 17h ago edited 16h ago
u/RemindMeBot 1 week
1
u/RemindMeBot 16h ago edited 10h ago
I will be messaging you in 4 days on 2026-09-07 18:30:42 UTC to remind you of this link
1 OTHERS CLICKED THIS LINK to send a PM to also be reminded and to reduce spam.
Parent commenter can delete this message to hide from others.
Info Custom Your Reminders Feedback
1
1
u/Bubbly_Orange_3502 9h ago
Workers breaks on the Postgres part. Each request runs in a fresh isolate so there is no long lived pool, and you end up putting Hyperdrive or a HTTP driver in front. Render and Railway just hold the pool.
1
1
u/Outside-Newt-897 1h ago
I'm using a VPS currently, because it's definitely cheaper, but of course a VPS requires more work when setting it up
1
u/thekwoka 39m ago
for this kind of "serverless" thing, Cloudflare workers will be the choice.
Basically anything that you need that is outside the limits of cloudflare worker, a VPS will be a very attractive option.
1
u/thekwoka 33m ago
Are you REALLY bound to postgres?
Cloudflares SQLite dbs are great, and you can likely just change the driver behind your apis to use that instead.
1
1
u/AggravatingGarlic753 6h ago
For a small production app, I’d probably lean Railway if the goal is keeping the architecture simple and predictable. Cloudflare Workers are really compelling for edge-heavy workloads, but once you have a conventional API + database + background jobs setup, I’d rather optimize for simplicity first. The DB location/latency would probably be my deciding factor more than the hosting brand itself.
1
12
u/TheLastNapkin 16h ago
Cloudflare workers is the best bang for your bucks but has serious considerations in how your processes work that you should take into account before opting in to it.
It can be very cheap while having tons of benefits having your deployments be almost entirely using cloudflare but you really should understand what you need from it and how you would use it with your stack.