gives databases to everyone
summary
Claims a practical, scalable way to give every tenant an isolated SQLite database as a file so deletion, backup, and per-user encryption are single operations, built on a libSQL fork that adds replication and HTTP access and in-file vector embedding columns. Shows on-device replicas with zero network latency, idle databases costing effectively zero, performance targets like 200 terabytes, 2,000 writes/sec, 100,000 reads/sec, and compliance notes (SOC2, HIPAA) plus a 500‑database free tier.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:17OLAP vs OLTP explained
- 3:46Modern OLTP needs and compliance
- 5:09Multi-tenancy and why it matters
- 8:00Per-user database isolation benefits
- 10:48Cost efficiency of per-user DBs
- 12:14Scaling with SQLite and libSQL
- 15:04Turso architecture and local dev
- 17:50Pricing and community support
- 19:14Q&A
related talks
19mSQLite - The most overlooked database
30mUse SQLite in production
01h 07mSQLite
31mSQLite, the World's Most Ubiquitous Yet Little-Known Database
48mSQLite – The everywhere database
34mEdge & Offline-First App Data Management in 5G devices
23mFANTASTIC DATABASES AND WHERE TO FIND THEM
01h 56mSQLite on Rails: From rails new to 50k concurrent users and everything in between