"You're using SQLite in production? For a SaaS?" — every developer who hears about our stack.
Yes. And after a year of running it with hundreds of active accounts, I'd make the same choice again. Here's why — and the specific patterns that make it work for multi-tenant workloads.
The architecture decision
HelperX manages multiple X accounts. Each account is an isolated "slot" with its own configuration, auth tokens, audit logs, and operational state. When we designed the data layer, we had two options:
Option A: Shared Postgres
