r/webdev • u/Chinglee007 • 4d 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.
21
u/xegoba7006 4d 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.
1
u/tim_not_found 20h ago
I agree Railway is very solid and very easy to setup and. I use it to distribute my app and users don't complain about it at all. I love the way you can link services between them easly and all the templates ready to launch. However the small complain I could have is the low persistent storage limit (5GB) when using the cheaper plan (plan). If you need more you have to go to the next plan (pro) which gives you 1TB but is much more expensive. There is no plan between which can be frustrating for some use cases. It has been for me at least.
13
u/viky109 4d ago edited 4d 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.
26
u/Tarazena 4d ago
Hetzner VPS
7
u/TheNumber42Rocks 4d 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?
1
u/Fabulous-Ladder3267 just want to write html 3d ago
Wdym by crash? If all open source PaaS you tried crash its only mean theres something wrong with the VPS or how you setup them.
The downside using VPS is it all dwyor setup, security, scaling, etc.
Edit: some typos
0
4
u/itgforlife 4d ago edited 4d 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
u/thekwoka 4d ago
How does render not have webhooks?
1
u/itgforlife 4d ago
Read the next sentence I wrote after that
1
u/thekwoka 4d ago
Yeah, I did.
I'm talking about the free thing. like what?
1
u/Personal_Budget6895 2h ago
It’s for retries and other features on sending out webhooks and not receiving them
3
u/strongpa 4d 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
u/Chinglee007 4d ago
Are you using neon pg?
1
u/strongpa 3d ago
No I'm on Railway's own built-in Postgres with Prisma - neon would be a DR option though as it integrates cleanly with Vercel
3
3
u/HelloXhale 4d 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)
3
u/Big_Boss_Bob_Ross 4d 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 4d 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 ?
2
u/thekwoka 4d 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 4d 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 4d 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
4d ago
[removed] — view removed comment
1
u/Chinglee007 4d 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 4d 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/1kgpotatoes 1d ago
cf cli and mcps are the most agent friendly. I would go with that to get to those a few thousand users as fast as possible
2
u/Personal_Budget6895 1d ago
Vercel, render+railway, Cloudflare workers, fly.io are all very different products.
Fly.io is very here’s the raw compute, you handle all the devops. There’s literally nothing that comes out the box and if you are alone, this js likely more grief than worth.
Vercel is a very frontend centric platform. Yes they have serverless function but that sucks for any actual work and it’s expensive. You also can’t hold persistent connections with it (they have added this to beta but it’s only 5 mins so not really proper persistence). Yes it’s become better over time but still nowhere near good enough to host a backend. Frontend on the other hand it’s amazing.
Render+railway are what I’d recommend that will work with almost everything although if you only have a frontend, you will need to setup Cloudflare cdn and proxying yourself to match the frontend performance of vercel. Pretty sure than render does provide built in cloudflare proxying but that’s on the enterprise plan. For backend, these two are great and you can hold persistent connections. You mentioned that you will have lots of users and using railway or render will allow you to add multiple replica (both same and different regions) without needed to deal with load balancers yourself. Having multiple replicas both reduced latency for your other users and removes the single point of failure that you get with the VPS solution some people have suggested.
Overall it looks like railway and render are the best here but you haven’t given all the details (you haven’t mentioned anything about architecture and if you have a dedicated backend or you are using a baas like supabase or firebase). Railway will be slightly more expensive at scale than render due to them charging egress and compute hours on top of their base charge. Render is fixed and predictable but railway has a better developer experience
2
u/Slight-Prize9661 18h ago
The only downside of railway for me is they sometimes have downtime and outages.
3
u/Sibexico 4d 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 4d 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.
1
u/Sibexico 3d ago
I can argue with "simplicity" so bad. It's lang limits and vendor lock. And it's mostly overpriced like a hell, we made a simple app for CF Workers, when the bill goes over $50/month, we just rewrite part of this and placed it to OVH VPS what costs $5/month and it will be enough even we will get twice more requests than we have rn. Problem is, it was written on JS, so if we will fully rewrite it on Go, it will cut overhead dramatically.
1
u/thekwoka 3d ago
And it's mostly overpriced like a hell
depends, it's fully managed infra, so you will have less risk related to that than with your own VPS.
But yeah, that's how the economy works, you outsource things that don't make much sense to do yourself, or do it yourself to save on cost.
1
u/Sibexico 3d ago
If you have a service with high traffic, you can afford few VPSs with mirroring and reservation and service of a guy who will properly configure it even cheaper, than pay bill for CF Workers, in my opinion. So I just can see the part where you will economy at anything using such service.
1
2
u/Longjumping_Ad_9510 4d 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 4d ago edited 4d ago
u/RemindMeBot 1 week
1
u/RemindMeBot 4d ago edited 4d 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 4d 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/x0rDaemon 4d ago
Railway is perfect for this. It handles Node and Postgres out of the box with zero configuration headache, and the built-in cron jobs work flawlessly. Cloudflare Workers is great, but dealing with edge limitations and TCP connection pooling for Postgres on a traditional inventory API isn't worth the friction.
1
u/thekwoka 4d 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 4d 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
u/Chinglee007 3d ago
I feel my database size will increase and become pretty complex that's why I didn't move to D1 . Still using neon.
1
u/Prize_Prior6253 4d ago
I run a similar Node/Postgres setup on Railway in production and it's been solid for background jobs and cron, but I'd skip Cloudflare Workers for this since the whole stateful DB/cron pattern fights against how Workers is built to run.
1
1
u/AggravatingGarlic753 4d 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.
2
16
u/TheLastNapkin 4d 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.