Frequently Asked Questions (FAQs)

General Overview

1. What is CompliAI?

CompliAI is a centralized EU AI Act compliance platform that helps organizations manage AI governance, risk classification, technical documentation, conformity workflows, and post market monitoring in a structured and auditable way. It serves as a single source of truth for AI compliance across the organization. 

2. Who is CompliAI designed for? 

CompliAI supports all roles defined under the EU AI Act, including AI Providers, Deployers, Distributors, and Importers. 

Workflows, requirements, and outputs adapt based on the organization’s role in the AI value chain. 

3. How does CompliAI help with EU AI Act compliance? 

CompliAI translates EU AI Act requirements into practical workflows covering AI system inventory, guided risk classification, technical documentation (including Annex IV), conformity assessment support, the EU Declaration of Conformity, and post-deployment monitoring. 

4. Is CompliAI a legal authority or regulator? 

No. CompliAI is a compliance enablement tool. The customer remains fully responsible for compliance decisions, accuracy of inputs, and regulatory submissions. 

5. Has CompliAI been approved by the EU or regulators? 

No compliance platform is formally approved or endorsed by regulators. CompliAI helps organizations operationalize and document compliance, while regulatory responsibility remains with the customer.

Legal Scope & Responsibility

6. Who is legally responsible for EU AI Act compliance? 

The customer is always legally responsible. CompliAI provides tooling, structure, and automation but does not assume regulatory responsibility. 

7. Does CompliAI itself fall under the EU AI Act? 

Yes. CompliAI includes AI functionality and falls within the scope of the EU AI Act. It has been internally assessed and classified as not high-risk. Registration and conformity obligations therefore apply to customer AI systems, not to CompliAI itself. 

8. Are documents generated by CompliAI legally valid? 

Documents generated by CompliAI can be used as part of the EU AI Act compliance file. Their legal validity depends on the accuracy of inputs, completeness of evidence, and formal approval by the organization. 

Risk Classification & Questionnaires

9. Is risk classification fully automated? 

No. Risk classification is human-in-the-loop. CompliAI guides users through structured questionnaires aligned with EU AI Act logic, while final confirmation remains with the organization. 

10. Is the risk assessment just a checklist? 

No. The questionnaire captures the intended purpose, deployment context, exclusions, and legal criteria required to justify the correct EU AI Act risk category. 

11. How does CompliAI reduce the risk of misclassification? 

Through structured legal logic, mandatory justification fields, embedded definitions and legal references, and review workflows that support consistent and well-documented decisions.

12. Can multiple stakeholders review or approve classifications? 

Yes. CompliAI supports collaborative review and approval workflows. At this stage, multiple users can review information and decisions, while editing and final confirmation are controlled through defined roles. 

13. Can an AI system change its risk category over time? 

Yes. If relevant changes occur, CompliAI flags them and supports reassessment. Risk categories are not automatically reclassified without human review. 

14. What happens if a system becomes prohibited? 

CompliAI flags the issue and escalates it through monitoring and notifications. Regulatory obligations may require prohibited systems to be removed from the market. CompliAI supports visibility, documentation, and governance actions, but does not enforce removal. 

AI System Lifecycle & Versioning

15. Can I start compliance work while an AI system is still in Draft? 

Yes. AI systems can remain in Draft while information is being collected and refined. Certain steps, such as final documentation and conformity actions, require the system to move out of Draft once information is complete. 

16. Can I add users or reviewers before the system is finalized? 

Yes. Users can be granted access to review available information during preparation. Final approvals and confirmations occur once the system progresses to later compliance stages. 

17. What happens if a new version of an AI system is released? 

A new version requires reassessment and documentation updates. Whether the full compliance process must be repeated depends on the materiality of the changes.

18. Do compliance processes need to restart after changes? 

Not always. CompliAI detects and classifies changes by severity and provides visibility so organizations can determine whether reassessment or re-certification is required. 

Repositories, Code & Monitoring

19. Does CompliAI analyze source code? 

No. CompliAI does not analyze source code line-by-line or inspect model internals. It focuses on compliance-relevant signals, metadata, and documented changes. 

20. What happens if a private repository is connected? 

Access is fully controlled by the customer. CompliAI analyzes only permitted information within the defined compliance scope. 

21. Can compliance checks run on one branch while development continues on others? 

Yes. Customers can scope monitoring and compliance checks to selected branches. 

22. How does monitoring work? 

Monitoring events are generated when relevant changes are detected in the connected repositories. Events are logged and classified by severity to support post-market monitoring obligations. 

23. Is monitoring continuous? 

Yes. Monitoring remains active for as long as repositories are connected and monitoring is enabled. 

Documentation & Conformity

24. How is Annex IV technical documentation generated?

Annex IV documentation is generated from structured inputs collected throughout the workflow, including questionnaires, uploaded documents, and repository signals. AI suggests a draft, which is always subject to human review and approval. 

25. Can users edit AI-generated documentation? 

Yes. All AI-generated content can be reviewed, edited, and finalized by users. 

26. How is documentation traceability ensured? 

Through structured fields, linked evidence, versioning, and audit-trail concepts that track changes over time. 

27. Does CompliAI support internal and external conformity assessments? 

Yes. Internal conformity is supported through QMS and post-market monitoring documentation, while external conformity includes uploading and managing certificates issued by Notified Bodies. 

28. How is the EU Declaration of Conformity generated? 

The EU Declaration of Conformity is generated as the final step of the compliance workflow, using structured inputs collected throughout the process, and requires human approval before finalization. 

29. Does CompliAI issue the CE mark? 

No. CompliAI does not issue the CE mark. It reflects CE marking once all regulatory requirements are fulfilled by the organization. 

GDPR & Data Protection

30. Does CompliAI process personal data? 

By design, CompliAI focuses on system-level metadata and documentation, not operational personal data. Any personal data entered by users is customer-controlled.

31. Does CompliAI replace GDPR compliance tools? 

No. CompliAI complements GDPR tooling by covering EU AI Act–specific obligations. Deployment & Operations 

32. Can CompliAI be deployed on-premise or in a private cloud? 

Yes. Both on-premise and private cloud deployments are supported, depending on the customer requirements. 

33. How long does it take to get started with CompliAI? 

Pilot or initial production deployments can typically be live within 30 days, depending on deployment model and scope.