Skip to main content
Postgres, including Supabase, AWS RDS, PlanetScale, and self-hosted. More databases coming soon.
Branch creation is under 6 seconds, regardless of source database size. First-time connector setup is a separate, one-time step. It takes longer depending on data size and write rate, but you only do it once.
No. Ardent uses logical replication to sync your data. Your application tables are never written to or modified. Ardent does install its own replication slot and DDL-tracking metadata on the source so schema changes replicate correctly; your data stays untouched.
They auto-suspend after 5 minutes of inactivity. When you reconnect, they spin back up instantly.
Yes. Create a branch and pass the connection URL to Claude Code, Cursor, or any agent. They can read, write, and run migrations without touching production.Ardent generates a unique connection string for each branch. Your real database credentials are never exposed. If a branch URL is ever compromised, your production data stays safe because the branch connection string has no access to the original database. An LLM will never see or have access to your real credentials.
No. Branches are created from a continuously synced replica of your production database, but once a branch is created it’s an isolated snapshot. Changes you make on the branch don’t affect production or any other branch.
As many as you need. Branches are efficient: you only pay storage for data you change on a branch.
Yes, just like git. Everyone on your team can see, switch to, and collaborate on branches. Use ardent invite to add people to your org.
Most of it. Branches include schema, data, grants, RLS, functions, triggers, and supported extensions. A few source features need an explicit setup choice: replica identity for tables without a primary key, and a small set of provider-specific extensions. Ardent flags these during connector setup so they’re decided before you branch.
Yes. You’d need to set up logical replication (WAL configuration, replication slots, schema drift, failure recovery; database replication is a nightmare), build a branching engine, build a connection proxy that routes to the right branch, handle auto-suspend and resume, manage credential isolation, and build a CLI on top of all of it. We’ve spent thousands of engineering hours building and maintaining this infrastructure. Ardent gives you all of it in one npm install.
Yes. See our Security page for full details.

​
Still have questions?

Contact us

Reach out at vikram@tryardent.com. We’re happy to help.