Qase: the factory infographic
Test management for 2,000+ engineering teams, now checking every change a coding agent makes against what was asked.
What the company does
In normal terms
Test management platform used by 2,000+ engineering teams; launching Tiden, which records what was asked and checks every change made by coding agents against it.
Qase's new product Tiden keeps the original request and verifies that each change a coding agent makes matches it.
In lay terms
Qase keeps the shopping list and checks that the AI came back with only what was on it.
The risks it faces, especially from AI agents
In normal terms
- Checking the code, not the reach. Verifying changes against a request does not cover what the agent could have done with its access.
- Vague requests. If the original request is loose, any change can be argued to match it.
- Trust in the checker. Customers must trust that the verifier itself is complete and not bypassed.
In lay terms
- Checking the code, not the reach. The shopping matches the list, but the assistant still had your credit card all day.
- Vague requests. 'Get some food' allows almost anything.
- Trust in the checker. Who checks the person checking the receipts?
How RiskMandate helps
- Reachwhat it can actually access or affectWhat the coding agent can change: repositories, pipelines, secrets.
- Mandatewhat the business authorisedThe request Tiden records.
- Gapthe difference: the riskAccess beyond what the request needs.
- Barrierswhat really stands in the wayTiden's checks as review evidence; branch rules as technical ones.
- Provenancewho owns it, who reviewed it, which versionWho made the request, which agent, which version.
In normal terms
Tiden and RiskMandate share an idea: write down what was asked, then check. Tiden checks the changes; RiskMandate covers the agent's whole reach and the barriers around it. Together: a mandate per task and per agent. Our own site works this way, with a gate before every release.
In lay terms
Qase checks the shopping; RiskMandate also checks who held the credit card and what else they could have bought.
A first line for the conversation: Tiden records what was asked. We record what the agent could do. Together that is the full picture.
Sources and method
The facts in grey (what it does) are from the company map, which cites:
- websummit.com, read 2026-11-01: LIS26 appearance page: name, country, industry, website
- websummit.com, read 2026-11-01: listed on the 2026 featured startups list with its elevator pitch (the "what" field)
The risks and how RiskMandate helps are our analysis, written by dev@web-summit.indi on 3 November 2026 from those facts and RiskMandate's model as this site explains it (Reach, Mandate, Gap; an Agent Behaviour Policy in practice). They are not the company's own statements and name no incident. A person reviews each before it is used.