database-branching

DBLab enables 🖖 database branching and ⚡️ thin cloning for any Postgres database and empowers DB testing in CI/CD. This optimizes database-related costs while improving time-to-market and software quality. Follow to stay updated.

A disposable copy of your production stack for every pull request: masked Postgres, contained third-party APIs, and agents that use your app like people.

PostgreSQL database branching

Isolated databases for every AI agent branch. Build, test, and migrate in parallel. Production stays untouched.

Keep your database in sync with your git branches.

Visualize your Neon Postgres branches

Postgres test DB cloned straight from your production, for AI agents and humans. Real-time replication of rows and schema, copy-on-write clones, snapshots. No seeding, no dumps.

The self-hosted Neon alternative — database branching for Postgres on infrastructure you own (AWS, GCP, Azure, or local Docker). Built on DBLab Engine.

Branch SQLite like git — copy-on-write forks, checkpoint/rollback/promote, kill-9-durable capture. Stock SQLite files on local disk or S3. Built for AI agents and eval harnesses.

Agentic-first CLI for Neon Postgres - per-project usage, billing, and branch management the dashboard won't show you

⚡ Lighting fast Postgres Branching/Cloning (Work In Progress)

Local PostgreSQL database branching CLI for migrations, schema diff, and isolated development.

GitHub Action for per-PR Cloudflare preview environments: an isolated Worker, D1, KV & R2 for every pull request — auto-deployed with dev data sync and migrations, torn down on close.

Versioned backend state for parallel AI coding agents — isolate, commit, diff, and reset real Docker Compose services.

Archived demo of pgoverlay: every PR got a masked copy-on-write clone of prod. The recorded run is PR #1 — a migration that passed locally and failed on real data.

Top Schema Migration Platform (Opensource) 🌟 Star if you like it! 🌟

Watch the WAL become the database: LSN observation, a deliberate delete, and a sub-second branch back to the pre-mistake LSN. Companion to the DevOps Daily post: devops-daily.com/posts/wal-as-the-source-of-truth-lakebase-storage-s3

The execution environment for AI database agents — give Claude Code, Cursor, or your own agent a disposable branch of your Postgres to run migrations, indexes, and DELETEs against, then throw it away. Production is never touched.

Serverless blog database — schema migrations, branching workflow, connection pooling