Receipts
Every claim on this site, sourced.
If a number appears on tai.ga, it appears here with its receipt: a public source, our own dated number, or a document available on request. When a claim stops being true, we remove it, and the removal is logged below.
15 claims · 5 public sources · 7 ours, dated · 3 on request
Live since May 13, 2026
Our number
First production customer traffic.
May 13, 2026internal, dated
Paying customers in healthcare and fintech
Our number
Customer names are under NDA. Vertical descriptors only; references available in the demo process.
June 2026internal, dated
2nd of 100 at Arctic15 2026
Arctic15 2026, published results
Taiga AI placed 2nd of 100 in the published results.
June 2026view source →
87% of AI-agent pull requests introduced at least one vulnerability
DryRun Security, March 2026
The Agentic Coding Security Report: 26 of 30 pull requests (87%) introduced at least one vulnerability. Agents tested: Claude Code, Codex, Gemini.
March 2026view source →
AI-generated code introduced a security flaw in 45% of tasks
Veracode, 2025
Tests across more than 100 models: AI-generated code introduced a security flaw in 45% of tasks.
2025view source →
EUR 100k annualized revenue · EUR 1M target by year end
Our number
EUR 100k is unaudited actuals as of June 2026. EUR 1M is our target for the end of 2026, not a claim.
June 2026internal, dated
22 checks
Our readiness bar
Derived from what regulators and platform teams demand. Full list on /governance and /gate.
June 2026internal, dated
Nine artifacts
Our number
Specification, user flows, architecture, technology decisions, data flow, threat model, DPIA, risk register, service blueprint.
June 2026internal, dated
7-year immutable audit archive
Taiga system description, section 11
Audit logs are immutable and retained for 7 years. Available to your security team on request.
June 2026on request
Regions outside the EU are denied by organization-wide guardrails
Taiga system description, section 6
AWS Control Tower landing zone, organization-wide guardrails, SCPs preventing security-control tampering, a Resource Control Policy data perimeter, and region controls. Available to your security team on request.
June 2026on request
Business ID 3607851-2
YTJ, the Finnish Business Information System
Taiga AI Oy, Business ID 3607851-2, Helsinki.
2026view source →
ISO 27001 in progress, SOC 2 planned
Taiga system description, section 15
Status, not a certification claim: ISMS established, ISO/IEC 27001:2022 certification in progress, SOC 2 Type II planned. Available to your security team on request.
June 2026on request
A signed engagement in national critical infrastructure
Our number
Sector-level description only. Details are part of the demo process.
June 2026internal, dated
One failed build, fixed and re-verified, in the XRM record
Taiga run record, project XRM
Initiative INI-021 in the XRM project: the build failed, the agent fixed it, and the re-run passed. Shown in the demo process.
July 2026internal, dated
6.3 million lost orders in one six-hour Amazon.com outage
Business Insider, March 2026
Internal Amazon incident documents, per Business Insider: a March 5, 2026 config change deployed outside change management cut orders 99% across North American marketplaces for about six hours. The figure is Amazon's own and not publicly confirmed.
March 2026view source →
Claims changelog
2026-07: artifact count corrected from eight to nine (service blueprint added).
2026-07: annualized revenue was planned for the home hero proof strip and not published. The number stays on /company and in this register.
2026-07: DryRun receipt corrected. Source relabeled from 2025 to March 2026, linked to the primary report instead of the press release, and the sample size (26 of 30 pull requests) added to the finding.
2026-07: the previous-company track record was removed from the site. The company page tells the general background; the single-company number belongs in investor materials.