Work in progress · engineering preview

PostgreSQL,
unbundled.

The PostgreSQL you already know, with quorum-durable WAL and immutable page history designed for object storage. Built in Rust. Coordinated at the edge. Made to recover, branch, and scale without copying a whole database.

Actual PostgreSQL

Upstream PostgreSQL remains the parser, planner, executor, catalogs, MVCC engine, and wire protocol.

Durable before “done”

Commits cross a fenced WAL quorum before acknowledgement. Object storage is the durable history, not a latency gamble.

Immutable by default

Checksummed page layers and manifests are content-addressed. Branches reuse history instead of duplicating it.

One database.
Four clean layers.

DBlicious separates the parts PostgreSQL does brilliantly from the durability and lifecycle machinery needed by a cloud database.

01 · Connect

PostgreSQL compute

Native clients, SQL semantics, extensions, MVCC, and query execution.

02 · Commit

WAL quorum

Signed leader leases, epoch fencing, batching, fsync, and majority durability.

03 · Materialize

Page service

LSN-versioned relation pages, sparse writable overlays, and bounded reconstruction.

04 · Retain

R2 history

Immutable layers, atomic manifests, instant branches, compaction, and retention.

Built in public.
Measured honestly.

This is an active engineering preview, not a production database offer. The site goes live early; customer provisioning waits for recovery, compatibility, and performance evidence.

FOUNDATIONPostgreSQL 18 storage hooks and authenticated page serviceworking
DURABILITYThree-keeper WAL path with 2-of-3 fsync quorum and fencingworking
HISTORYImmutable snapshots, incremental overlays, and O(1) branchesworking
RECOVERYPostgreSQL-verified arbitrary-LSN replay; automated promotion nextin progress
CLOUDFLAREFree-tier Rust Worker, Durable Objects, and guarded R2 Standardworking
RELEASECloud SQL migration, compatibility matrix, regional performance, and SLOsnext
Preview status

No magic. No compatibility theater.

PostgreSQL 18 now replays DBlicious-reconstructed WAL to a selected LSN in the recovery drill. Database testing opens after automated promotion, upstream compatibility suites, and measured failure behavior match the promises on this page.