Multi-Tenant Data Isolation in SQLite: Per-User Database Files vs Row-Level (opens in new tab)

When you build a multi-tenant SaaS, the first big architectural decision is how to isolate tenant data. With Postgres, the question is usually "shared schema with tenant_id, schema-per-tenant, or database-per-tenant." With SQLite, the trade-offs shift because the operational characteristics are completely different. For HelperX, we went all the way to one SQLite database file per tenant instead of using row-level isolation. A year later it's the design decision I'd most strongly defend. This ...