Adjoint — by stagDB

Every developer deserves their own copy of production.

Adjoint gives each developer an isolated, production-like Postgres in seconds — copy-on-write clones of real data, at near-zero incremental storage cost, on AWS infrastructure you own. Break it, reset it, no ticket.

Get started Talk to us 
$ adj clone prod-pg16
✔ claimed from warm pool          ready in 16s
$ adj creds i-4f2a
postgres://daniel:••••••@i-4f2a.ns-daniel.svc:5432/app
$ psql -c "select count(*) from orders"
  50,000,000   -- real volumes, real distributions, real edge cases
$ adj reset i-4f2a    # broke it? re-clone and move on
16 smedian time to a ready clone, from a pre-warmed pool
1.12×total storage measured for 10 full-size clones
0 bytesof your data on our servers — metadata-only control plane
< 60 minfrom empty AWS account to a working cluster, one command
The problem

Seed data lies. Staging is a queue. Dumps go stale.

To ship correct software, developers need data that behaves like production — real volumes, real distributions, real edge cases. But production data is large, sensitive, and slow to copy, so teams settle for one of four bad options:

// option 1

Tiny seed data

The query that's fast on 500 rows times out on 50 million. Bugs slip to prod.

// option 2

One shared staging DB

Contention and pollution. One destructive migration breaks everyone.

// option 3

Manual prod dumps

Hours per copy, perpetually stale, and PII sprayed across laptops.

// option 4

Per-dev cloud copies

Cost-prohibitive at multi-TB × headcount. Nobody ever refreshes them.

The root cause: copying multi-TB data the naive way is O(size × developers). Adjoint changes the economics — ZFS copy-on-write makes per-developer copies effectively free.

How it works

Admins curate once. Developers self-serve forever.

Provision your cluster

adj cluster provision --developers 20 stands up EKS + FSx for OpenZFS + the data-plane stack in your own AWS account — sized from your team, preflight-checked against your IAM, one command.

Curate golden snapshots

adj import run pulls from your real source (e.g. RDS Postgres) into a versioned, immutable golden snapshot — the curated base your whole team clones from. Re-import anytime; versions are pinnable.

Developers clone

adj clone hands each developer a full copy-on-write Postgres in their own locked-down namespace — then reset, refresh to a newer version, or destroy. No DBA, no ticket.

Your data never leaves your walls.

The Adjoint control plane is metadata-only: it orchestrates orgs, catalogs, and lifecycle — never your rows. Data lives exclusively in your AWS account; instance credentials are brokered live and never stored; every privileged action lands in a tamper-evident, hash-chained audit log. Isolation between developers is enforced with default-deny network policy and penetration-tested.

Features

A complete platform, not an engine to assemble.

CLI-first, portal included

The adj CLI is the product — scriptable end to end. A companion web portal covers the same hero loop for clicking around.

Versioned golden snapshots

Immutable, admin-curated base datasets with lineage. Pin a version for reproducible test runs; share across the org.

Pre-warmed clone pools

Pools keep ready clones on standby so a developer claims one in seconds instead of waiting on storage provisioning.

Your AWS account

EKS + FSx for OpenZFS + CloudNativePG, provisioned by one command. Adjoint never holds your cloud credentials.

Isolation, enforced

A namespace per developer with default-deny network policy, image allowlists, and admission control — pen-tested live on EKS.

Guardrails built in

Per-user and per-org quotas, TTLs with automatic reaping, invite-only membership with role-based access, and a verifiable audit trail.

Pricing

Flat, per cluster. Every developer included.

Adjoint

  • One data-plane cluster in your AWS account
  • All developers, golden snapshots, and clones included — no per-seat fees
  • CLI + web portal
  • Imports from your real sources (e.g. RDS Postgres)
  • Policy-enforced isolation, quotas, TTLs, audit log
  • You pay AWS directly for the infrastructure you run
$49 / month
per org, per cluster

$29 / month when billed annually $49

Get started

Questions, pilots, design-partner interest — hello@stagdb.com