FoxByte
GitHubContact salesInstall
Product

Everything FoxByte adds to Postgres, and nothing it takes away

Transaction speed was the first requirement and it is never traded. FoxByte has no storage engine of its own: rows, indexes and the write-ahead log are stored by PostgreSQL 18 itself. What FoxByte built is everything around it.

Install FoxByteRead the docs
How FoxByte is put togetherApplications, tools and agents connect to the FoxByte gateway on port 6432, which routes each connection to stock PostgreSQL 18 on local disk. Beside the commit path, copy-on-write clones on ZFS or btrfs create branches, and wal-g ships write-ahead log and base backups to S3-compatible storage.Commit pathstock Postgres on local disk; connections through the gatewayOff the commit pathnever waited on by a transactionYour app · psql · ORMand AI agentsGateway :6432database name = branchPostgreSQL 18 · mainstock, on local NVMeCopy-on-write branchesZFS or btrfs clonesObject storagewal-g: WAL + base backupsBlackbox and guardrailsevent triggers inside Postgres
Capabilities

Six things, one page each

Every capability maps to one job: branch, record, stream or protect.

Branching

A full, isolated copy of the whole database in seconds, for every developer, test or agent.

Learn more →

Blackbox

Every schema change recorded with who made it, in a tamper-evident hash chain.

Learn more →

RealtimeEnterprise

Every insert, update and delete as it commits, from your own server.

Learn more →

Guardrails

Destructive commands blocked, deletes without a WHERE refused.

Learn more →

Time travel & HA

Restore to any second in the archived window, keep backups off the machine, fail over in one command.

Learn more →

Web console

Dashboard, SQL editor, data grid and the Blackbox, served by the engine itself.

Learn more →
The design

On the commit path: only Postgres

Your commits go to stock PostgreSQL on local NVMe. The only thing in front of them is a wire-protocol gateway that routes each connection by database name.

Branching, backups and time travel happen beside the commit path, using a copy-on-write file system and asynchronous WAL archiving. The commit never waits for them.

  • One endpoint, :6432. The database name is the branch.
  • TLS on by default; sslmode=require works out of the box.
  • Drivers, ORMs and SQL work unchanged.
restore main as it was at 14:45:36drag the handle
09:00 · base backup17:00 · now
Built on

Proven, open foundations

PieceWhat it does
PostgreSQL 18Stores every row, index and log record, unmodified. Installs created on 16 keep running 16.
ZFS or btrfsCopy-on-write clones for branches: ZFS on macOS and Linux, btrfs on Windows.
wal-gShips write-ahead log and base backups to object storage for point-in-time restore.
S3-compatible storageHolds backups and anchor copies, with Object Lock when you want them unchangeable.
GoThe gateway, control plane, CLI and console server.

See it around your own database.

Install FoxByte and import a copy of the Postgres you already run.

$ curl -fsSL https://get.thefoxbyte.com/install.sh | sh
Install FoxByteQuickstart