Product · ComplianceEngine

The compliance layer that ships with your model.

ComplianceEngine integrates directly into your MLOps pipeline. Every commit is classified, audited, documented, and gated — automatically — against the EU AI Act and ISO 42001.

Built for scale-ups and regulated enterprises across the EU. ComplianceEngine runs on EU-hosted infrastructure or inside your own cloud or on-premise environment; customer data does not leave the EU unless you deploy it elsewhere yourself. Free for one system, from €290 per month.

The Compliance Pipeline

Illustrative run · credit-scoring model, high-risk
Step 01
Commit
Model and dataset metadata captured at every push.
Step 02
Profile
Automated risk classification under EU AI Act categories.
Step 03
Audit
Bias, robustness, and Annex IV checks gated against thresholds.
Step 04
Document
Evidence package and technical file generated automatically.
Step 05
Deploy
Live monitoring with drift, incident, and post-market reporting.
compliance.audit › model:credit-scoring-v3.2
✓ risk_classification        High-Risk · Annex III §5(b)
✓ technical_documentation    annex-iv.json generated (87 fields)
✓ data_governance            EU 2024/1689 §10  PASS
✓ bias_metrics               disparate_impact 0.94  PASS
✓ robustness                 adversarial_acc 0.91  PASS
! human_oversight            requires reviewer signoff
✓ post_market_monitoring     telemetry attached
Annex IV Coverage
100%
Audit Latency
38s
Open Findings
1

Annex IV Automation

Generates and maintains the technical file with every model version.

CI/CD Gates

Block non-compliant releases before they reach production.

Risk Classifier

Assigns EU AI Act tiers based on use case and data flows.

Bias & Robustness

Standardized fairness, adversarial, and stability evaluations.

Post-Market Monitoring

Drift, incident, and usage telemetry tied to your obligations.

Auditor Workspace

Single source of truth your DPO and external auditors share.

Questions buyers ask

What it does, who it is for, what it costs.

What does ComplianceEngine actually do?

ComplianceEngine runs inside your CI/CD pipeline. On every model version it classifies the system under the EU AI Act risk tiers, runs bias and robustness evaluations against thresholds, generates and updates the Annex IV technical file, and gates the release until the checks pass or a reviewer signs off. After deployment it attaches drift, incident and usage telemetry to the post-market monitoring obligations, so the evidence an auditor asks for is produced by the pipeline rather than assembled by hand.

Who is ComplianceEngine built for?

Scale-ups and regulated enterprises across the EU that build or fine-tune AI systems and need evidence that operates over time rather than a one-off document: providers of Annex III high-risk systems, deployers who have become providers under Article 25, and organisations preparing for an ISO/IEC 42001 certification audit or an ISAE 3000 assurance engagement.

Which features should an EU AI Act compliance tool have?

Five, in order: risk classification with its reasoning rather than a score; Annex IV technical documentation generated from the system's own artefacts and kept current on every version; a risk register and Article 14 human-oversight records; post-market monitoring tied to the specific obligations of the system; and a path to an audit — internal first, then external — on the same evidence. Hosting in the EU or in your own environment, and pricing per AI system rather than per seat, are the two commercial checks.

How does automated monitoring keep a system compliant after launch?

The Act's post-market monitoring duty (Article 72) and the serious-incident reporting duty (Article 73) require a provider to know how the system behaves in use. ComplianceEngine attaches drift, performance and incident telemetry to the deployed model version, re-runs the assessment when the model or prompt changes, and records the result in the same technical file, so the file describes the system as it is running, not as it was released.

Does it integrate with our MLOps stack?

It runs as a stage in the pipeline you already have — GitHub Actions, GitLab CI or an equivalent — and reads model and dataset metadata from the repository and registry rather than replacing them. The Compliance Kit modules run offline in CI for developer teams, and their output is accepted by the platform as documented evidence. Where a connector does not exist for your stack we say so in the scoping call rather than during a pilot.

How much does it cost?

Explore is free for one AI system with no time limit. One-off packs are €290 (Article 50 Transparency Pack) and €490 (Single System File). Subscriptions are €290 per month for one system, €890 for three and €2,900 for fifteen; Enterprise adds internal and independent audit workflows, SSO and EU data residency with customer-managed keys and is priced on scope. Compliance Kit for developers is €79 per developer per month. EUR, excluding VAT, as published on 15 September 2026.

Where does the data live?

ComplianceEngine runs on EU-hosted infrastructure or inside your own cloud or on-premise environment; customer data does not leave the EU unless you deploy it elsewhere yourself.