# Ardent Aiolum story: https://aiolum.com/story/ardent/ · added 2026-11-07 · updated 2026-11-07 **In short.** Ardent (Instant Postgres database copies (branches) for coding agents to test their code, United States (San Francisco, per its Y Combinator page)): Live with paid plans after a pivot from an AI agent, November 2026. Evidence grade E: no revenue figure was checked. Team: 1 founder listed (Vikram Chennai, Founder/CEO); team size 3 on the Y Combinator company page, November 2026, with one open founding-engineer role. Launched 5 May 2026; still running. Instant Postgres database copies (branches) for coding agents to test their code · United States (San Francisco, per its Y Combinator page) · AI-native · team of 2 to 10 · still running · group: Developer tools and coding agents - Outcome: Live with paid plans after a pivot from an AI agent, November 2026 (evidence grade of the headline number: E; no revenue figure) - Launch: 5 May 2026; months from launch to the outcome: 6 - Team: 1 founder listed (Vikram Chennai, Founder/CEO); team size 3 on the Y Combinator company page, November 2026, with one open founding-engineer role - Outside funding: Y Combinator, Spring 2026 batch; amount not published - Main factor: Domain experience - Meters, 1 to 4: evidence strength 1, copyable pattern 1, capital needed 2 - Tags: AI-native, Small team, Funded, Running, B2B, Developer tools Links: - Visit tryardent.com: https://www.tryardent.com/ **The product.** Ardent connects to an existing Postgres database on Supabase, AWS RDS, PlanetScale or a self-hosted server, keeps a read replica of it in sync, and creates isolated copies (branches) from that replica in under 6 seconds with one command, ardent branch create. Each branch has its own connection URL, so a developer or a coding agent can run migrations, backfills and data cleaning on real data without touching production. Idle branches suspend after 5 minutes. The pricing page lists a free Starter plan and a Scale plan at US$250 a month, both plus usage charges for compute and storage. **Why it worked.** The founder wrote that the idea came from the failure of the company's first product, an AI agent that wrote database code: the code looked right, but there was no safe place to test it, so customers would not run it in production. The launch post says that at many later-stage startups the founder talked to, most engineers now use Claude, Codex or Cursor for migrations and backfills, and a shared staging database cannot give each agent its own copy. Evidence grades: A = disclosed by a public company, a filing or a payment processor, or verified by one; B = two or more independent reports agree, or a journalist confirmed it; C = a founder claim that no one else verified; D = reported, not verified: one founder claim or a third-party estimate with no second source; E = no revenue figure found, so the headline is a non-money fact and the other facts carry their own grades; calc = computed on this page from graded facts. ## Summary Ardent sells database branching for Postgres: a branch is a full, separate copy of a database that you can change and then throw away, the way a git branch is a copy of code. Each branch uses copy-on-write, a storage method in which the copy shares the original's data blocks and stores only the blocks it changes, so the company says a copy of a database of any size appears in under 6 seconds. The buyers are engineering teams that let coding agents (AI programs such as Claude Code, Cursor or Codex that write and run code) write migrations (changes to the structure of database tables) and backfills (jobs that fill in or correct data in existing rows), and who want those agents to test on a 1:1 copy of production instead of on production itself. Vikram Chennai, a former machine-learning engineer who studied computer science at Cornell, founded Ardent in San Francisco in 2025, according to its Y Combinator page. Its first product was an "AI Data Engineer", a coding agent that wrote data pipelines, migrations and backfills; in the Y Combinator launch post of 5 May 2026 he wrote that customers would not put its untested database code into production and that "We churned almost 200K in ARR". The new product is the missing test environment, and in November 2026 the Y Combinator page lists the company in the Spring 2026 batch with a team of 3. No figure for the revenue Ardent has today was found, so this story is grade E: the product is live and the pricing page lists a paid plan, but its money is not verified. The churn sentence describes revenue that was lost, not revenue the company has. The page also shows earlier companies that sold managed databases, cloud development environments or AI coding help and failed. ## Pricing Ardent prices in November 2026, from the company's pricing page (grade C) | Plan | Per month, billed yearly (US$) | Per month, billed monthly (US$) | Limit | |---|---|---|---| | Starter | | 0 | US$30 one-time credit, up to 3 projects, community support, plus compute and storage | | Scale | | 250 | US$100 a month in credits, unlimited projects, Slack support, plus compute and storage | | Enterprise | | custom | dedicated infrastructure, BYOC, VPC, custom SLAs | | Compute, after credits | | | US$0.40 per CU-hour | | Storage, after credits | | | US$0.70 per GB-month | Both self-serve plans add usage charges after the included credits: compute at US$0.40 per CU-hour (1 CU is 1 vCPU and 4 GB of memory) and storage at US$0.70 per GB-month. The page shows no yearly billing. Enterprise adds unlimited compute and storage, deployment in the customer's own cloud (BYOC) or behind a VPC, custom SLAs and team-level access controls. ## How much revenue does Ardent make? The numbers, graded A three-person Y Combinator company that sells Postgres copies for coding agents after a failed first product, with no published revenue | Fact | Value | Grade | Note | Sources | |---|---|---|---|---| | Status, November 2026 | Live site with sign-up, a free Starter plan and a paid Scale plan | C | Home page and pricing page read 7 November 2026: 'Get started', 'Book a Demo', 'Backed by Y Combinator'. | [1, 2] | | Founder | Vikram Chennai, Founder/CEO | C | Y Combinator company page founder list; bio: 'Formerly ML Engineer, Cornell CS'. The launch post is signed by him. | [3, 4] | | Team | 3 people, November 2026 | C | Y Combinator company page data: team_size 3, one founder listed, one open role 'Founding Engineer - Product (Staff)'. | [3] | | Founded and location | 2025, San Francisco | C | Y Combinator company page: year_founded 2025, location San Francisco, batch P26 (Spring 2026), status Active. | [3] | | Launch of the current product | 5 May 2026, Y Combinator launch post | C | Launch 'Ardent - Clone any postgres DB of any size in <6s', created 2026-05-05, 16 votes when read. The founder shows a 1.6 TB database cloned in 6 seconds in a linked video. | [4] | | First product | An AI Data Engineer coding agent; customers left | D | Launch post, 5 May 2026: generated code 'would never be tested and was too unstable to put in production' and 'We churned almost 200K in ARR'. One founder sentence; no currency, no date and no figure for the revenue the company had. | [4] | | Prices | Starter US$0, Scale US$250 a month, Enterprise custom, all plus usage | C | Pricing page: compute US$0.40 per CU-hour, storage US$0.70 per GB-month. | [2] | | Named users | Supermemory and Surface Labs (launch post); a testimonial by the CTO of Zennagents (home page) | C | Named by Ardent only; none of these companies was found confirming it. | [4, 1] | | Supported databases | Postgres on Supabase, AWS RDS, PlanetScale or self-hosted | C | Documentation FAQ: 'More databases coming soon'. | [7] | | How a branch is made | From a read replica fed by logical replication, with copy-on-write storage | C | Architecture page: production data flows through a Kafka-backed pipeline into a read replica; branches are full Postgres instances cloned from it and share its storage. Idle branches suspend after 5 minutes (FAQ). | [6, 7] | | Funding | Y Combinator, Spring 2026; amount not published | C | The home page also quotes Zach Wilson, founder of Dataexpert.io: 'I'm investing in Ardent'. No round size was found. | [3, 1] | | Time from launch to the November 2026 status | 6 months | calc | Calculated: May 2026 to November 2026. | [4, 2] | How to read this table: product and price values come from the Ardent site and documentation read on 7 November 2026; founder, team size and launch date from the Y Combinator company page and launch post read the same day. The one money statement, the churn of the first product, is a single founder sentence (grade D). No value is grade A or B. ## When did Ardent launch, and how did it grow? Timeline From a failed AI data-engineering agent in 2025 to a database-copy service for coding agents, launched in May 2026. Each entry carries its grade. - **2025** (grade C [3, 4]): Vikram Chennai founds Ardent in San Francisco. Its first product is an AI Data Engineer, a coding agent that writes data pipelines, migrations and backfills. - **Before May 2026** (grade D [4]): Customers will not run the agent's untested database code in production. The founder later writes: 'We churned almost 200K in ARR'. - **5 May 2026** (grade C [4]): Y Combinator launch post for the new product: clones of any Postgres database in under 6 seconds, with Supermemory and Surface Labs named as users. - **Spring 2026** (grade C [3]): Ardent is in the Y Combinator Spring 2026 batch (P26). - **28 October 2026** (grade C [8]): The sitemap lists use-case pages for Claude Code, Cursor, CI/CD and Supabase, and comparison pages for Neon branching, Aurora cloning and database replicas. - **November 2026** (grade C [1, 2, 3]): The site sells Starter, Scale and Enterprise plans; the Y Combinator page lists 3 people. ## Why did Ardent work? ### Build the tool that the failed product needed The AI Data Engineer wrote database code that nobody could test safely, and the founder wrote that this is why customers left. Ardent sells the missing test environment to every team that now uses coding agents, not only to its own former customers. ### Copies from a replica, not from production Ardent streams changes from the production database into a read replica by logical replication (the Postgres feature that sends row changes to another server) and makes every branch from that replica, so many branches put no load on production. Branches share storage by copy-on-write and suspend when idle, so the customer pays mainly for changed data and active compute. ### The agent is a user The CLI works like git, a branch is handed to the agent as one connection URL that cannot reach production credentials, and the documentation publishes a SKILL.md file that Claude Code loads so that the agent creates and deletes its own branches. ## How it was built These details come from Ardent's documentation, its Y Combinator pages and the site's HTML. They are grade C. - A split architecture: a control plane run by Ardent (branch coordination, connection routing, policies, auth, usage and billing) and a data plane that holds the customer's data, on Ardent's cloud or in the customer's own cloud account. - The Ardent Replicator takes logical replication from production through a Kafka-backed pipeline into a read replica; custom event triggers replay schema changes (DDL) in order on the replica. - Each branch is a full Postgres instance cloned from the replica, with autoscaling compute and copy-on-write storage shared with the replica. - Connection URLs pass through Ardent's branch proxy, so a branch URL given to an agent cannot reach production or its credentials. - A CLI installed with npm, an API with API keys, and a SKILL.md file for Claude Code; the documentation is hosted on Mintlify. - The marketing site's HTML loads its files from /_next/static paths, the layout of a Next.js app; the open founding-engineer role lists Go and PostgreSQL as skills. Sources: [6, 7, 5, 3, 1] ## Who tried this before Ardent, and why did they fail? Three companies in our database of failed startups sold developers relief from setup or coding work and failed. The values below are from that database and are not independently verified. The failed startups come from our database of dead startups, retold here in our own words; Its entries are AI-assisted summaries of public sources, so they carry no evidence grade. ### FathomDB (2008 to 2011; funding none recorded; cause: Competition) - Promise: Managed cloud databases, so developers did not have to run database servers themselves. - Why it died: AWS and other large clouds offered the same service, and it did not have the money to keep up. - Record: ### Nitrous.io (2012 to 2016; funding US$8M; cause: Competition) - Promise: Cloud development environments, so developers could write code anywhere without local setup. - Why it died: AWS bought its competitor Cloud9 and gave it away free, while Nitrous.io spent its money trying to sell the same thing. - Record: ### Kite DevTool (2014 to 2024; funding US$21M; cause: Competition) - Promise: AI code completion inside code editors, years before GitHub Copilot. - Why it died: Its free product did not turn into paying customers, and GitHub Copilot had more distribution and stronger models. - Record: ## What changed FathomDB sold managed cloud databases and lost to AWS; Nitrous.io sold cloud development environments and lost when AWS bought Cloud9 and gave it away; Kite sold AI code completion and could not turn free users into paying ones before GitHub Copilot arrived, as the database records them. Each sold developers relief from setup work that a large platform could later give away. Ardent does not replace the database provider: it works next to Supabase, AWS RDS or PlanetScale and adds disposable copies for a new kind of user, the coding agent, which needs a separate copy for each task and, the founder wrote, makes teams ship "100x more DB code". The old risk remains: database providers offer their own branching and cloning, and Ardent's own site has comparison pages for Neon branching and Aurora cloning. ## Can one person copy Ardent now? **Verdict: Hard for one person: it needs deep Postgres replication work and money for infrastructure.** The method is general: when your own AI product fails because a piece of infrastructure is missing, sell that piece to everyone who has the same problem. Ardent's founder had built the agent first, so he knew what it lacked. The replication pipeline, copy-on-write storage and branch proxy are a large engineering job, as Ardent's own FAQ says. 1. Write down why customers did not trust your agent's output, and look for the missing tool, not a better prompt. 2. Build the smallest version of that tool that works with the providers customers already use, so that nobody has to migrate. 3. Make the agent itself a user: a CLI, a connection URL, and a skill file that the agent can read. 4. Charge a base plan plus usage, so that idle copies cost the customer little. **What is still open.** Other systems that coding agents cannot test safely today: copies of message queues, search indexes and object storage, and sandbox cloud accounts for infrastructure code. ## What could go wrong for Ardent? - **What is not verified.** No figure for the revenue Ardent has today was found. The only money statement is one sentence by the founder in the Y Combinator launch post of 5 May 2026 about the earlier product: 'We churned almost 200K in ARR'. Churn is recurring revenue lost when customers cancel; the sentence gives no currency, no date and no figure for the recurring revenue the company had, so it is not used as a headline. No TrustMRR profile (the pipeline's list of TrustMRR slugs has no Ardent entry), filing, round announcement or interview with figures was found. Supermemory, Surface Labs and Zennagents are named as users by Ardent only. A reader could look for a seed-round announcement or a customer case study that names a client. - **Endorsements on the home page.** The home page quotes a Head of Data at Chevron, the CEO of Openledger, the CTO of Zennagents and an investor, Zach Wilson of Dataexpert.io. None of these was checked with the person or the company, and the Chevron quote does not say that Chevron uses Ardent. The 'Customer Impact' counters (downtime, release speed, hours saved) show 0 in the downloaded HTML because a script fills them, so their values could not be read. - **Competition.** Database providers sell their own copies: Ardent's sitemap lists comparison pages for Neon branching, Aurora cloning and database replicas, and its FAQ says a team could build the same thing with enough work. On this site the closest stories are developer-tools stories about infrastructure for coding agents, such as Omnara (a control plane for agents) and Metorial (an MCP gateway); neither copies databases. - **Dependence on model providers.** Ardent runs no language model itself in the sources read; it is infrastructure built for coding agents, which is why it is listed as AI-native. Its demand depends on agents made by others: the documentation names Claude Code and Cursor, and the launch post names Claude, Codex and Cursor. It also depends on database providers that allow logical replication; Supabase, AWS RDS and PlanetScale are the supported connectors. ## Sources 1. Ardent: Database branching for coding agents (home page) — https://www.tryardent.com/ (grade C). Read in full on 7 November 2026. Source for the product claims, the supported providers, the quotes, the counters and the Y Combinator badge. 2. Pricing | Ardent — https://www.tryardent.com/pricing (grade C). Read in full on 7 November 2026. Source for the plans, credits and usage prices. 3. Ardent: Database sandboxes for Agents | Y Combinator — https://www.ycombinator.com/companies/ardent (grade C). Read the page data on 7 November 2026. Source for the founder and his title, team size 3, year founded 2025, San Francisco, batch P26 and the open founding-engineer role. 4. Ardent launch post on Launch YC, 5 May 2026: Clone any postgres DB of any size in under 6 seconds — https://www.ycombinator.com/launches/QE3-ardent-clone-any-postgres-db-of-any-size-in-6s (grade C). Read in full on 7 November 2026. Source for the earlier AI Data Engineer, the churn sentence, the named users, the 1.6 TB demonstration and the launch date. 5. AI agents, Ardent documentation — https://docs.tryardent.com/workflows/ai-agents (grade C). Read in full (markdown version) on 7 November 2026. Source for the URL handoff and the SKILL.md for Claude Code. 6. Architecture, Ardent documentation — https://docs.tryardent.com/architecture (grade C). Read in full (markdown version) on 7 November 2026. Source for the control plane, data plane, Replicator, Kafka pipeline, read replica and copy-on-write branches. 7. FAQ, Ardent documentation — https://docs.tryardent.com/faq (grade C). Read in full (markdown version) on 7 November 2026. Source for the supported databases, branch time, auto-suspend after 5 minutes and the npm install. 8. Ardent sitemap — https://tryardent.com/sitemap.xml (grade C). Read in full on 7 November 2026. Source for the use-case and comparison pages and their 28 October 2026 date; the comparison pages themselves were not read. 9. Database of failed startups, local export — /method/#dead (grade C). Local export. AI-written summaries, not independently verified. Source for the failed predecessors. Contact: aiolum@livyden.com. Run Ardent? Send corrections or a verified figure to aiolum@livyden.com (subject: Correction: Ardent).