frankensqlite

Independent ground-up Rust reimplementation of SQLite with page-level MVCC concurrent writers (serializable snapshot isolation). Runs today in compatibility mod

What is frankensqlite?

Independent ground-up Rust reimplementation of SQLite with page-level MVCC concurrent writers (serializable snapshot isolation). Runs today in compatibility mode over standard SQLite files; RaptorQ erasure-coded self-healing durability is in-progress research, not yet a live guarantee.

Overview of frankensqlite

What it is

FrankenSQLite is an independent ground-up Rust reimplementation of SQLite with page-level MVCC concurrent-writer support. It runs today in compatibility mode over standard SQLite files. RaptorQ erasure-coded self-healing durability is in-progress research and not yet a live guarantee. It is not a C-to-Rust translation; it references the C source only for behavioral specification.

Key features

  • Page-level MVCC concurrent writers: replaces the single-writer lock with page-level Multi-Version Concurrency Control. Writers touching different pages can overlap their page work. Serializable Snapshot Isolation (SSI) tracks write-skew dependencies by default.
  • Safe Rust engine core: most of the workspace forbids unsafe code; the engine, pager, parser, VDBE, and surrounding crates stay in safe Rust. Unsafe is limited to fsqlite-vfs (mmap/shm) and the optional fsqlite-c-api (FFI).
  • File format compatibility: built around standard .db plus rollback-journal/WAL files. Admits databases with UTF-8 (encoding 1) and UTF-16le/UTF-16be (encodings 2/3) for both reads and writes.
  • Serializable Snapshot Isolation (SSI) by default: BEGIN CONCURRENT targets SERIALIZABLE isolation. The conservative Cahill/Fekete rule is applied at page granularity. PRAGMA fsqlite.serializable = OFF downgrades to plain Snapshot Isolation.
  • Extensions wired in: FTS5, JSON1, R-tree/geopoly, ICU, and generate_series.
  • Cross-process MVCC: partial support via shared-memory coordination.
  • Embedded, zero-config: yes.

Use cases

  • Write-heavy workloads where SQLite's single-writer bottleneck limits throughput.
  • Applications needing concurrent writers while maintaining compatibility with existing SQLite databases.
  • Environments requiring memory safety and data race prevention in the database engine.
  • Embedded systems that benefit from zero-configuration and file format compatibility.

Getting started

Linux and macOS: bash curl -fsSL 'https://raw.githubusercontent.com/Dicklesworthstone/frankensqlite/main/install.sh?$(date +%s)' | bash Windows PowerShell: powershell irm 'https://raw.githubusercontent.com/Dicklesworthstone/frankensqlite/main/install.ps1?$([DateTime]::UtcNow.Ticks)' | iex Rust users can install the CLI with: bash cargo +nightly install fsqlite-cli --locked

License and pricing

The license is not stated (NOASSERTION). The project is open source.

Based on the project's public README and repository metadata.

Add this badge to your README

Featured on YunoDB Badge styles & help

Maintain this project? Show that it is featured on YunoDB.

Markdown[![Featured on YunoDB](https://yunodb.com/badge/dicklesworthstonefrankensqlite.svg)](https://yunodb.com/tools/dicklesworthstonefrankensqlite?utm_source=github&utm_medium=badge)
HTML<a href="https://yunodb.com/tools/dicklesworthstonefrankensqlite?utm_source=github&utm_medium=badge"><img src="https://yunodb.com/badge/dicklesworthstonefrankensqlite.svg" alt="Featured on YunoDB" height="20"></a>