Give every PR, CI run, and AI agent an isolated, disposable database
with production-like data. Keep production where it is.
HyperAdvisor
Quillstack
Ferncrest
Connect production once. Agents, CI and pull requests branch from it on demand.
We never host your production database. Data is masked before it's copied.
Twenty agents on one staging database means colliding migrations, tests that step on each other and state nobody can trust. Give every agent its own Postgres instead.
Every agent writes into the same database.
Claude Code ─┐ Codex ─┼→ staging GitHub Actions ─┘
Every agent gets a branch of its own.
Connect production once. pgrun creates isolated, disposable branches for agents, CI and pull requests.
Each agent, PR or CI job triggers the same loop — automatically.
Connect your existing Postgres — production stays put.
Spin up an isolated Postgres branch in seconds.
Get a normal DATABASE_URL. No custom API.
Delete it when the job's done. No cleanup.
CLI, API, and structured output for agents.
Every branch hands back an ordinary connection string. Nothing in your app has to know.
Your app reads the same variable it always has — the branch is just another Postgres.
DATABASE_URL=postgresql://agent:x8Kq2vLm@br-7f3a9c.us.db.pgrun.dev:5432/postgres?sslmode=require
Frameworks and clients connect as they always have: a Postgres URL, nothing else.
ENV["DATABASE_URL"]
DATABASES["default"]
url = env("DATABASE_URL")
drizzle(DATABASE_URL)
psql "$DATABASE_URL"
libpq · wire protocol
Agents and pipelines drive pgrun through the CLI, the MCP server or the Claude Code skill.
pgrun skill install
branch create --format=json
pgrun mcp serve
branch exec --create ci-$RUN
branch exec --delete-after
pgrun mcp serve · stdio
The same loop — create, run, delete — wherever something needs a database of its own.
Every job branches from the Safe Copy, runs migrations and tests on real data, and deletes the branch when it exits — pass or fail.
branch exec --create ci-$RUN --delete-after -- bin/rails db:migrate
Read the docs →
Claude Code, Codex or Cursor open a branch, try the change, and throw it away. Through the CLI, the MCP server or the Claude Code skill.
pgrun skill install · pgrun mcp serve
Read the docs →
Each preview gets its own Postgres with production-shaped data, named after the deploy and gone when the deploy is. Same recipe as CI.
branch exec --create preview-$SHA --ttl 24h -- …
Read the docs →
Agents need a real database to try things on. It shouldn't be shared staging, a dump on someone's laptop, or a reason to move your production somewhere new.
Connect RDS, Aurora, Cloud SQL, Supabase, Neon or your own server. Nothing to migrate, and no new host to trust with production.
instead ofmoving to a new Postgres host
pgrun reads production once to build a Safe Copy, masking sensitive columns under a policy a person approves. Agents only ever see the copy.
instead ofpg_dump onto laptops
Branches are copy-on-write clones of the Safe Copy, ready in about 3 seconds whatever the size of your data.
instead ofrestoring a dump for every run
Every agent, pull request and CI job gets its own isolated Postgres in parallel. Nobody waits, and no one's migration lands on anyone else.
instead ofqueueing on shared staging
A CLI with JSON output and real exit codes, an MCP server, a Claude Code skill and an HTTP API. Approvals stay with people.
instead ofa dashboard someone has to click
Every branch can carry a TTL, --delete-after cleans up even when the job fails, and compute is billed by the second only while a branch runs.
instead ofcleanup scripts and forgotten databases
A hundred pull requests a day against a 100 GB database. A copy of production per run means a hundred full databases running all day. A pgrun branch stores only what it changes and bills compute only while it runs.
--delete-after removes it.
see pricing →
Don't take our word for it — listen to what developers say about our open-source Postgres tools.
No credit card required. Create real Postgres branches, connect your agents, and test the workflow before paying.
Safe Copies and branches run on our own hardware in the US. Production stays wherever it is.
Every branch connection requires TLS through pgrun's gateway. Branch ports are not reachable from the internet.
Masking runs inside the read. Your production connection string is encrypted at rest and never shown again.
Managed databases take daily base backups plus continuous WAL, stored off-site. The Safe Copy refreshes from production on a schedule you set.
Start free with $10 credits · Keep production where it is. Or create branches directly through the API.