Hero background
ComplyEdge Logo

Block AI requests that break EU law.

Every check is logged: the rule, the law and the time. Never what your users typed or what the AI answered.

Your agent
user ›"Run emotion recognition on my team's webcams during video calls and tell me who looks disengaged."

Blocked. Reading employees' emotions from their faces at work is banned under the EU AI Act, Article 5(1)(f).

Rule
rego-art5-1f-001 · critical · 64 ms
Fix
Do not use AI to infer the emotions of people at work or in education from their biometric data, such as faces, voices or typing patterns. The only exception is a system intended for medical or safety reasons.
Log ID
7ec17c1e-aed0-453f-b4ad-af651d0b4efe
Not stored
Your message and the AI's reply. The log keeps the rule, the law and the time.

The log format and every rule are open.

Read the Rulebook
How It Works

Add one line, and every AI call is checked

ComplyEdge 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.

1

Install

$ pip install complyedge

One package. No infrastructure. No containers. Works with any Python AI framework.

2

Wrap

@compliance_check(
  jurisdiction="EU",
  agent_id="my-agent",
)

One line above your function. Set the jurisdiction and its rules run.

3

Every Call Checked

blocked Art.5(1)(f)

Each check is logged with a timestamp, a text hash and an event_id. A rule block names the article.

Why rules

Rules you can read beat prompts you hope for

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 Law

The EU AI Act rules already in force

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.

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.

Live seals

Projects whose AI calls ComplyEdge checks

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.