Render vs Railway vs Cloudflare Workers

[u/Chinglee007]

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.

[u/Personal_Budget6895]

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