Roadmap
Gates, not dates.
Each phase ends with a gate that has to pass before the next one starts, so the project changes course on evidence. The estimate for a first hosted, non-critical workload is six to twelve months from October 2026, revised at every gate.
Done
3 phases
Foundations, storage engine, query plans and verifier.
In progress
1 phase
The SQL front end over the PostgreSQL protocol.
Planned
3 phases
Distribution, first hosted tenant, search and vectors.
Phases
Each phase and its gate
| # | Phase | State | Gate | Evidence |
|---|---|---|---|---|
| 0 | Foundations | Done | Simulator, fault-injecting disk, model-checked log design, benchmark harness | TLA+ model of the write-ahead log checked with TLC; deterministic simulator in the repository |
| 1 | Storage engine | Done | Crash-safe engine with transactions, compaction and a memory governor, checked against RocksDB | One million simulated crash points against the log; three-way differential vs RocksDB; 412k point reads/s on the dev host (pending a soak test and dedicated hardware) |
| 2 | Query plans and verifier | Done | Plan language, verifier, executor, optimizer; 10⁷ differential plans; isolation harness; Lean proofs; TPC-H within 3× of DuckDB | All correctness items passed on 21 Oct 2026. The 3× speed item failed (11–46× after columnar storage) and was re-scoped by an architecture decision record |
| 3 | SQL front end | In progress | PostgreSQL wire protocol so psql and drivers connect unchanged; one real application's test suite passes | psql and pgx connect with a token over both protocols; inserts, updates, deletes, filtered and grouped queries and joins run with answers equal to DuckDB's; key lookups seek. Transactions, the catalog tables ORMs read and parallel reads are open |
| 4 | Distribution | Planned | Replication per shard, distributed transactions, failover, with Jepsen-style testing | Not started; distributed operators and their laws are specified |
| 5 | Migration and the first hosted tenant | Planned | Copy-and-follow migration from PostgreSQL; backups and point-in-time restore rehearsed; 30 days on a real non-critical workload | Not started; this is the gate hosted early access waits for |
| 6 | Search, vectors and graphs | Planned | Each engine proven by a public benchmark against a named leader (ANN-Benchmarks, LDBC SNB) behind the same verifier | Operators specified; nothing built |
Rules
What will not ship early
No hosted database
before backups and restore have been rehearsed on a real workload.
No performance claim
until it is measured on dedicated hardware; development-host numbers stay labelled indicative.
No feature that bypasses the verifier
including internal jobs, caches and any future learned optimizer.
See the detail behind each phase.
The status page lists every built part and its state.