Turso

active

by Turso (ChiselStrike Inc.) · since 2023 · also known as Turso Cloud, ChiselStrike

Managed SQLite-compatible cloud for database-per-tenant apps, with embedded replicas and offline sync.

relationaldocumentvectormanaged serviceproprietarygrowing

Overview

Turso is the managed cloud from the company behind libSQL and the Rust rewrite of SQLite now called Turso Database. It hosts SQLite-compatible databases that you reach over HTTP or WebSockets, or sync into an embedded replica inside your application for microsecond local reads and offline writes. Pricing and limits are built for very large numbers of small databases, so per-user or per-tenant databases are the intended pattern, and the free plan includes 100 databases and 5 GB. In 2026 the cloud began previewing MVCC-based concurrent writes from the new engine, which lifts SQLite's classic single-writer bottleneck. It fits mobile, edge and agent workloads well, but not large shared OLTP databases.

Strengths & trade-offs

Strengths

  • +Cheap to run thousands of databases, ideal for database-per-tenant
  • +Embedded replicas give in-process read latency and offline writes with sync
  • +Native vector search inside SQLite-compatible databases
  • +Point-in-time restore and database branching from a timestamp
  • +Generous free plan and low entry price

Trade-offs

  • −Individual databases are small and single-writer outside the concurrent-writes preview
  • −SQLite dialect lacks stored procedures, rich types and roles
  • −Two engines (libSQL and Turso Database) in transition can confuse feature support
  • −Not suited to large shared analytical or OLTP datasets

Great for

  • +Per-user or per-tenant databases for SaaS
  • +Local-first mobile and desktop apps with sync
  • +AI agents that each get an isolated database
  • +Edge-rendered sites needing low-latency reads

Think twice for

  • −One large multi-terabyte OLTP database
  • −Heavy concurrent writes to a single database
  • −Workloads needing Postgres extensions or stored procedures

Capabilities

Native or official first-party support · 14 of 25 tracked

✓Transactions
✓Joins
✓Secondary indexes
✓Full-text search
✓Vector search
✓JSON
✓Change data capture
✓Triggers
✓Durable persistence
✓Encryption at rest
✓Time travel
✓Branching
✓Offline sync
✓Runs in WebAssembly
–Geospatial
–Stored procedures
–Materialized views
–TTL / expiry
–Pub/Sub
–Columnar storage
–In-memory
–Compression
–Role-based access
–Online schema changes
–Streaming ingest

Scale & consistency

Comfortable data size
Small · ≤ 100 GB
Horizontal scaling
Manual
Multi-region
Read replicas
Transactions
Full ACID
Consistency
Strong, Eventual
Schema
Strict
Architecture
Serverless, Primary replica, Embedded
Query languages
SQL

Scales by number of databases (database-per-tenant) rather than size of one database; embedded replicas push reads into the app process.

Deployment

Self-hosted Vendor-managed cloud Serverless Embedded Edge Kubernetes operator

available on · AWS · Fly.io

Ecosystem

compatible withSQLite
apis & protocolslibSQL remote protocol (HTTP/WebSocket), Platform REST API, SQLite C API (embedded)
client languagesJavaScript, TypeScript, Python, Go, Rust, Swift, Kotlin, PHP

Alternatives to Turso

Compare all→
Cloudflare D1Relational5.8

Serverless SQLite for Cloudflare Workers, priced per row read and written, with read replicas and time travel.

turso vs cloudflare-d1 →
Turso Database (Limbo)Relational24.1

Ground-up Rust rewrite of SQLite with concurrent writes, async I/O, CDC and vector search.

turso vs turso-database →
libSQLRelational29.1

Turso's open-contribution SQLite fork with native vectors, a network server and embedded replicas.

turso vs libsql →
SQLite CloudRelational13.8

Managed, distributed SQLite with pub/sub, edge functions and CRDT sync to on-device databases.

turso vs sqlite-cloud →
NeonRelational30.4

Serverless Postgres with copy-on-write branching and scale-to-zero, now part of Databricks.

turso vs neon →
PowerSyncRelational23.3

Sync engine that keeps on-device SQLite in sync with Postgres, MongoDB, MySQL or SQL Server.

turso vs powersync →

Turso FAQ

What is Turso?

Turso is a relational database by Turso (ChiselStrike Inc.), first released in 2023. Turso is the managed cloud from the company behind libSQL and the Rust rewrite of SQLite now called Turso Database. It hosts SQLite-compatible databases that you reach over HTTP or WebSockets, or sync into an embedded replica inside your application for microsecond local reads and offline writes. Pricing and limits are built for very large numbers of small databases, so per-user or per-tenant databases are the intended pattern, and the free plan includes 100 databases and 5 GB. In 2026 the cloud began previewing MVCC-based concurrent writes from the new engine, which lifts SQLite's classic single-writer bottleneck. It fits mobile, edge and agent workloads well, but not large shared OLTP databases.

Is Turso open source?

No. Turso is proprietary, closed-source software.

Does Turso support ACID transactions?

Yes. Turso supports full ACID transactions, with strong, eventual consistency.

Does Turso scale horizontally?

Turso has no built-in sharding; scaling out means partitioning data in your application. It is comfortable at small scale (≤ 100 GB). It supports cross-region read replicas.

How can I run Turso?

You can embed it in your application, use the vendor's managed cloud, run it serverless and run it at the edge. Managed offerings include Turso Cloud. It is available on AWS and Fly.io.

What is Turso best for?

Turso is a strong fit for per-user or per-tenant databases for SaaS; local-first mobile and desktop apps with sync; and AI agents that each get an isolated database. Think twice for one large multi-terabyte OLTP database.

What are the best alternatives to Turso?

Common alternatives to Turso include Cloudflare D1, Turso Database (Limbo), libSQL, SQLite Cloud and Neon. The right choice depends on your workload, scale and hosting; WhichDB's smart match ranks them against your requirements.

How popular is Turso?

Turso ranks #297 of 844 databases on the WhichDB Score (10.6/100), and #94 among relational databases. The score combines public adoption signals such as package downloads, GitHub activity, job posts and developer discussion.