November 2026 Summaries
6 posts from Turso
Filter
Month:
Year:
Post Summaries
Back to Blog
No summary generated yet.
Nov 16, 2026
2,298 words in the original blog post.
Turso and Neon address the growing need for agent platforms to create isolated databases for large numbers of agents, users, and tasks, but they use different underlying models: Neon provides each database as a Postgres project with dedicated, autoscaling compute, while Turso uses lightweight SQLite-compatible database files managed on shared infrastructure. The comparison argues that Turso’s storage-and-operations-based pricing, unlimited paid-plan databases, local-device synchronization, per-database encryption keys, and bring-your-own-cloud option are suited to short-lived, highly numerous agent workloads, whereas Neon’s compute-based projects and branching are well suited to creating complete copies of a Postgres-backed application environment. Both services support isolation and branching, but Neon imposes project limits that can be expanded through its Agent Plan, while Turso treats branches as additional databases under its unlimited-database model. Turso, now part of Supabase, positions its database offering alongside Supabase Postgres for workloads requiring Postgres features, while acknowledging that Neon may be preferable when agents need rapid replicas of an entire production backend including application data, authentication, and files.
Nov 12, 2026
2,154 words in the original blog post.
Turso Cloud BYOC is a deployment model that runs Turso’s managed, SQLite-compatible database platform inside a customer-owned AWS account, enabling organizations to keep database compute, object storage, data residency, and security controls within their own cloud environment while retaining Turso’s APIs and managed operational workflows. Designed for workloads that create large numbers of small, isolated databases—such as AI agents, users, tenants, applications, and devices—it uses a diskless architecture in which durable data resides in object storage and compute nodes can be replaced without data migration. The customer account hosts the data plane and database-management portion of the federated control plane, while Turso retains only billing, organization settings, and metrics, with no access to database contents or the ability to create, inspect, or delete databases. BYOC supports features including concurrent writes, customer-managed encryption keys, point-in-time recovery, and synchronization with local databases, allowing teams to move between hosted Turso Cloud and BYOC without changing application code. It targets AWS-based deployments rather than conventional on-premises environments and is positioned for agent platforms, enterprise SaaS, regulated workloads, and connected device fleets that require both large-scale database-per-entity isolation and customer-controlled infrastructure.
Nov 11, 2026
1,697 words in the original blog post.
Turso Database, an open-source SQLite rewrite in Rust that is joining Supabase, introduces built-in change data capture (CDC) that records row-level inserts, updates, deletes, transaction commits, and schema changes without requiring triggers or direct WAL parsing. CDC moves downstream work such as cache invalidation, search indexing, webhooks, analytics, and audit logging out of application request paths by exposing changes in an ordered table stream, while preserving transaction boundaries through shared transaction IDs and commit records. Capture is enabled per write connection with a PRAGMA and can store varying levels of detail, from row IDs to before-and-after row images and column-level updates. The feature addresses limitations of prior SQLite approaches, including trigger maintenance and performance costs, WAL decoding complexity, and non-durable hooks, but has early limitations involving schema evolution, unbounded change-table growth, and the need to enable capture on every writer. The post recommends a polling consumer that tracks durable watermarks, buffers changes until transaction commits, makes downstream operations idempotent to tolerate replay after failures, and prunes old records based on the slowest consumer’s offset.
Nov 05, 2026
1,964 words in the original blog post.
Turso Cloud has expanded to twelve AWS regions by adding Singapore and Frankfurt, improving latency for Southeast Asian applications and enabling German data residency for organizations that require data to remain in Germany. Turso is a managed, open-source SQLite-compatible database platform that stores each database as a file in object storage, allowing low-cost idle databases without cold starts and supporting a separate database for each AI agent, user, or tenant. This model can provide agents with isolated memory and action logs, support database branching and rollback for risky operations, and accommodate independently defined schemas. Database locations can be assigned per group within one account, enabling tenants in different countries to keep data near users or meet local requirements. The expansion is constrained to AWS regions that support S3 Express One Zone, which Turso uses for low-latency write-ahead-log storage, while Paris, Seoul, and Northern California remain planned possibilities.
Nov 04, 2026
590 words in the original blog post.
Sauna, a proactive workplace AI assistant launched in April 2026, uses Turso to provide separate databases for every user session, agent, inbox, and calendar connection, creating more than 2 million databases overall and roughly 90,000 each day. Its architecture combines Turso-backed conversation histories and locally synchronized connected-service data with an in-house memory system and searchable file system, enabling persistent context, faster searches, granular sharing controls, and individualized retention policies. After using Cloudflare Durable Objects and then SQLite with Litestream, Sauna adopted Turso when its pricing model removed active-database limits, citing improved performance, lower costs, and two-way database synchronization. Turso Sync lets Sauna perform reads and writes locally while replicating data to the cloud, helping it maintain service continuity across hosting providers and retain long-term chat histories affordably. Sauna plans to consider moving its file system to Turso and eventually experiment with multi-version concurrency control to support simultaneous writes from users and background agents.
Nov 03, 2026
1,927 words in the original blog post.