What Compliade does that adjacent tools do not
Same “AI agents” problem — different jobs. Compliade owns register → gate → prove.
| Compliade | Privacy GRC | Ops / alerts | Runtime / egress | |
|---|---|---|---|---|
| Gate at ingest | Blocks (deny / HITL / suspend) | Workflows on declared systems | Alert after the run | Network / egress intercept |
| Primary UX | Approvals as home + register | Treatment / FRIA forms | KPIs, judges, alert center | Traffic / security console |
| DPO artifact | Art. 30 + AIPD + hash (primary) | Strong RoPA / FRIA | Scores / tokens (rarely Art. 30) | Security trail |
| Granularity | Each agent action | Systems / treatments | Pipeline + post-run scores | Network / MCP events |
| Hosting | OVH + Scaleway (France) | Often EU | FR / EU | FI / EU (e.g.) |
Category examples: privacy GRC (e.g. Dastra), ops / alerts (e.g. NIAOne), runtime / egress (e.g. Roder). Mid-market often only needs Compliade for agents; large orgs may combine tools.