Compliade
Stop the risky action. Seal Art. 30 / AIPD proof. Hosted in France.
The action waits — it has not applied
crm.write_contact
Support agent · sandbox
Amber — approval required
docs.export_pack
Compliance agent · sandbox
Not applied
crm.bulk_update
Ops agent · staging
Pending · DPO / CISO
HITL gate at ingest: require_approval holds the action until a human decides (Art. 14).
Register → Gate → Prove
One loop: inventory, control that blocks, fileable proof.
Without a gate, you only have logs after the fact
A PDF register or a post-run alert does not stop the action. Compliade is the OS where the agent is governed — not a checklist or an alert center.
Agents, purposes, legal bases, skills — Art. 30 system of record.
Deny, require_approval, suspend — before the agent applies.
Hash chain + Art. 30 / AIPD exports for CNIL, board, or auditor.
The same inventory feeds the register, AIPD, and integrity chain — one pack, not four tools.
Compliance pack
Data OVHcloud (GRA / Roubaix) · Compute Scaleway fr-par · Multi-tenant RLS
SecNumCloud is roadmap, not an MVP promise.
What Compliade stops, proves, and hosts — short answers.