vs

Cloudflare D1 vs Turso

Cloudflare D1: Serverless SQLite for Cloudflare Workers, priced per row read and written, with read replicas and time travel. Turso: Managed SQLite-compatible cloud for database-per-tenant apps, with embedded replicas and offline sync.

key differences

  • Only Turso has vector search, change data capture, branching, offline sync, runs in webassembly.
  • Turso can run embedded in your application process.

choose cloudflare-d1 for

  • +Database-per-tenant SaaS on Workers
  • +Edge apps, blogs and CMS backends
  • +Configuration and feature metadata near users
  • +Prototypes needing SQL without managing servers

best at · OLTP, Edge, Content

choose turso 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

best at · OLTP, Edge, Embedded

overview
Primary model
Relational
Relational
Also supports
Document
Document, Vector
Type
Managed service
Managed service
Status
Active
Active
Developer
Cloudflare
Turso (ChiselStrike Inc.)
First release
2022
2023
Latest version
–
–
License
ProprietaryProprietary (Cloudflare service)
ProprietaryProprietary (cloud service; engines are MIT)
Free tier
✓
✓
popularity
WhichDB Score
5.8
10.6
Rank
#373
#297
GitHub stars
–
–
Stack Overflow questions
–
5
scale & guarantees
Comfortable data size
Small (≤ 100 GB)
Small (≤ 100 GB)
Horizontal scaling
Manual
Manual
Multi-region
Read replicas
Read replicas
ACID
Full
Full
Consistency
Strong, Causal
Strong, Eventual
Schema
Strict
Strict
Architecture
Serverless, Primary replica
Serverless, Primary replica, Embedded
deployment
Self-hosted
—
—
Vendor-managed cloud
✓
✓
Serverless
✓
✓
Embedded
—
✓
Edge
✓
✓
Clouds
Cloudflare
AWS, Fly.io
capabilities
Transactions
✓
✓
Joins
✓
✓
Secondary indexes
✓
✓
Full-text search
✓
✓
Vector search
—
✓
Geospatial
—
—
JSON
✓
✓
Change data capture
—
✓
Triggers
✓
✓
Stored procedures
—
—
Materialized views
—
—
TTL / expiry
—
—
Pub/Sub
—
—
Columnar storage
—
—
In-memory
—
—
Durable persistence
✓
✓
Compression
—
—
Encryption at rest
✓
✓
Role-based access
—
—
Time travel
✓
✓
Branching
—
✓
Online schema changes
—
—
Streaming ingest
—
—
Offline sync
—
✓
Runs in WebAssembly
—
✓
interfaces
Query languages
SQL
SQL
Client languages
JavaScript, TypeScript, Python, Rust
JavaScript, TypeScript, Python, Go, Rust, Swift, Kotlin, PHP
Best for
OLTP, Edge, Content, Coordination
OLTP, Edge, Embedded, Mobile/offline

Cloudflare D1 vs Turso: FAQ

What is the difference between Cloudflare D1 and Turso?

Cloudflare D1: Serverless SQLite for Cloudflare Workers, priced per row read and written, with read replicas and time travel. Turso: Managed SQLite-compatible cloud for database-per-tenant apps, with embedded replicas and offline sync. Only Turso has vector search, change data capture, branching, offline sync, runs in webassembly. Turso can run embedded in your application process.

When should I choose Cloudflare D1 over Turso?

Choose Cloudflare D1 for database-per-tenant SaaS on Workers; edge apps, blogs and CMS backends; and configuration and feature metadata near users. Choose Turso 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.

Is Cloudflare D1 or Turso more popular?

Turso ranks #297 on the WhichDB Score (10.6/100) and Cloudflare D1 ranks #373 (5.8/100). Popularity is not fit: check the requirements that matter for your project.

Are Cloudflare D1 and Turso open source?

No. Cloudflare D1 is proprietary, closed-source software. No. Turso is proprietary, closed-source software.