Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-08-03 · high
The founder's last AI agent reached $200,000 in yearly revenue, then stalled because it couldn't verify its own SQL.
Why now: Ardent surfaces now because rival Postgres platforms already let agents touch live databases through MCP, and a six-second clone claim is a direct challenge to that approach.
Ardent clones a 1.6-terabyte production Postgres database in under six seconds, per a report on the startup's launch. Founder Vikram Chennai knows why that matters. His last company, an AI agent called AI Data Engineer, reached $200,000 in annual recurring revenue, then stalled. It had no safe way to verify the SQL it generated.
Each clone is isolated at both compute and storage, so testing against it can't touch the original database. It also matches production exactly, not a sampled copy, which matters because SQL that passes against fake data can still break on the real thing.
Storage costs nothing until data changes, and compute for an idle clone scales to zero. That keeps a full test copy nearly free to spin up and tear down.
Crane Venture Partners led a $2.15 million pre-seed round for the two-person company, which came out of Y Combinator's Spring 2026 batch.
PlanetScale, Neon and Supabase have all shipped MCP servers that let AI agents query and migrate databases directly, so Ardent isn't the only way in. Branching speed, not raw access, is what will separate them, and Ardent's six-second number so far has no independent benchmark behind it.
Each link below shares sources, entities, or timing with this story.
Supabase supports Postgres / Shared entities / Earlier coverage / Tension
Linked by a graph relationship (Supabase supports Postgres); both cover Neon, PlanetScale, Supabase; earlier Neon coverage from 2026-03-27.
Supabase supports Postgres / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Supabase supports Postgres); both cover MCP, Supabase; overlapping topics (agent, company).
Linked by a graph relationship (Supabase supports Postgres); both cover MCP, Supabase; overlapping topics (agent, data).
Ardent uses Postgres / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Ardent uses Postgres); both cover MCP, Postgres; overlapping topics (agent, data).
Ardent uses Postgres / Shared entity: Postgres / Shared topic / Earlier coverage / Tension / Downstream implication
Linked by a graph relationship (Ardent uses Postgres); both cover Postgres; overlapping topics (agent, company).
Anthropic released MCP / Shared entity: MCP / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Anthropic released MCP); both cover MCP; overlapping topics (agent, data).
Claude Code uses MCP / Shared entity: MCP / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Claude Code uses MCP); both cover MCP; overlapping topics (agent, cost).
VS Code supports MCP / Shared entity: MCP / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (VS Code supports MCP); both cover MCP; overlapping topics (agent, data).