Why we built CompliAI
Article 4 of the EU AI Act is short — barely two paragraphs — and deceptively simple. It says: providers and deployers of AI shall take measures to ensure, to their best extent, a sufficient level of AI literacy of their staff and other persons dealing with the operation and use of AI systems on their behalf.
What counts as “sufficient”? The regulation doesn't say. Enforcement begins August 2, 2026. Every regulated org operating AI in the EU — and that's most orgs now — has to produce a defensible answer before then.
Who this is for
Fortune 500s hire EY. Scrappier SMBs stare at a 160-page regulation and hope. CompliAI is the middle option: structured training content, role-based assessments, and a risk register that together produce the artefact an auditor wants to see.
How we think about it
Compliance is a documentation problem masquerading as a training problem. We train your people because the regulation says we must. We generate the paperwork because that's what “compliance” actually means when the auditor arrives. Both, in one flow.
Part of the Kalpa ecosystem
CompliAI is built on the Kalpa platform — the same backend that powers Hearts & Harvest, LearnersZone, and PermitPilot. One login across the portfolio, unified billing, single source of truth for your organisation's data.