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.
26 claims · 15 public sources · 7 ours, dated · 4 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 readiness questions
Our evidence review checklist
A published checklist across governance, security, build and run. It is not one universal automated release gate. Check execution and evidence depend on the project and its configured pipeline.
September 2026internal, dated
Eight setup documents; optional service blueprint
Taiga new-project setup workflow
New-project setup requires specification, user flows, architecture, technology decisions, data flow, threat model, DPIA and risk register. The service blueprint is optional; imported reality documents follow a separate workflow.
September 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 →
Bedrock Guardrails are configured but not enforcing
Taiga system description, section 10
Two guardrail profiles are built and versioned: one user-facing with prompt-attack detection and credential/card/national-ID blocking, one for backend agents. The kill switch is on in dev, staging and production while support cases with AWS are open, so no guardrail is enforcing today. Available to your security team on request.
August 2026on request
Public price list, September 2026
Aurora rate card v1.0 and master service terms v1.0
Published v1.0 rate card, effective 6 September 2026: Learn from EUR 2,000 a month; Learn with Deliver + Operate from EUR 6,000. Scale permits 1–8 units; Portfolio includes 80,000 Aurora. The always-on cap stops consumption-driven work until an authorized resolution. Step-ups require administrator acceptance under the master terms. Prices exclude VAT; the signed Order Form governs.
September 2026view source →
Eight required setup documents, with optional design work
Taiga setup workflow and product documentation
New-project setup requires specification, user flows, architecture, technology decisions, data flow, threat model, DPIA and risk register. Service Blueprint and Look & Feel are optional. Imported reality documents follow the codebase-analysis workflow.
10 September 2026view source →
Code-derived documents, cited findings and an automatic initial backlog
Taiga codebase import documentation
Import derives versioned reality documents with file citations, then runs repository scans and an assessment against published policies. The initial backlog waits for that evidence and references the findings and gaps it addresses. Your team can then review and prioritize the work.
10 September 2026view source →
Grouped findings, cited policy gaps and independent verification
Taiga Maintaining documentation
Maintaining groups dependency, secret, code and infrastructure findings into work your team can act on. Fix queues a remediation initiative. Eligible urgent dependency updates can enter the queue automatically. Building and merging follow the configured controls. A fresh scan verifies scanner findings; a new assessment against refreshed documents verifies policy gaps.
10 September 2026view source →
One initiative queue, with configurable building and merging
Taiga initiative delivery workflow
The board groups work into Build, Queue, Todo and Backlog. Taiga plans and builds one initiative at a time per project, using its documents, policies and repository context. Plans can wait for approval, or build on their own. The next queued initiative starts after the preceding pull request merges.
10 September 2026view source →
Taiga tracks connected GitHub deployments
Taiga deployments documentation
Taiga mirrors deployment records and status from connected GitHub repositories. The configured customer pipeline executes deployment and any environment approval steps.
7 September 2026view source →
Configured URL checks and browser signals
Taiga monitoring documentation
Application availability checks require a configured URL. Browser signals require the Taiga beacon to be installed. Monitoring and repository scans answer different questions; missing setup or stale data must remain visible.
7 September 2026view source →
Microsoft Entra ID federation and Google sign-in
Taiga members and access documentation
Microsoft Entra ID connects against a verified organization domain. Google sign-in is available separately. Organization roles govern actions and teams govern project access. Require SSO blocks password sign-in for affected members, with an owner recovery exception.
7 September 2026view source →
Conversational User Flows with diagrams and published versions
Taiga User Flows documentation
From a published specification, Taiga drafts user journeys with diagrams, decisions and steps. Edit in conversation alongside the document, inspect the changing draft and publish the version that architecture and later planning will use.
10 September 2026view source →
A composed Look & Feel screen with editable design choices
Taiga Look & Feel documentation
Taiga drafts choices for the overall look, navigation and form conventions, then proposes a combination as one rendered screen. Change individual choices, compare page and form views, and publish the direction that planning and building use.
10 September 2026view source →
Claims changelog
2026-09: clarified eight required setup documents and optional service blueprint; distinguished the 22 readiness questions from project-specific automated checks.
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.