Ardent clones any Postgres database in under 6 seconds using copy-on-write storage so coding agents can test against production data safely.
Key Takeaways
Clones are isolated at compute and storage level; storage cost covers only changes made, not full DB copies.
Benchmarked at 30,960x faster cloning per TB versus traditional replicas; supports infinite concurrent clones vs. 15-20 for replicas.
Compute autoscales and scales to zero between agent workloads, eliminating overprovisioning.
Supports Supabase, AWS RDS, and PlanetScale with no config changes or migrations required.
Targets AI-native data teams running coding agents for migration testing, backfills, data cleaning, and schema verification.
Hacker News Comment Review
Core competitive challenge: commenters immediately flagged Neon and Supabase already offer database branching, pressing Ardent on differentiation and moat.
Commenters noted the “zero risk to production” framing is incomplete: cloned DB access can still trigger real side effects via stored OAuth tokens or external API calls.
LLM agent read access to raw production data drew skepticism; write access was flagged as the sharper risk that Ardent’s isolation model at least partially addresses.
Notable Comments
@znnajdla: stored OAuth tokens in a cloned DB can trigger real customer-facing API side effects, undermining the blast-radius guarantee.
