Every check is logged: the rule, the law and the time. Never what your users typed or what the AI answered.
Blocked. Reading employees' emotions from their faces at work is banned under the EU AI Act, Article 5(1)(f).
The log format and every rule are open.
Read the RulebookComplyEdge sits between your app and the AI model. It checks every prompt and answer against rules for prompt injection everywhere, the EU AI Act, personal data and keys for users in the EU, and US rules for users in the US.
One package. No infrastructure. No containers. Works with any Python AI framework.
One line above your function. Set the jurisdiction and its rules run.
Each check is logged with a timestamp, a text hash and an event_id. A rule block names the article.
An instruction is not a control. A system prompt can be ignored; a rule in the request path runs on every call. A phrase-rule block records the article citation (e.g. 5(1)(f)), rule ID, timestamp, text hash and event_id.
Above the stack
GRC platforms inventory your AI systems and gather evidence. ComplyEdge does not replace them.
In the request path
ComplyEdge sits between your app and the AI model. It checks every prompt and answer, and logs each check.
An inventory says the system exists. A check in the request path is the evidence for each call.
| The question | ComplyEdge | Model-based guardrails | Manual audit |
|---|---|---|---|
| DPO Is the prompt stored? | No. A keyed hash of the text, never the text. | Varies by vendor | Samples are read by people |
| DPO Where does the record live? | EU (Frankfurt) or US, picked at sign-up. | Varies by vendor | Wherever the report is kept |
| Compliance Which law did it apply? | A rule block names the rule, the article and the paragraph. | Only if the model writes one | Yes, in the report |
| Auditor Same input, same answer? | A rule block, yes. The paid injection check is a model decision. | A model judges each call | Reviewer judgement |
| Engineering What does it add to each call? | ~64ms engine p50 (opa_latency_ms). On a paid plan, the injection check after a clean pass can add a model call. |
A model call per check | Nothing; it runs after the fact |
| Engineering Can we read the code? | SDKs, CLI, MCP server and rule set (Apache 2.0) | Varies by vendor | Not applicable |
The EU AI Act applies to any company whose AI is used in the EU. These three parts already apply, fines included, and ComplyEdge has rules for all three. Each card links to the article.
Prohibited Practices
IN FORCE SINCE FEB 2025
No grace period. Violations have been illegal for over a year.
↗General-Purpose AI
FINES IN EFFECT
GPAI obligations in force since Aug 2025. Fines have applied since August 2026. No postponement.
↗Transparency
IN FORCE SINCE Aug 2026
Transparency is enforceable. Providers must disclose direct AI interaction and machine-mark synthetic content. Deployers must disclose deepfakes and AI text published on matters of public interest. Systems already on the market before 2 August 2026 must machine-mark from 2 December 2026.
Fines: up to €35M or 7% of worldwide turnover
Art. 5 · Art. 99(3) · €15M / 3% for operator & transparency duties (Art. 99(4)) · GPAI providers €15M / 3% (Art. 101) · Art. 99 & Art. 101 (opens in a new tab)
Using high-risk AI for hiring, credit or insurance pricing? The deployer duties of Article 26 apply from 2 December 2027. What ComplyEdge records for Article 26.
Every project below is a ComplyEdge tenant that chose to show its seal here. Each seal is drawn from its own audit data, the real /v1/check calls it runs, so it changes when their enforcement does. Today all of them are our own projects, run on ComplyEdge like any other tenant. Open one to see its public trust page.
Free covers open source and rate-limited hosted checks. Pay for volume (Developer) or the verifiable evidence pack (Enterprise). Monthly list prices in US dollars (USD) below.
$0
Open source + hosted free
$99/mo
More volume, plus US rules
$999/mo
Listed price, billed by invoice