So you don't have a redundant server until $1marr?
That means you also don't apply updates to the server/kernel that require a reboot until then? Or you accept the downtime? And what happens if it doesn't boot properly?
None of that is an issue depending on what your software actually does. Now sure if you're doing something like logging, or you're cloudflare, or meta or some shit then yeah it's not going to cut it.
Generally I target enterprise b2b customers, they use the application from 9-5 generally. Weekly scheduled downtime is not the end of the world.
If it doesn't boot properly, which has never happened, I build a new server - takes 10 minutes max. Litestream keeps database relatively fresh, so it gets pulled on boot. Floating IP points at new server. We do this in dev regularly, the only difference in prod is a few variables.
Even if your target is higher uptime or bigger scale, you can go far further than you think on sqlite - it's multitudes of magnitude quicker than postgres for most general use cases.
Most software projects go nowhere. YAGNI. Build something valuable and people will put up with bullshit for a while.