Open-Source Databases · tursodatabase

turso

Turso is an in-process SQL database written in Rust that provides SQLite compatibility while adding modern features like multi-version concurrency control (MVCC), change data capture, and vector support. It runs on multiple platforms including Linux, macOS, Windows, and WebAssembly, with bindings for Rust, JavaScript, Python, Go, Java, and .NET.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/tursodatabase/turso

22.7k

GitHub stars

1.1k

Forks

Rust

Primary language

MIT

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	tursodatabase/turso
Owner	tursodatabase
Primary language	Rust
License	MIT — OSI-approved
Stars	22.7k
Forks	1.1k
Open issues	774
Latest release	v0.6.1 (2026-05-22)
Last updated	2026-07-08
Source	https://github.com/tursodatabase/turso

What turso is

A Rust-based embedded SQL database implementing SQLite wire protocol and file format compatibility, enhanced with BEGIN CONCURRENT for MVCC-based write concurrency, async I/O via io_uring on Linux, and optional encryption at rest. Features include CDC streams, vector search capabilities, and experimental full-text search via tantivy integration.

Quickstart

Get the turso source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/tursodatabase/turso.git2cd turso3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

WebAssembly and browser-based applications

Turso compiles to WebAssembly, enabling embedded SQL databases directly in the browser for offline-first and edge compute scenarios without server-side database dependencies.

Multi-language polyglot environments

With official bindings for Rust, JavaScript, Python, Go, Java, and .NET, Turso simplifies database integration across heterogeneous tech stacks without requiring database abstraction layers.

Real-time data synchronization workflows

Built-in change data capture (CDC) enables real-time streaming of database mutations for event-driven architectures, analytical pipelines, and cross-service synchronization.

Implementation considerations

Beta software—establish internal testing protocols and verify experimental features (encryption, incremental computation, FTS) against production requirements before deployment.
MVCC via BEGIN CONCURRENT is non-standard SQL; applications using traditional SQLite transaction isolation must review query logic for correctness under new concurrency model.
WebAssembly binding works in browsers but carries the usual wasm constraints: bundle size, initial load time, and browser storage quotas; verify performance profiles for target use case.
Vector support is included but vector indexing is still on the roadmap; confirm whether exact vector search meets performance SLAs before committing to production.
Multi-process WAL coordination via `.tshm` sidecar is experimental; thoroughly test cross-process scenarios if your application shares database files across multiple processes.

When to avoid it — and what to weigh

Production-critical systems requiring maximum stability — Project explicitly marked BETA with 774 open issues; unsuitable for mission-critical workloads without extensive internal testing and operational maturity validation.
Large-scale distributed multi-node clusters — Turso is an in-process database; it does not provide native distributed replication, sharding, or cluster coordination—use traditional distributed databases for horizontally scaled systems.
Applications requiring mature ecosystem tooling — Unlike SQLite (decades-old), Turso lacks mature query planners, advanced indexing strategies, and battle-tested production observability—experimental features (encryption, incremental computation) are explicitly marked unstable.
Scenarios with strict compliance and security audits — Beta status and experimental encryption mean formal security audits, compliance certifications (SOC 2, FedRAMP, etc.), and long-term support contracts are unknown; requires direct vendor verification.

License & commercial use

Licensed under MIT (MIT License), a permissive OSI-approved license allowing commercial use, modification, and distribution with minimal restrictions (preservation of copyright and license notice required).

MIT license permits commercial use without restrictions. However, project is in BETA with explicit stability warnings; commercial adoption requires internal risk assessment, testing, and contingency planning for potential breaking changes or bugs in future releases.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	Low
DEV.co fit	Good
Assessment confidence	High

Security considerations

Encryption at rest is experimental and unaudited; do not assume production-grade data protection. No security disclosure policy, audit reports, or known CVE tracking visible. Beta status means unknown vulnerability surface. Async I/O on Linux and WAL multi-process coordination add complexity—review for side-channel and race condition risks if handling sensitive data.

Alternatives to consider

SQLite (native C library)

Mature, battle-tested, zero dependencies; lacks Turso's MVCC, CDC, and vector features but offers proven stability and extensive tooling for production systems.

DuckDB

Another Rust-based embedded SQL engine with strong analytical query support, column-oriented storage, and Parquet integration; better for OLAP workloads, less suitable for transactional write concurrency.

libSQL (Turso's predecessor/related project)

If you require vector search infrastructure and distributed cloud database capabilities, Turso Cloud (commercial) or libSQL ecosystem may offer managed hosting alternatives.

Software development agency

Build on turso with DEV.co software developers

Turso is best suited for WebAssembly, multi-language, and real-time data sync scenarios. Review the BETA stability warnings, test vector and CDC features, and verify encryption maturity before committing to production.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

libsql sqlx sqlsync

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source Databases AI Application Development Web App Development API Development Talk to DEV.co

turso FAQ

Is Turso a replacement for SQLite?

Turso is compatible with SQLite's SQL dialect and file format but adds features (MVCC, CDC, vectors). It is an in-process database like SQLite, not a server; not a drop-in replacement for all use cases.

Can I use Turso in production?

Turso is in BETA; the project explicitly warns of potential bugs and unexpected behavior. Production use requires internal testing, risk acceptance, and backups. No commercial SLA or support is advertised.

What is the performance overhead vs. SQLite?

Not documented in the provided data. Benchmarks comparing Turso to SQLite on read/write throughput, memory, and latency are unknown; requires vendor documentation or independent testing.

How do I encrypt my database?

Turso offers experimental encryption at rest, but it is unaudited and not recommended for compliance-critical scenarios. Verify security requirements with the Turso team before deployment.

Software developers & web developers for hire

Need help beyond evaluating turso? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source databases integrations — and maintain them long-term.

Ready to evaluate Turso for your project?

Talk to DEV.co Schedule a Consultation