I'm gearing up to launch my SaaS, and I've built the backend using FastAPI. I'm really torn between options for deployment. I was thinking about using a VPS with Coolify, Docker, and Better Auth, but honestly, I'm a bit nervous about managing everything. I have a full-time job, so I won't have daily time to maintain the server. Should I be worried about security, like data breaches or hacks?
On the flip side, I'm also considering managed services like Railway or something larger like AWS. However, I'm worried about their pay-as-you-go pricing leading to unexpected bills. I want to keep costs low while ensuring my data stays protected. What do you suggest?
3 Answers
Don't stress too much about VPS maintenance; it's pretty manageable for a small app. It does require some initial setup for security, but once that's done, you're looking at minimal upkeep.
If you're comfortable with tech, building it yourself might take slightly longer than using a managed service, but the control can be worth it. Dockerizing your application can help simplify the process too!
Honestly, I've had a great experience with Vercel and was considering Railway too. These managed services seem to have made a lot of developers feel like they can't manage things on their own anymore. But if you’re just running a small app, maintaining it on a VPS can be low-effort after the first setup.
You won't have to do much ongoing upkeep if it's done right.
I hear you! I worried about maintenance too, but it really feels feasible after setup.
Railway seems like a solid choice for your needs. It offers predictable pricing, which avoids the surprises you might get with AWS. Most early-stage SaaS projects run around $5-20 a month here, plus it has built-in Postgres support and deploys directly from GitHub—perfect for someone busy with a day job!
As for VPS with Coolify, once set up, the maintenance isn't that bad. You might only spend a couple of hours a month on admin tasks after the initial configuration. The key concern is getting it all set up right the first time.
On the GDPR front, just remember that you're still the data controller, no matter which auth provider you choose, and you need to consider where your data is hosted.
Thanks for breaking that down! That clarity on the GDPR stuff is really helpful!
I get the anxiety about liability too! It’s true, you remain responsible as the data controller regardless of the auth service you use. You're making it clearer for me.
That definitely sounds doable! Dockerizing will simplify everything—I'll need to try that!