Give each of your users their own SQLite database

Blogs

Journey from multi-tenant to SQLite single-tenant architecture, inspired by DHH's vision. DHH argues in this post that the complexities in modern web services come from the need for a single system to accommodate serving a multitude of users.

Visit Site

Blogs Turso

BlogsHow Poke Gives Every User Their Own Database, Without Them Ever KnowingTurso BlogsReplicate my *entire* production database? You must be mad!Turso BlogsStoring Vercel's AI SDK chat messages in a Turso databaseTurso BlogsReplacing Kafka with… SQLite?Turso BlogsBatches in SQLiteTurso BlogsSQLite Encryption in Production: Key Management, Migration, and Real-World Use CasesTurso BlogsNew team management and improved invoicing with Netlify Enterprise Grid planNetlify BlogsEnhancements to Honeycomb Telemetry Pipeline Deliver Greater Visibility, Smarter Control, and LowerHoneycomb BlogsThe Fast Path to More Useful TelemetryHoneycomb BlogsGotta Go SlowHoneycomb BlogsHoneycomb Acquires Grit and Expands Leadership Team to Accelerate Customer Value and EnterpriseHoneycomb Products & ServicesNew in GitBook: Upgrade your public docs with powerful new customization toolsGitbook BlogsAWS PrivateLink for Neon Databases - NeonNeon BlogsMeet BaseHub: Developer Velocity And Efficiency Right Down to The Database - NeonNeon Blogsxpander.ai Brings AI Agents to Slack, With Neon Powering the Backend - NeonNeon BlogsTest Your Database Without Mocks - NeonNeon BlogsWhy Invenco Migrated From Aurora Serverless v2 to Neon - NeonNeon BlogsRun Product Analytics on Your Neon Data Using Fabi.ai - NeonNeon BlogsUsing Windsurf Cascade and Neon MCP for Agent-Driven Database Interaction - NeonNeon BlogsPivoting Your Career Without Starting From ScratchSmashingmagazine