TiloBox
Back to directory
Limbo project preview

Limbo

Modern, complete in-process relational database engine compatible with SQLite, built in Rust.

LicenseMIT
GitHub stars7.4k
Last commit1 weeks ago
Tags5 topics
Rust Sqlite EngineIn Process Oltp DatabaseDeveloper ToolsWasm Relational DatabaseAsync Io Database Runtime
Overview

Why consider Limbo?

Limbo is an open-source, in-process OLTP database engine written in Rust. Designed as a modern, asynchronous architecture compatible with SQLite data files, it achieves high concurrency and native WebAssembly runtime compilation.

Guided learning

Learn Limbo by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

1 min read 2 sections
In this guide2 sections

Overview of Limbo

Limbo provides an asynchronous, Rust-native relational database compatible with standard SQLite databases.

Quickstart

bash
1cargo install --git https://github.com/tursodatabase/limbo.git limbo-cli
2limbo my_database.db

Execute SQL queries through the Limbo CLI shell or embed the Rust crate into high-concurrency servers.

Limbo is licensed under the permissive MIT License.

Related tools

More options with a similar category or technology profile.

Limbo FAQs

Limbo is listed as a Developer Tools tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

Limbo is listed under the MIT license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

Limbo is listed as an alternative to DuckDB. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.