How to evaluate an AI governance platform

Every vendor in this category claims discovery, assessment, enforcement, monitoring and audit. The words have converged because the analyst category has, but underneath the words are three different product lineages with different strengths, and a feature checklist cannot tell them apart. Questions can. This guide sets out the ones that expose the differences fastest, and they work on any vendor, including Aicura.

On discovery: signals or self-reporting?

Ask the vendor to name the sources their discovery actually reads, and to show a finding traced from the original signal to the register. Discovery ranges from a form teams fill in, to scans of a single source, to correlation across identity providers, device management, outbound network traffic, cloud inventories and finance systems. The width matters because shadow AI does not announce itself in any single source, and the correlation matters because raw hits without resolution just move the work. Ask what share of findings in a reference deployment came from sources other than self-reporting.

On enforcement: does it act on traffic, or on paperwork?

Ask what happens to a prompt that violates policy at 2pm on a Tuesday. For most of the category the answer, once unwound, is that nothing happens to the prompt, because “enforcement” means an approval workflow that ran before deployment or a review task created after the fact. Real enforcement on live traffic sits between your people or systems and the AI model, and blocks, redacts or constrains the request itself. Both models are legitimate, but they are different products, and a vendor should be able to say plainly which one they are. Follow up by asking to see an enforcement event fire live, and where the record of it lands.

On agents: is the governance a record or a constraint?

Ask whether the platform can stop an agent doing something, or only record that it did. Agent registries are now common. Limits on which tools an agent may call and what it may do while it runs, suspension of a misbehaving agent and a decision log of what an agent actually did are much rarer, and they are what the risk of systems that act calls for. Ask to see an agent’s permitted tools changed and the change take effect, and ask what record exists when someone later asks why an agent did something.

On frameworks: loaded data or a logo wall?

For the frameworks you need, ask to see the content operating inside the product, not the logo on the website. Framework coverage claims range from content genuinely wired into assessments and reviews, to mappings maintained on request, to a list. The question bites hardest outside the EU and the US, because much of the category’s content was written for those two and national frameworks elsewhere are often thin or missing. Ask to see an assessment run against the framework that matters to you, on your systems.

On evidence: who has to be trusted for it to hold?

Ask whether a third party can check the audit trail without access to the vendor’s systems. The category’s standard words here are immutable, tamper-evident and system of record, and they almost always describe an append-only log inside the vendor’s own infrastructure. That is a promise about the vendor’s database, and relying on it means trusting the vendor. Cryptographically verifiable evidence is different in kind, using hashes anchored externally, timestamps from an external service, signatures with external keys and a verifier the third party can run themselves. If a vendor’s answer is a description of access controls, you have your answer. The companion guide on what makes AI evidence independently verifiable covers the distinction in full.

Then ask the continuity version. If the vendor disappears in five years, what happens to your evidence? The answer reveals whether the record’s durability depends on the vendor’s survival.

On buying: can you start, or only be sold to?

Ask what the smallest real commitment is, and whether you can make it without a sales process. Much of the category is sold only through an enterprise sales process, with entry prices set for large organisations. That is a fine model for some buyers and a wall for others. A free or low-floor entry means the evaluation can be your own hands on your own systems rather than a scripted presentation, which improves every other question on this list.

Running the evaluation

Ask every vendor the same questions, in writing, and make the shortlist show rather than describe. One real piece of work end to end beats any presentation, so register real systems, run a real assessment against your real framework, fire a real guardrail, produce a real evidence pack and hand it to someone sceptical. Where a vendor is weak, listen for whether they say so plainly. A vendor who concedes a real limitation and explains the mitigation is telling you more about the next five years of the relationship than one who has no weaknesses at all. Before any of that, know your own starting point. A maturity assessment shows which of the seven areas you are weakest in, which is where the evaluation should press hardest.

Where Aicura fits

Run these questions against Aicura the same way you would against anyone else. The discovery question can be tested on the free Register tier with your own sources connected, by checking which AI tools discovery reports and how each one reaches the register. The framework question has a plain answer by plan and country. Privacy carries your country’s rules on automated decisions. Essentials adds national frameworks, such as the EU AI Act in the EU or Australia’s Guidance for AI Adoption. Pro adds ISO/IEC 42001, the NIST AI RMF and sector and breach notification frameworks. Your country’s pricing page lists them. Enforcement, agent limits and the Evidence Vault, Aicura’s sealed store of evidence snapshots, are Pro capabilities, and for those the proof of concept starts with a conversation.

Aicura provides guidance, not legal advice, and does not certify or audit. It issues no compliance verdicts or scores by design, so if your evaluation requires a product that asserts pass or fail, that is a real difference to weigh, and we would rather say so here than surprise you in month three.

A note on this page

This guide is written by a vendor in the category it describes, so read it the way you would read any vendor’s evaluation advice, as a set of questions to ask everyone, us included. It is general information, not advice, and the right weighting of these questions depends on your organisation’s obligations and risk.