Turso

Concurrent writes on Turso Cloud entered early preview this period, removing the single-writer constraint that capped write-heavy SQLite workloads.

Simultaneous writes are open for early testing on Turso Cloud. The preview lets applications issue concurrent writes where only reads were previously concurrent — addressing a SQLite constraint that required serializing write access. Applications that serialized writes around a single connection can revisit that design while remaining on the SQLite storage model.

The new Rust CLI is shipping frequent pre-releases alongside stable CLI updates. Seven pre-releases (v0.8.0-pre.3 through pre.7) shipped in the window alongside the stable v0.7.2 release. The companion stable CLI reached v1.0.31 and v1.0.32: v1.0.31 added turso:// URL generation and export logging for Turso databases; v1.0.32 introduced TursoDB import support using an embedded Turso Go driver and removed the linux i386 build target.

Database-per-user and database-per-agent patterns are getting production case studies. A multi-tenancy at scale post covered the design rationale for giving every user a dedicated database. Two case studies added concrete examples: Poke uses a database-per-user model in a consumer app, and CTO.new runs tens of thousands of AI agents using a database-per-project model on Turso, with each project getting its own isolated database.

Guides cover offline-first database sync and switching from PostgreSQL and MySQL. A complete guide on offline-first database synchronization covers building local-first applications on Turso. A separate migration tutorial walks through switching from PostgreSQL and MySQL to SQLite, including guidance on when the move makes sense and how to approach the data transfer.