Limbo is a project to build the next evolution of SQLite.
Find a file
Jussi Saurio 6559f23f85 Merge 'hack imports of wasm due to the issues in Vite and Next.js build systems' from Nikita Sivukhin
This tries to establish smooth as possible experience for browser
packages in web.
In order to do that this PR do the following tricks:
1. export `./vite` entry-point which should be used like `import {
connect } from "@tursodatabase/database-browser/vite"` for Vite bundler
   * This entrypoint has fix for the issue
https://github.com/vitejs/vite/issues/8427 which breaks package in the
dev-server mode
   * In order to overcome this we do 2 tricks:
     - Inline WASM module in order to avoid loading it from the separate
file
     - Use same file as entry-point for main thread and for the web
worker
   * Note, that we do these tricks only for `development` build and
produce build will be chunked and optimized as usual with Vite and will
treat worker and WASM modules as separate fiels
3. export `./turbopack` entry-point which should be used like `import {
connect } from @tursodatabase/database-browser/turbopack"` for Turbopack
(Next.js) bundler
   * This entrypoint has fix for the issue
https://github.com/vercel/next.js/issues/82520'
   * In order to overcome this for now we always inline WASM for Next.js
4. Bundle browser libraries in order to easily consume them without need
for bundlers:
   * e.g. `import { connect } from
"https://unpkg.com/@tursodatabase/database-browser/bundle/main.es.js";`
5. We vendor `@napi-rs/wasm-runtime` for now in order to fix runtime
errors due to accesses to `process.env.NODE_DEBUG_NATIVE` env var (not
defined in web)
   * This should be very temporary solution because I already fixed
wasm-util dependency which cause this error
(https://github.com/toyobayashi/wasm-util/issues/4) and hope that napi-
rs PR will be merged soon: https://github.com/napi-rs/napi-rs/pull/2921

Reviewed-by: Jussi Saurio <jussi.saurio@gmail.com>

Closes #3017
2025-09-12 16:18:47 +03:00
.cargo configure cargo for napi-rs 2025-08-08 15:45:05 +04:00
.github fix CI 2025-09-12 15:39:38 +04: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 Merge 'hack imports of wasm due to the issues in Vite and Next.js build systems' from Nikita Sivukhin 2025-09-12 16:18:47 +03:00
cli resolve merge conflict 2025-09-11 18:13:29 +07:00
core Fix tests for views 2025-09-12 08:20:40 -04:00
docs Document DEFERRED and IMMEDIATE transaction modes 2025-09-10 19:39:58 +03:00
extensions add remove_file method to the IO 2025-08-21 14:51:02 +04:00
fuzz fix: math function parameter conversion 2025-09-10 20:49:30 -03:00
licenses
macros Merge branch 'perf-3' into perf-4 2025-09-02 18:47:05 +07:00
packages/turso-serverless await on .close() 2025-09-10 13:42:21 +05:30
parser Add BEGIN CONCURRENT support for MVCC mode 2025-09-11 16:05:52 +03:00
perf perf: Add simple throughput benchmark 2025-09-12 07:35:57 +03:00
scripts fix update script 2025-09-12 17:03:04 +04:00
simulator Merge 'core: Rename IO::run_once() to IO::step()' from Pekka Enberg 2025-09-10 15:11:28 +03:00
simulator-docker-runner run 50% of AWS sims with faultless profile 2025-09-10 00:38:37 +03:00
sql_generation sql_generation: Add support for DROP INDEX 2025-09-11 08:35:18 +03:00
sqlite3 sqlite3: Remove broken sqlite3_checkpoint() test cases 2025-09-05 10:15:55 +03:00
stress Clippy you are so smart 2025-09-10 13:54:42 +03:00
sync/engine fix clippy and remove old action yaml 2025-09-11 00:03:01 +04:00
testing Merge 'core: Support ceiling modifier in datetime' from Ceferino Patino 2025-09-10 14:46:07 +03:00
tests Merge 'core: Fix reprepare to properly reset statement cursors and registers' from Pedro Muniz 2025-09-12 12:29:53 +03:00
vendored/sqlite3-parser Add expr_compiler 2025-08-25 17:48:17 +03:00
whopper whopper: Switch to mmap2 crate to fix Windows build 2025-09-11 08:35:18 +03:00
.dockerignore Add .dockerignore and Makefile commands to support docker 2025-07-31 00:00:44 -04:00
.github.json
.gitignore on reprepare create new state with updated number of cursors and 2025-09-11 12:50:22 -03:00
.python-version setup uv for limbo 2025-04-15 12:45:46 -03:00
Cargo.lock Commit uncommitted whopper lockfile 2025-09-12 08:43:59 +03:00
Cargo.toml perf: Add simple throughput benchmark 2025-09-12 07:35:57 +03:00
CHANGELOG.md s/2024/2025/ 2025-09-10 16:39:11 +03:00
COMPAT.md Merge 'core: Support ceiling modifier in datetime' from Ceferino Patino 2025-09-10 14:46:07 +03:00
CONTRIBUTING.md whopper: A new DST with concurrency 2025-09-11 08:35:18 +03:00
db.sqlite reset statement before executing 2025-05-02 19:26:44 -03:00
dist-workspace.toml Update cargo-dist to the latest official version 2025-08-02 04:35:52 +09:00
Dockerfile.antithesis antithesis: Add io_uring stress test 2025-09-04 19:17:46 +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
Pipfile.lock
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!