Building a Local-First Tauri App with Drizzle ORM, Encryption, and Turso Sync

Building a Local-First Tauri App with Drizzle ORM, Encryption, and Turso Sync I've been building desktop apps with Tauri for a while now, and one thing that consistently caused friction was the database layer. Tauri's official @tauri-apps/plugin-sql gets you SQLite, but it has no encryption support and no Drizzle integration that actually works inside a WebView. So I built my own plugin — tauri-plugin-libsql — and this post covers why I built it, the design decisions I made, and a few genuinely weird bugs I ran into along the way. The Problem with Databases in Tauri Tauri apps run your UI in a WebView. That WebView is essentially a browser — it has no Node.js fs module, no native bindings, no ability to open SQLite files directly. All access to the filesystem has to go through Tauri's IPC layer: your TypeScript code calls invoke() , and a Rust command handler does the actual work. The official plugin, @tauri-apps/plugin-sql , handles this. It's fine for basic use. But I kept running in