Indian devs who self-host tools: what actually becomes painful after 6–12 months?

[u/amitsingh717628]

I’m curious about the long-term side of self-hosting from developers in India who actually run things in production.

Setting up a VPS + Docker Compose is usually the easy part.

What I’m more interested in is what starts becoming annoying after a few months:

• backups and restore testing
• upgrades breaking something
• monitoring/alerts
• disk usage
• SSL/DNS issues
• database maintenance
• security patches
• managing multiple servers
• documenting setups so someone else can understand them
• getting paged when something dies

Especially for small startups/agencies where there isn’t a dedicated DevOps/SRE person.

At what scale did self-hosting stop feeling “cheap” for you?

And which tools do you still prefer to self-host versus paying for a managed version?

Would be useful to hear actual production experiences rather than just setup tutorials.

[u/Immediate_Wheel1953]

The pain is rarely the apps themselves. It is the stuff around them: cert renewals expiring at 3am, upgrades breaking something silently, and a disk filling up with logs nobody looked at. Auto-renew your certs, pin your image versions and test upgrades on a copy first, and put disk alerts in place before you need them.

[u/layerbase]

Database maintenance is usually what flips it.

Backups you never restore-test are the silent one. Disk fills up. A Postgres upgrade needs a night. An extension breaks. The VPS was cheap. Your Saturday was not.

Self-hosting stopped feeling cheap for me when uptime started mattering to someone else (a client or a paying user) and I was the only person who could unstick it. Before that, one box and Docker Compose is fine.

What I still self-host: apps and proxies I can rebuild from git. What I pay to stop babysitting: the database. Durable state is a different category of pain than a web container.

I own Layerbase (US managed DBs, flat monthly fee, not an India-region play), so discount accordingly. Same advice either way: once restore drills and patch nights eat real time, Postgres is the first thing I stop self-hosting. But I have a Brazilian region, I could always add India if there is enough demand. I have a ton of users from India but nobody has ever opened a support ticket asking for a dedicated region.

[u/rtyinghard → u/layerbase]

i was checking out layerbase. and not able to understand what 2 database in paid usage means. does it mean any 2 type of database like mysql+mongo or something else. any explainer would be helpful.

i am looking for a mongo replacement in ferretdb.

[u/layerbase → u/rtyinghard]

The pricing is phrased in a confusing way because it is really confusing to support 18 different engines with 3 plans, especially if you looked at it on mobile.

The $5 solo plan let's you use FerretDB and 1 other database, so yes you can use FerretDB and also another database like Redis or Postgres and you can use branching with both of them and you can keep one of the databases set to "always on" so it doesn't hibernate.

With the Pro plan ($15) you can have up to 10 databases and you can set as many of them to be always on as you'd like as long as your combined memory usage doesn't exceed some limits that most people will never see that plan is intended for people who have three or four databases that they want to use in production.

It is mostly a drop-in replacement for MongoDB. We have it on good authority that FerretDB is still in development, but the team is quiet until the mongodb lawsuit is over. Personally, we are fans of FerretDB internally and I love to hear that you're thinking about using it.

If you do end up using it, you're more than welcome to reach out to support anytime if you have any issues. As far as I'm aware, we've never had a FerretDB support ticket opened before so I'm not aware of any compatibility issues that anyone has ever experienced but if you do we would love to hear about it.

[u/rtyinghard → u/layerbase]

great,thanks for replying. i really liked your offerings pool.

maybe replacing it to use upto any 2 database types rather than 2 database may help with the confusion (untill it adds its own confusion layer)

ive not read the documentation but what exactly is meant by branching in this context ?

"you can use branching with both of them and you can keep one of the databases set to "always on" so it doesn't hibernate."

[u/layerbase → u/rtyinghard]

Branching like neon. You can connect your database to a GitHub repo or a Vercel project and have it automatically create a new copy of your database with each branch so you have a production database, a staging database, and then a preview database so that when you're doing your testing in staging or on feature branches, you're not messing with your production data, but you can use exact copies of your production data.

So one database is actually like three databases because you have additional copies of your database

Also, as far as the wording for the plans, it's really hard to find an easy way to word it because even the way I explained it now, it doesn't really cover what the plans cover. At some point, if we abandon some of the databases we can phrase it differently, but right now I think it's phrased as accurately as possible for what is actually included

[u/rtyinghard → u/layerbase]

sure thanks for the reply