by DB Branch
Self-hosted MySQL and PostgreSQL branches on ZFS clones: the maker measured 0.5 seconds for a PostgreSQL branch on its own three-node test cluster.
Pick it if your platform team wants a throwaway copy of a big database per pull request or AI agent and can run Ubuntu with ZFS. Skip it if you want a managed cloud database. It is Beta, only days old, and promises no support for the free core.
One open-source tool makes copy-on-write branches of both MySQL and PostgreSQL on your own servers and exposes them to agents over MCP.
Main trade-off
Linux and ZFS only, no hosted version, and a Beta project with no promised support.
| Plan | Monthly price | What it includes |
|---|---|---|
| Community | Free | Bases, snapshots and branches, Checkpoints: save a branch and go back to it, Branch upgrade, such as MySQL 8.0 to 8.4, Anonymous branches with limits, Scheduled refresh and free masking tools, Cluster, console, CLI, API and MCP |
| Lite | $30/mo | History module: record a branch and go back to any transaction (MySQL), History of what changed, shown with the checkpoints, Up to 3 nodes, Billed monthly or yearly, for businesses only |
Community is free and open source under Apache-2.0, on any number of nodes. Lite costs USD 30 monthly or USD 300 yearly, is sold to businesses only, and adds the history module for small clusters of three nodes at most. Team and Business are not on sale yet and have no announced price. Paid modules run free for 30 days without a key.
db-branch is open-source software that creates instant MySQL and PostgreSQL database branches on your own servers using ZFS copy-on-write clones. It ships a command line, REST API, web console and MCP server, runs on Ubuntu with ZFS, and has no hosted version, so branch data never leaves your network.
Copy-on-write branches
A branch is a ZFS clone of a base snapshot, so creating one copies no data and the time does not grow with the size of the base.
Reset and checkpoints
Each branch keeps its starting point as a snapshot, so a reset finishes in seconds and runs no SQL, and a checkpoint saves a running branch to return to later.
Per-branch version upgrade
branch upgrade moves one branch to a newer MySQL or PostgreSQL version after saving a checkpoint, and rolls back by itself if the upgrade fails.
Scheduled refresh and masking
Set a source and an interval and db-branch dumps, loads and snapshots production, with Greenmask or PostgreSQL Anonymizer available to mask the base first.
MCP server for agents
An agent can create, use and delete its own branches through MCP with a personal token that carries the branches scope.
Cluster and routing
Raft keeps state on every node so any node takes commands, and optional ProxySQL routes a connection to a branch by user name or query comment.
Web console
Admin and user pages show bases, snapshots, branches, storage and cluster load, and from 0.2.4 can run SQL on a branch.
Expiry and notifications
A branch can expire after a set time, and notifications go to Slack or a webhook.
Most users expect these and they are not currently supported.
The nearest AI tools on Hokai for the same job.
| Tool | Price from | Free plan | Runs on | Rating |
|---|---|---|---|---|
| $30/mo | Yes | Web | 3.0 | |
| -- | Yes | Web | 3.4 | |
| $30/mo | Trial | Web · Mac · Windows | -- | |
| $12/mo | Yes | Web · iOS | -- |
Apache-2.0 core; the paid modules are closed-source
The core is free under Apache-2.0 and runs on any number of nodes. The Lite plan is USD 30 a month or USD 300 a year, up to 3 nodes, and adds the history module; Japanese businesses see JPY 3,000 and JPY 30,000 instead. Team and Business have no announced price. Sales are to businesses only, and the Japanese legal notice states that the seller gives no refund after payment (read 16 November 2026).
Yes. Everything in the open-source core is free, including branches, checkpoints, branch upgrade, clustering, the console and MCP. Paid modules also run without a key for a 30-day trial that starts when you first enable one, once per cluster; afterwards only the paid features stop and your databases keep working.
MySQL and PostgreSQL. The maker tests MySQL 8.0 and 8.4 and PostgreSQL 18, and engine runtimes install by version and sit side by side, so each base picks its own. A branch runs on the version of its base, and branch upgrade can move a single branch to a newer one.
Only on your servers. The README states there is no hosted or cloud version, and a licence key is checked by its signature inside your cluster. You need a supported Ubuntu release and a ZFS pool; a Multipass VM on macOS or Windows works for evaluation, but its file-backed pool is not meant for real data.
An agent connects through the built-in MCP server with a personal token created under Account, MCP access, which carries the branches scope. It can create a branch, run its SQL there and delete the branch, so production is not touched. Masking stays your job: the maker's FAQ says it runs the masking tool and rules you choose and does not guarantee the result.
db-branch is open-source software that gives MySQL and PostgreSQL databases Git-style branches on your own servers. Its public repository was created on 13 November 2026 and the project calls itself Beta; the maker's Japanese legal notice names one individual, Keisuke Masuda, as the seller. A branch is a ZFS copy-on-write clone of a snapshot of a loaded database called a base, so making one copies no data and takes seconds however large the base is. The maker measured 0.5 seconds for PostgreSQL and 3 seconds for MySQL on its own three-node test cluster.
Each branch is a stock mysqld or postgres process on its own port, so nothing proprietary sits in the data path and ordinary tools such as zfs, mysql and psql still work. A base can be loaded from a dump or refreshed from production on a timer, then masked with the free Greenmask or PostgreSQL Anonymizer modules before branches are cut. A branch can be reset to its start, saved as a checkpoint, upgraded to a newer database version on its own, or left to expire. A command line, a REST API and a web console share one API, and three or more nodes form a Raft cluster that keeps working when one is down.
It suits platform and backend teams that want a fresh copy of a large database for every pull request or migration test, and teams that let Claude Code or another AI agent loose on data. The built-in MCP server lets an agent create a branch, run a risky query on it and delete it, so production stays untouched. The maker's CI example is a GitHub Actions workflow that opens a branch when a pull request opens and deletes it when the pull request closes.
It runs only on Ubuntu 24.04 or 26.04 with a ZFS pool and has no hosted version. The nearest alternatives are Neon, whose docs describe branches as copy-on-write clones of your data, and DBLab Engine from Postgres.ai, an open-source project built for Postgres that showed 2.8k GitHub stars against this project's 18 on 16 November 2026. Neither has a Hokai page yet. For sandboxes built to test AI agents, see Archal and the wider AI software testing shelf.
Versions 0.2.4 and 0.2.5 shipped on 15 November 2026 and added pause and resume for a branch, an SQL box in the web console, a storage page that shows pool use per base and branch, and fixes for MySQL runtimes on arm64.
On 16 November 2026 Hokai opened the public demo console, whose data is sample data that resets on reload. Its user page listed a MySQL 8.4.13 base and a PostgreSQL 18.6 base of about 1 GiB, and let a visitor pick a branch name, a keep-for time from 1 hour to 7 days, who may connect, and an option to record every change.
Decision: use it if you already run Ubuntu with ZFS and want a database branch per pull request or per agent. Choose a managed branching service if you want no servers to run, and wait if you need vendor support or sign-in control today.
Product facts on this page (pricing, plans, integrations, compliance) are read from DB Branch's own pages and documentation. The verdict is Hokai's reading of them, not the vendor's claim.