> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryardent.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Common questions answered

<AccordionGroup>
  <Accordion title="What databases does Ardent support?">
    Postgres, including Supabase, AWS RDS, PlanetScale, and self-hosted. More databases coming soon.
  </Accordion>

  <Accordion title="How long does it take to create a branch?">
    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.
  </Accordion>

  <Accordion title="Does branching affect my production database?">
    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.
  </Accordion>

  <Accordion title="What happens to idle branches?">
    They auto-suspend after 5 minutes of inactivity. When you reconnect, they spin back up instantly.
  </Accordion>

  <Accordion title="Can I use branches with AI agents?">
    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.
  </Accordion>

  <Accordion title="Do branches stay in sync with production?">
    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.
  </Accordion>

  <Accordion title="How many branches can I create?">
    As many as you need. Branches are efficient: you only pay storage for data you change on a branch.
  </Accordion>

  <Accordion title="Does my team share branches?">
    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.
  </Accordion>

  <Accordion title="What Postgres features work on branches?">
    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.
  </Accordion>

  <Accordion title="Can I build this myself?">
    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`.
  </Accordion>

  <Accordion title="Is my production data safe?">
    Yes. See our [Security](/security) page for full details.
  </Accordion>
</AccordionGroup>

## Still have questions?

<Card title="Contact us" icon="envelope" href="mailto:vikram@tryardent.com" horizontal>
  Reach out at [vikram@tryardent.com](mailto:vikram@tryardent.com). We're happy to help.
</Card>