Engineering notes
How FoxByte is built and why, with the numbers behind each decision.
What the Blackbox proves to an auditor, and what it does not
An auditor asks who changed the database, who approved it, and how you know the answers were not edited. What FoxByte’s Blackbox answers today, the commands that show it, and where it stops.
Read the note →Maker-checker for schema changes: one asks, another approves
Separation of duties for database changes: prepare a change on a full-size branch, review the exact statements, and apply them to main in one transaction. How FoxByte’s change requests work, and their one limit today.
Read the note →The agent row limit: why a row counter, and what it costs
We measured two ways to stop an AI agent’s runaway UPDATE or DELETE on a million-row table. One refuses it in 14.5 ms on a small test VM. Here is the data, including what it costs people. It ships in the next release.
Read the note →Sell the making of anchors, not the checking
Signed Blackbox anchors are an Enterprise feature. Verifying them is free, forever, in every edition. Here is why we drew the line there.
Read the note →Why FoxByte has no storage engine of its own
FoxByte branches, rewinds and backs up PostgreSQL without replacing how Postgres stores data. The reason is one requirement we locked first: transaction speed is never traded.
Read the note →Try what you just read about.
Everything in these notes ships in the free edition, except where it says Enterprise.
$ curl -fsSL https://get.thefoxbyte.com/install.sh | sh