Limbo is a project to build the next evolution of SQLite.
Find a file
Glauber Costa cb7c04ffad return error instead of panic for invalid syntax on views
I have accidentally typed "create materialized views", and noticed
that this panics, instead of returning an error. Fix it.
2025-09-19 03:59:28 -05:00
.cargo configure cargo for napi-rs 2025-08-08 15:45:05 +04:00
.github fix c compat tests and add a minimal CI 2025-09-18 10:13:31 +01:00
antithesis-tests antithesis: Drop experimental_indexes parameter from commect() 2025-09-05 13:17:39 +03:00
assets Add Nyrkiö to partners section in README 2025-07-10 04:54:24 +03:00
bindings remove mvvmode and set logical log as default 2025-09-18 18:22:25 +02:00
cli remove mvvmode and set logical log as default 2025-09-18 18:22:25 +02:00
core Implement JOINs in the DBSP circuit 2025-09-19 03:59:28 -05:00
docs Encryption support for database header page 2025-09-16 10:04:30 -04:00
extensions core/vtab: Mark VTabModuleImpl as Send and Sync 2025-09-17 11:48:42 +03:00
fuzz fix: add log with base to fuzzer 2025-09-18 13:09:39 -03:00
licenses fix tests and return nan as null 2025-03-29 14:46:11 +02:00
macros clean PR 2025-09-14 19:03:09 +07:00
packages/turso-serverless await on .close() 2025-09-10 13:42:21 +05:30
parser return error instead of panic for invalid syntax on views 2025-09-19 03:59:28 -05:00
perf remove mvvmode and set logical log as default 2025-09-18 18:22:25 +02:00
scripts fix update script 2025-09-12 17:03:04 +04:00
simulator remove mvvmode and set logical log as default 2025-09-18 18:22:25 +02:00
simulator-docker-runner Fix simulator and Antithesis Dockerfiles 2025-09-16 17:09:49 +03:00
sql_generation move as many dependencies as possible to workspace to avoid multiple versions of the same dependency 2025-09-15 17:19:36 -03:00
sqlite3 remove mvvmode and set logical log as default 2025-09-18 18:22:25 +02:00
stress stress: Retry sync on error to avoid a panic, take 2 2025-09-18 11:38:11 +03:00
sync/engine remove mvvmode and set logical log as default 2025-09-18 18:22:25 +02:00
testing Merge 'Compat: Translate the 2nd argument of group_concat / string_agg' from Iaroslav Zeigerman 2025-09-18 09:23:05 +03:00
tests mvcc: un-ignore mvcc fuzz test 2025-09-19 09:18:20 +03:00
vendored/sqlite3-parser move as many dependencies as possible to workspace to avoid multiple versions of the same dependency 2025-09-15 17:19:36 -03:00
whopper end sim test if the size exceeds soft limit 2025-09-19 12:56:47 +05:30
.dockerignore Add .dockerignore and Makefile commands to support docker 2025-07-31 00:00:44 -04:00
.github.json Add Jussi to .github.json 2025-01-14 18:37:26 +02:00
.gitignore Add target dir to .gitignore for perf subdirectories 2025-09-14 09:17:43 -04:00
.python-version setup uv for limbo 2025-04-15 12:45:46 -03:00
Cargo.lock run whopper with encryption if arg is passed 2025-09-17 21:58:27 +05:30
Cargo.toml move as many dependencies as possible to workspace to avoid multiple versions of the same dependency 2025-09-15 17:19:36 -03:00
CHANGELOG.md s/2024/2025/ 2025-09-10 16:39:11 +03:00
COMPAT.md Add AggValue instruction 2025-09-13 10:49:14 +02:00
CONTRIBUTING.md Update whopper run and explore scripts 2025-09-17 21:58:54 +05:30
dist-workspace.toml Update cargo-dist to the latest official version 2025-08-02 04:35:52 +09:00
Dockerfile.antithesis Fix Antithesis Dockerfile some more 2025-09-16 17:14:16 +03:00
Dockerfile.cli release and remove copies 2025-07-30 11:45:24 +02:00
flake.lock fix: update flake dependencies 2025-07-17 20:25:40 -03:00
flake.nix fix(flake.nix): added uv dependency to flake.nix 2025-08-17 21:49:24 -05:00
LICENSE.md rename Limbo to Turso in the README and other files 2025-06-27 15:44:40 -05:00
Makefile Add tracing_release feature for benchmarks to compile tracing macros to noops 2025-09-10 09:56:12 -04:00
NOTICE.md rename Limbo to Turso in the README and other files 2025-06-27 15:44:40 -05:00
PERF.md Update TPC-H running instructions in PERF.md 2025-08-25 17:43:42 -07:00
Pipfile Updated Pipfile 2024-07-12 13:07:34 -07:00
Pipfile.lock Added Pipfile and Pipfile.lock 2024-07-12 12:38:56 -07:00
pyproject.toml extract ruff lint rules to workspace 2025-06-20 15:59:03 -03:00
README.md Update README.md for Go documentation 2025-08-27 22:23:19 -04:00
rust-toolchain.toml chore: update rust to version 1.88.0 2025-07-16 19:17:58 +01:00
turso.png Rename Limbo to Turso Database 2025-06-26 21:05:02 +03:00
uv.lock Fix merge-py.py script to use github CLI and add makefile command 2025-07-31 10:20:17 -04:00

Turso Database

Turso Database

An in-process SQL database, compatible with SQLite.

PyPI PyPI PyPI

Chat with the Core Developers on Discord

Chat with other users of Turso (and Turso Cloud) on Discord


About

Turso Database is an in-process SQL database written in Rust, compatible with SQLite.

⚠️ Warning: This software is ALPHA, only use for development, testing, and experimentation. We are working to make it production ready, but do not use it for critical data right now.

Features and Roadmap

  • SQLite compatibility for SQL dialect, file formats, and the C API [see document for details]
  • Change data capture (CDC) for real-time tracking of database changes.
  • Language support for
  • Asynchronous I/O support on Linux with io_uring
  • Cross-platform support for Linux, macOS, Windows and browsers (through WebAssembly)
  • Vector support support including exact search and vector manipulation
  • Improved schema management including extended ALTER support and faster schema changes.

The database has the following experimental features:

  • BEGIN CONCURRENT for improved write throughput using multi-version concurrency control (MVCC).
  • Incremental computation using DBSP for incremental view mainatenance and query subscriptions.

The following features are on our current roadmap:

Getting Started

Please see the Turso Database Manual for more information.

💻 Command Line
You can install the latest `turso` release with:
curl --proto '=https' --tlsv1.2 -LsSf \
  https://github.com/tursodatabase/turso/releases/latest/download/turso_cli-installer.sh | sh

Then launch the interactive shell:

$ tursodb

This will start the Turso interactive shell where you can execute SQL statements:

Turso
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database
turso> CREATE TABLE users (id INT, username TEXT);
turso> INSERT INTO users VALUES (1, 'alice');
turso> INSERT INTO users VALUES (2, 'bob');
turso> SELECT * FROM users;
1|alice
2|bob

You can also build and run the latest development version with:

cargo run

If you like docker, we got you covered. Simply run this in the root folder:

make docker-cli-build && \
make docker-cli-run
🦀 Rust
cargo add turso

Example usage:

let db = Builder::new_local("sqlite.db").build().await?;
let conn = db.connect()?;

let res = conn.query("SELECT * FROM users", ()).await?;
JavaScript
npm i @tursodatabase/database

Example usage:

import { connect } from '@tursodatabase/database';

const db = await connect('sqlite.db');
const stmt = db.prepare('SELECT * FROM users');
const users = stmt.all();
console.log(users);
🐍 Python
uv pip install pyturso

Example usage:

import turso

con = turso.connect("sqlite.db")
cur = con.cursor()
res = cur.execute("SELECT * FROM users")
print(res.fetchone())
🦫 Go
go get github.com/tursodatabase/turso-go
go install github.com/tursodatabase/turso-go

Example usage:

import (
    "database/sql"
    _ "github.com/tursodatabase/turso-go"
)

conn, _ = sql.Open("turso", "sqlite.db")
defer conn.Close()

stmt, _ := conn.Prepare("select * from users")
defer stmt.Close()

rows, _ = stmt.Query()
for rows.Next() {
    var id int
    var username string
    _ := rows.Scan(&id, &username)
    fmt.Printf("User: ID: %d, Username: %s\n", id, username)
}
Java

We integrated Turso Database into JDBC. For detailed instructions on how to use Turso Database with java, please refer to the README.md under bindings/java.

🤖 MCP Server Mode

The Turso CLI includes a built-in Model Context Protocol (MCP) server that allows AI assistants to interact with your databases.

Start the MCP server with:

tursodb your_database.db --mcp

The MCP server provides seven tools for database interaction:

Available Tools

  1. open_database - Open a new database
  2. current_database - Describe the current database
  3. list_tables - List all tables in the database
  4. describe_table - Describe the structure of a specific table
  5. execute_query - Execute read-only SELECT queries
  6. insert_data - Insert new data into tables
  7. update_data - Update existing data in tables
  8. delete_data - Delete data from tables
  9. schema_change - Execute schema modification statements (CREATE TABLE, ALTER TABLE, DROP TABLE)

Example Usage

The MCP server runs as a single process that handles multiple JSON-RPC requests over stdin/stdout. Here's how to interact with it:

Example with In-Memory Database

cat << 'EOF' | tursodb --mcp
{"jsonrpc": "2.0", "id": 1, "method": "initialize", "params": {"protocolVersion": "2024-11-05", "capabilities": {}, "clientInfo": {"name": "client", "version": "1.0"}}}
{"jsonrpc": "2.0", "id": 2, "method": "tools/call", "params": {"name": "schema_change", "arguments": {"query": "CREATE TABLE users (id INTEGER, name TEXT, email TEXT)"}}}
{"jsonrpc": "2.0", "id": 3, "method": "tools/call", "params": {"name": "list_tables", "arguments": {}}}
{"jsonrpc": "2.0", "id": 4, "method": "tools/call", "params": {"name": "insert_data", "arguments": {"query": "INSERT INTO users VALUES (1, 'Alice', 'alice@example.com')"}}}
{"jsonrpc": "2.0", "id": 5, "method": "tools/call", "params": {"name": "execute_query", "arguments": {"query": "SELECT * FROM users"}}}
EOF

Example with Existing Database

# Working with an existing database file
cat << 'EOF' | tursodb mydb.db --mcp
{"jsonrpc": "2.0", "id": 1, "method": "initialize", "params": {"protocolVersion": "2024-11-05", "capabilities": {}, "clientInfo": {"name": "client", "version": "1.0"}}}
{"jsonrpc": "2.0", "id": 2, "method": "tools/call", "params": {"name": "list_tables", "arguments": {}}}
EOF

Using with Claude Code

If you're using Claude Code, you can easily connect to your Turso MCP server using the built-in MCP management commands:

Quick Setup
  1. Add the MCP server to Claude Code:

    claude mcp add my-database -- tursodb ./path/to/your/database.db --mcp
    
  2. Restart Claude Code to activate the connection

  3. Start querying your database through natural language!

Command Breakdown
claude mcp add my-database -- tursodb ./path/to/your/database.db --mcp
#              ↑            ↑       ↑                           ↑
#              |            |       |                           |
#              Name         |       Database path               MCP flag
#                          Separator
  • my-database - Choose any name for your MCP server
  • -- - Required separator between Claude options and your command
  • tursodb - The Turso database CLI
  • ./path/to/your/database.db - Path to your SQLite database file
  • --mcp - Enables MCP server mode
Example Usage
# For a local project database
cd /your/project
claude mcp add my-project-db -- tursodb ./data/app.db --mcp

# For an absolute path
claude mcp add analytics-db -- tursodb /Users/you/databases/analytics.db --mcp

# For a specific project (local scope)
claude mcp add project-db --local -- tursodb ./database.db --mcp
Managing MCP Servers
# List all configured MCP servers
claude mcp list

# Get details about a specific server
claude mcp get my-database

# Remove an MCP server
claude mcp remove my-database

Once configured, you can ask Claude Code to:

  • "Show me all tables in the database"
  • "What's the schema for the users table?"
  • "Find all posts with more than 100 upvotes"
  • "Insert a new user with name 'Alice' and email 'alice@example.com'"

Contributing

We'd love to have you contribute to Turso Database! Please check out the contribution guide to get started.

Found a data corruption bug? Get up to $1,000.00

SQLite is loved because it is the most reliable database in the world. The next evolution of SQLite has to match or surpass this level of reliability. Turso is built with Deterministic Simulation Testing from the ground up, and is also tested by Antithesis.

Even during Alpha, if you find a bug that leads to a data corruption and demonstrate how our simulator failed to catch it, you can get up to $1,000.00. As the project matures we will increase the size of the prize, and the scope of the bugs.

More details here.

You can see an example of an awarded case on #2049.

Turso core staff are not eligible.

FAQ

Is Turso Database ready for production use?

Turso Database is currently under heavy development and is not ready for production use.

How is Turso Database different from Turso's libSQL?

Turso Database is a project to build the next evolution of SQLite in Rust, with a strong open contribution focus and features like native async support, vector search, and more. The libSQL project is also an attempt to evolve SQLite in a similar direction, but through a fork rather than a rewrite.

Rewriting SQLite in Rust started as an unassuming experiment, and due to its incredible success, replaces libSQL as our intended direction. At this point, libSQL is production ready, Turso Database is not - although it is evolving rapidly. More details here.

Publications

  • Pekka Enberg, Sasu Tarkoma, Jon Crowcroft Ashwin Rao (2024). Serverless Runtime / Database Co-Design With Asynchronous I/O. In EdgeSys 24. [PDF]
  • Pekka Enberg, Sasu Tarkoma, and Ashwin Rao (2023). Towards Database and Serverless Runtime Co-Design. In CoNEXT-SW 23. [PDF] [Slides]

License

This project is licensed under the MIT license.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Turso Database by you, shall be licensed as MIT, without any additional terms or conditions.

Partners

Thanks to all the partners of Turso!

Contributors

Thanks to all the contributors to Turso Database!