AI compliance software that adapts to your AI system’s obligation level. The AI compliance software measures compliance progression you can show leadership, and the evidence and audit history build themselves as you work. Built for AI providers, deployers, importers, and GPAI providers under the EU AI Act.
A platform that operationalizes the obligations imposed by AI regulations and standards. It is the working surface where compliance gets done, not a static policy library.
Unlike generic GRC tools, AI compliance software ships with the AI-specific regulatory content built in and scopes controls to AI-specific dimensions: risk classification, provider-versus-deployer role, and component-level granularity. AI Sigil is built around this concept: each AI system in your inventory carries the controls relevant to it, and nothing else.
AI Sigil treats every control as a living object. The AI compliance software reshapes the guidance text, regulatory sources, and assessment questions around the AI system you are evaluating:
The control assessment matches your situation, not a generic worst-case template.
Every control has one of four statuses: not started, in progress, done, or rejected. The AI compliance software aggregates control statuses into a compliance progression metric at every level of your portfolio:
Filter the dashboard by status, framework, owner, risk level, or overdue date.
Progression, not a score. The aggregate is a status progression, not a weighted compliance score and not a pass/fail certification. It reflects actual assessment status, not whether a form was opened. When leadership asks “where are we”, the number is grounded in the same records the auditor will see.
AI compliance software organizes controls in two layers inside AI Sigil, with two complementary roles. These controls also align with ISO/IEC 42001, the international AI management system standard. Both run in the same portfolio, with their own status, evidence, and audit trail.
Organization-wide governance, independent of any specific AI system
Answer the question “is your organization set up to govern AI?”. Triggered by activating a framework on the company.
Examples
One AI system at a time, scoped by risk classification
Answer the question “is this particular AI system compliant with the framework it carries?”. Triggered by activating a framework on the AI system.
Examples
Most tools were not built around AI systems with regulatory obligations as first-class objects. The “AI compliance software” category covers several distinct profiles:
The AI compliance software you choose must scope obligations to your AI system’s role and risk class, not bundle a generic worst-case template. A high-risk provider, a limited-risk deployer, a GPAI provider, and a minimal-risk system each carry different duties, and your software has to surface only what applies.
It must produce immutable evidence, not editable forms. Auditors look for tamper-proof submissions and a complete answer history that ties every record back to a regulatory article. Editable evidence is not evidence.
And the AI compliance software has to make the audit trail a by-product of how your teams already work, not a separate task. Software that bolts logging on top of policy documents shifts the maintenance cost back to your team.
Every control traces back through a chain: control to requirement to framework instance to parent framework. The requirement identifies the regulatory theme (for example, “Risk Management”), and the control implements the specific obligation. The traceability is built in, not configured by the user.
Each control contains content blocks (guidance text, regulatory sources, assessment questions) tagged with risk tiers. When an AI system is classified, only blocks matching its tiers are visible. A minimal-risk system sees screening-level content. A high-risk system sees the full depth of guidance and assessment questions.
Evidence is any document, screenshot, test result, or file that demonstrates a control has been implemented. It is uploaded as an attachment and linked to the specific control it supports. The platform maintains the link so you can always trace which evidence supports which obligation.
The AI compliance software stores form submissions as immutable snapshots: once submitted, they cannot be modified. Answer history records every change with the previous value, new value, timestamp, and who made the change. The application layer enforces append-only behavior for all compliance records.
Yes. The AI compliance software stores answers per entity and per question, not per user session. Multiple team members can answer different questions on the same control. The audit trail records who answered each question and when.
The current control library is maintained by AI Sigil and derived from regulatory analysis. Custom-control authoring is on the roadmap. Evidence and assessment features work with any control in the library.
Yes. Each framework activation tracks its own set of controls. The portfolio view aggregates completion across all active frameworks for an AI system, giving you both per-framework and cross-framework compliance visibility.
All assessment answers, evidence, and form submissions are preserved. Deactivating a framework only removes the rollout link. If you reactivate the framework, the controls reconnect to the existing data with all answers and evidence intact.