What they do
evaluates, monitors and red-teams AI apps
How close to us
4, very close
checks only; evals and observability for AI quality, enterprise and developer led
Wedges
- W2 Seeing whether your AI agents actually produce direct
- W1 Trusted 24/7 coding for small startup teams adjacent
Who buys
- Firm size
- enterprise
- Buyer type
- developer
- Role
- head of AI quality or AI engineering lead (product managers run it too at Finom)
- UK
- not known
Their own description (from YC)
Confident AI provides enterprises an all-in-one platform to evaluate, observe, red team, and govern AI applications. Built by the creators of DeepEval (16k stars, 8m monthly downloads), Confident AI is able to offer battle-tested, open-source evaluation algorithms while providing the infrastructure needed for teams to stay confident their AI systems.
Full teardown
Confident AI (YC Winter 2025): teardown vs XMarts
In one line: Confident AI sells a platform that tests, watches and red-teams the AI apps other companies build, on top of its free open-source tool DeepEval [site] [yc]. Threat: 2, because it owns the "is my AI working?" space that W2 lives in, but it checks AI apps for end users and does not do or learn from the work (checks only) [site] [docs]. A YC partner will name it for W2.
1. Fact file
| Item | Finding | Source |
|---|---|---|
| What they say | "AI quality platform built for enterprise teams." YC line: "The LLM Eval and Observability Platform for AI Quality." | [site] [yc] |
| Founded, team, funding | Founded 2024, San Francisco, 7 people on the YC page. $2.2M seed in March 2025 (YC, Flex Capital, Liquid 2, January Capital, Rebel Fund and others). One aggregator says $2.7M total, so the total is not firm. No later round found. | [yc] [press] |
| Founders | Jeffrey Ip (CEO, creator of DeepEval, ex-Google and Microsoft engineer) and Kritin Vongthongsri (CTO, AI researcher, Princeton). What YC likely saw: a tool with real open-source pull before the company existed (inference from the stars and downloads they claim). | [yc] [press] |
| Customers | Case studies on the site: Finom, RLDatix, Amdocs, Humach, Supernormal. They claim DeepEval runs in CI at BCG, AstraZeneca, AXA and Microsoft. | [site] [yc] |
| Price | Public. Free; Starter $200 a month; Team $2,000 a month; Enterprise custom. Trace storage $1 per GB-month. | [pricing] |
| Path | No rename found. Eval tool (DeepEval) → eval platform → observability → red teaming and governance → monitoring and drift detection (launch weeks, Sep to Oct 2026) → teaser that agents will "do your work" on the platform. | [site] [blog] |
| Open source | DeepEval: 19.0k GitHub stars, Apache-2.0. The YC page claims 8M monthly downloads; the launch post claims 3M; a bio claims 400k. Self-reported and inconsistent. | [github] [yc] |
2. Their proposition, reverse engineered
| Part | What they do |
|---|---|
| Who buys | AI engineering teams, with a head of AI quality or AI governance as the signer at larger firms [site] [yc]. Finom shows product managers using it too [case]. |
| The pain | Teams ship AI apps they can not trust. Each team builds its own eval kit, which fails at company scale (RLDatix CTO, paraphrased) [site]. An improvement cycle waited on engineers for days [case]. |
| The promise | Standardise AI quality across the whole company: test before release, watch after release, block what fails [site]. |
| How it works | Open-source DeepEval runs in CI. The cloud platform adds tracing (OpenTelemetry), 50+ metrics, simulated multi-turn chats, drift alerts, red teaming and release gates. SaaS or self-hosted [site] [docs]. |
| The output | Scores, ranked failures, alerts, audit trails and a release gate. Not a changed agent. The docs describe no automatic fix to prompts or code [docs]. |
| Proof style | Time and cost counts: "10 days to 3 hours" (Finom), "cut LLM cost by 80%" (Supernormal). All "they claim" [site] [case]. |
| Who sells it | Open-source pull plus self-serve plans, with sales for Team and Enterprise [pricing]. Open roles: developer advocate, open-source growth, one founding GTM [jobs]. |
| Price model | Flat monthly tiers plus usage ($1 per GB-month of traces). Enterprise is custom, on-prem is allowed [pricing]. |
| The story | AI quality is a company-wide standard, not a test script. Open-source metrics are the base, the platform is the system of record [site]. |
3. Positioning
- Category they claim: AI quality platform: evals, observability, red teaming, governance [site].
- Category a YC partner would put them in: LLM evals and observability, a dev tool in the Langfuse, LangSmith, Braintrust and Arize group (their own comparison pages name those rivals) [site].
- What they want to be known for: the standard way to prove an AI app is good enough to ship and still good a month later.
- Where they sit on the map: L1/L2/L3 = 1/0/1. Buyer: enterprise by pitch, but the $0 and $200 plans reach small teams. Developer-led, with some business users [site] [pricing].
4. Three layers vs ours
| Layer | Them (score + evidence) | Us (Marton's logs show) |
|---|---|---|
| L1 Company brain | 1. Uses the customer's own traces to build test datasets and version metrics and prompts [site] [pricing]. No lasting memory of the organisation that other work reads. | A vault of about 1,400 pages, 112 call transcripts and about 8,700 customer quotes, searchable by meaning. |
| L2 Agent orchestration | 0. They test and simulate other people's agents. They do not run a team of agents. The "Mr. Bits & Bytes" post says only that agents will do work "soon", with no detail [blog]. | About 5,600 jobs run by agents from three makers, each checked by a different AI, then automatic tests. |
| L3 Execution and learning | 1 (checks only). Scores, ranks failures with "root causes and suggested fixes", alerts on drift [blog] [docs]. The docs describe no change made for the customer, and no step that feeds results back into the next run. | Every failure gets a record and an automatic check (about 160 incident records). Offer feedback lines fell from 44 to 18 as rules were added. Only about 15% of jobs reached the main code. |
5. Same and different
| Topic | Same or different | Them | Us |
|---|---|---|---|
| Core belief | Same | AI output can not be trusted unchecked [site]. | Same: Marton's logs show a different AI checks every agent job. |
| What is watched | Different | LLM apps built for their customers' users [site]. | Agents that do our own work (jobs, merges, cost) per Marton's logs. |
| Do the work | Different | No. Measures and alerts [docs]. | Yes, on Marton's own business. No customer run yet. |
| Learning loop | Different | Humans turn failures into new evals; the guide says so [blog]. No automatic loop found (UNVERIFIED that none is planned). | Failures become rules and checks; offer feedback lines fell 44 to 18 (Marton's logs show). |
| Buyer | Different | AI engineering leads and AI quality heads, enterprise-led [site]. | Target: SMEs and scale-ups (brief). No customer yet. |
| Open source | Different | DeepEval and DeepTeam, 19.0k stars [github]. Free pull into the paid product. | None. |
| Price and speed | Different | Self-serve from $0; Team $2,000 a month [pricing]. | Not set. |
| Proof | Different | Cycle time and cost, with named customers (they claim) [site] [case]. | No customer number yet. |
| Delivery | Different | Software, with docs and migration guides [site]. | The system plus the two founders. |
| Size | Different | 7 people, $2.2M seed [yc] [press]. | Two founders. |
6. Wedge overlap
| Wedge | Fit | Why |
|---|---|---|
| W2 Seeing whether your AI agents actually produce | direct | Same words: traces, alerts, drift, cost. They watch AI apps for end users; W2 watches agents that do work. Buyers differ, but their product could cover it with new traces (inference) [site] [blog]. |
| W1 Trusted 24/7 coding for small startup teams | adjacent | Their release gate and CI evals make AI output safer to ship [site]. They do not write or land code. |
7. Whitespace (where they stop)
- Layer gap: they check and rank; they do not do the work or change the agent [docs] [blog]. To own it we need one customer workflow run by our agents for 4+ weeks, with failures turned into rules the customer can see.
- Number gap: their public numbers are cycle time and token cost, not money earned or work finished [case]. To own it we need one before/after business number a customer would sign, for example jobs finished per week.
- Buyer gap: not a true gap. Free and $200 plans reach small teams [pricing]. The open buyer is the one running agents as workers (not shipping an AI product), which they do not target yet (inference from their pages).
- Price and speed gaps: not gaps. Self-serve start and a free tier [pricing].
8. For the YC application
- Proven today: Marton's logs show his system runs about 5,600 agent jobs, each checked by a different AI and then automatic tests, and that about 160 incident records each added an automatic check. Their public product scores AI output and alerts; it does not describe fixing the agent or doing the work [docs].
- Draft answer to "how are you different from Confident AI?": DRAFT. "Confident AI tells you when your AI is wrong. Our system already does the work, checks it with a second AI, and turns each failure into a rule, every day, on our own business." Founders say it their own way.
- Future claim (needs proof): "Agents do your work and get better from every failure, with a number you can see." Needs one customer workflow run for 4+ weeks with a before/after number, and failures visibly turned into rules.
- What we understand that they don't: watching is not enough; a check must change the next run.
provenon Marton's own work (offer feedback lines fell 44 to 18 as rules were added);needs proofon a customer. - Copyability (M3): medium. Watching agents is easy for them: traces, alerts and drift tools are already shipped [blog]. The loop (do the work, learn from rejections) is harder: it pulls them from a neutral "judge" role toward doing the work, and their own teaser says agents are coming "soon" [blog] (inference). They are small (7 people) but open-source led, so they ship fast: seven launches in about four weeks [blog]. If our edge is only W2 observability, copyability is easy. Not
hard, so M3 can not score above 3 against Confident AI alone. - Why now (M4): None found in this teardown. Do not use "more companies ship agents": that is general AI progress.
- Do not claim: "no one watches AI agents" (they and others do). "We do evals better" (no test against theirs). "Our loop is automatic end to end" (only about 15% of jobs reached main; merges were unreliable in October per Marton's logs). Any customer result.
9. Ideas worth taking
- Open-source core as the way in: DeepEval is free, and the paid platform sits on top [github] [site].
- Let non-engineers run the check. Finom's product managers run evals without a ticket [case]. That fits W6.
- Show a gate that blocks a bad release, and make the audit trail the buyer-facing proof [site].
10. Unknowns
- What "Confident Monitor" and "Jev-as-a-Judge" really are. They appear in the blog list (Oct 13 and Sep 25, 2026) but I could not open the posts. Details above are from the listing only [blog].
- What the promised agents will do on the platform. Look for the next launch week.
- Real revenue and customer count ("hundreds of companies" is their claim [jobs]). The funding total also conflicts between sources.
- UK or Europe sales. Finom is Amsterdam-based [case]; no UK office or customer confirmed. Check the careers and customer pages.
- Whether any customer uses it to watch coding-agent fleets, which is the W2 buyer.
Sources
- confident-ai.com [site]
- Pricing [pricing]
- YC company page [yc]
- YC jobs page [jobs]
- Blog index, read 2026-10-19 [blog]
- Say Hello to Mr. Bits & Bytes, Oct 1, 2026 [blog]
- Docs [docs]
- Finom case study [case]
- Supernormal case study (title only seen in search) [case]
- DeepEval on GitHub [github]
- Seed round, $2.2M, Mar 2025 [press]
- Seedtable funding record [press]
Technical detail
- Slug
- confident-ai
- Lens hash
- 179096c479
- Pass
- deep
- Stale
- no