frankensqlite
Independent ground-up Rust reimplementation of SQLite with concurrent writers and information-theoretic durability
frankensqlite: Independent ground-up Rust reimplementation of SQLite with concurrent writers and information-theoretic durability
Independent ground-up Rust reimplementation of SQLite with concurrent writers and information-theoretic durability
What the project is
frankensqlite is a Rust project hosted on GitHub. Independent ground-up Rust reimplementation of SQLite with concurrent writers and information-theoretic durability An independent ground-up Rust reimplementation of SQLite with page-level MVCC concurrent-writer support. The repository is maintained by Dicklesworthstone and tracks activity through its public issue tracker and commit history. Readers who want a working example rather than a bare library will find the documentation and the linked resources useful for getting a first build running.
What it offers
The frankensqlite repository documents several concrete capabilities that shape how people use it. Row-level (PostgreSQL-style) would break the file format and require VACUUM Table-level would conflict on every write to a shared table Public entry point: fsqlite::Connection (crates/fsqlite/src/lib.rs), implemented by fsqlite-core::Connection (crates/fsqlite-core/src/connection.rs). Execution backend: the default table-backed path uses pager transactions plus storage cursors into the B-tree stack, executed by fsqlite-vdbe::VdbeEngine (crates/fsqlite-vdbe/src/engine.rs). Runtime image/fallback: fsqlite-vdbe::engine::MemDatabase is still maintained as the in-memory execution image and remains in selected compatibility/fallback paths while cutover work continues. These points are taken from the project README, so they reflect what the maintainers actually ship rather than marketing claims. Checking the file list and the example directories gives a fuller picture of how each piece fits together.
How to set it up
Getting frankensqlite running starts with cloning the source from https://github.com/Dicklesworthstone/frankensqlite. The README lists the commands needed to fetch the code and build or launch it. Representative steps from the documentation include: curl -fsSL "https://raw.githubusercontent.com/Dicklesworthstone/frankensqlite/main/install.sh?$(date +%s)" | bash. After the code is on disk, the project instructions walk through configuration and any dependencies. Following the order shown in the README avoids the common setup mistakes that come from mixing steps.
License and project status
frankensqlite is written primarily in Rust and is released under the NOASSERTION license, which sets the terms for reuse and redistribution. The project reports around 214 stars on GitHub, a signal of how many developers have bookmarked it. The source was last updated on 2026-08-21. The canonical location is https://github.com/Dicklesworthstone/frankensqlite, where the license file, the changelog and the open issues give the most current state of the work. Anyone planning to depend on it should read the license text directly before shipping it inside another product.
Editorial conclusion
The frankensqlite source lives at https://github.com/Dicklesworthstone/frankensqlite under the NOASSERTION license and is mainly written in Rust. The README and the linked examples remain the place to confirm the current behaviour before adopting the project.
Community notes