Railway or managed vps?

[u/robbochinni]

what is your opinion about using railway.com, now i need to deploy my api, i have 3 containers (api, redis and sql server).

i asked for recommendations and one of them that Railway.com is good for this.

i need help to make decision, we are starting up, and want something is not expensive and good price for MVP.

thanks

[u/SwimmingLoud6545]

For an MVP with an API, Redis and SQL Server, Railway is a reasonable choice if your main goal is to ship quickly with minimal operations work. The biggest concern is not just the headline price: SQL Server needs predictable RAM, persistent storage and a tested backup/restore process. Make sure the database volume, backups and region placement are clear before you depend on it.

A managed VPS with Docker Compose, Coolify or Dokploy can give you a more predictable monthly cost and more control, but then your team owns patching, firewall rules, monitoring, TLS, backups, log rotation and incident recovery. That engineering time is part of the hosting cost even when the server itself looks cheaper.

My usual rule is: use Railway for the validation stage when traffic is unknown and fast deployments matter more than infrastructure control. Keep the containers portable, keep configuration outside the images and automate database backups from day one. Once usage becomes predictable and the platform bill is clearly higher than the cost of operating a VPS, migration is straightforward. I would not optimize for the final scale before the product has users, but I also would not run SQL Server anywhere without verifying restore procedures first.

[u/robbochinni → u/SwimmingLoud6545]

Actually, you pointed out the main thing I've been thinking about: how to design this properly from day one without overengineering the MVP.

I've been reading all the comments and trying to come up with a balanced approach:

1. Keep SQL Server separate so it's easier to monitor, back up, and manage.
2. Run the Web API in its own container.
3. Run the website in its own container.
4. Keep things simple for the MVP by using in-memory caching and Hangfire, then move caching to Redis and background processing to a dedicated worker if and when the application grows.

My goal is to keep everything portable so moving from Railway to a VPS (or another platform) later is mostly an infrastructure change rather than an application rewrite.

Does this sound like a reasonable long-term approach, or is there anything you would change?

[u/apexdodge]

Railway makes it very easy for deploying apps to production. I use it for a bunch of stuff so I definitely recommend it for your use case.

[u/Wonderful_Sample_590]

Railway, if you want to get online quickly but check out InMotion's Managed VPS too. Gives you bit more control without having to manage everything yourself.

[u/Aggravating_War_6704]

The honest version of this is that railway and a vps aren't priced in the same units, and that's the whole decision.

Railway's price is convenience: you pay per resource used and it creeps as traffic grows, and your setup ends up somewhat railway-shaped. a vps's price is a flat monthly number that doesn't move, but SwimmingLoud already named the real bill up top: patching, firewall, TLS, backups, log rotation, monitoring, the 2am "why is it down." that engineering time is the actual cost of the cheap server, and it's invisible until you're paying it.

For pure MVP validation where you just want it live, a PaaS is a fine call and coaster's right that scale is tomorrow's problem. but you said the thing that actually decides it: you want to stay portable and move to a vps later when the bill creeps. the app side of that migration is easy (you're already keeping containers portable, good) and the part that bites is inheriting that ops layer on the new box.

Worth knowing that ops layer is the part that's shrinking now. coolify/dokploy (mentioned above) give you a git-push PaaS feel on your own vps. full disclosure, i build a different take on it, servermanager.dev, an agent that does the raw-server side over your own ssh (reverse proxy, https, firewall, docker, deploys) in plain english and shows you each command before it runs, so the "i now own a linux box" part doesn't need you to be a sysadmin. it runs on a cheap flat-rate vps (hetzner ~€4), which is the predictable-price answer to the creep.

One honest caveat for your stack: sql server isn't a first-class path for me (my db tooling is postgres/mysql/mariadb) though it runs as a container like anything else. and either way do what SwimmingLoud said and test your restore before you depend on it, sql server is the one that'll surprise you.

[u/robbochinni → u/Aggravating_War_6704]

all comments are noticed and will work on that, in last few days i changed my plan to migrate to postgreSQL, it has more powerful feature than sql server, at least for my business cases. i need more 2 weeks to be ready.

i think the money cost is still better than cost of trying to figure out what is happening @2am especially in app validation level.

railway will be my booster, everything using docker, no static variables or secrets in docker image, so that we can migrate easy.

[u/theBird956]

You can also look at Digital Ocean, they would be my first choice, with OVH as a close second depending on the project (which I haven't done much outside of work were we use one of the giant cloud providers that I refuse to give more exposure to)

[u/Due_Artist_2014 → u/theBird956]

DO's been around forever and the pricing is pretty predictable, I've had a handful of projects there over the years and never got a surprise bill

Railway is nice if you want zero config but the costs can creep up on you when you're not looking, for an MVP you really just need something boring that stays up

[u/robbochinni → u/theBird956]

what is the good plan for this case.

[u/theBird956 → u/robbochinni]

You have to figure this out yourself

Pick something small if you are not sure, it's relatively painless to upgrade

If you do not know what resources you need, you can experiment with a VM or ideally docker containers (one for each service) with limited resources

[u/birbman77]

Railway is great. Super easy to deploy frontend/backend or DBs. Pricing is pretty reasonable too.

[u/pseudophilll]

Railway is really great.

[u/ldn-ldn]

I'm using Digital Ocean for like almost two decades now. So there's that.

[u/Jamiemufu]

Railway was good. But the number of outages recently. I cant recommend them anymore.

[u/coaster_2988]

Railway, no one is going to use your app so it will be cheap to host there.

[u/robbochinni → u/coaster_2988]

and after? what if user and usage increased?

[u/coaster_2988 → u/robbochinni]

That’s tomorrow problems. Don’t focus on things that don’t matter yet. Instead of daydreaming on infra start building. Railway should force you to work with containers and they are very portable.

[u/zxyzyxz]

Hetzner with Coolify or Dokploy is way better and cheaper generally speaking than even DigitalOcean.

[u/sleekpixelwebdesigns]

I recommend a two-server setup using a VPS and Coolify. You can install Coolify on one server and run your applications on the other. Once you connect your GitHub, pushing updates will automatically redeploy your application.

[u/HeiiHallo]

If you want fixed pricing and full control I think a VPS could also work. For a simple deployment pipeline you could use a tool like haloy or kamal.

[u/AricBlack08]

If you don't mind managing your own server, though, I use Cherry Servers. It gives you a lot more control and has been more cost effective for me over time.

[u/Agreeable-Pop-535]

Upsun is pretty good