Dike

Compliance for EU AI Act-regulated products demands evidence the auditor can verify, not just logs you claim are accurate. Dike sits as a proxy between your application and any OpenAI-compatible provider — OpenAI, Azure, Ollama, vLLM — intercepting every request. PII is redacted in-flight before storage, prompt injection attempts are blocked, responses flagged for human review are routed to an approval queue, and every event is written as a hash-chained, tamper-evident audit record. The vendor states the entire integration is a single base URL change; no SDK swap, no new dependencies.

The differentiating feature is the audit chain itself. Each record — prompt, retrieval, completion, human approval, incident — is sealed with a hash and chained to the previous record, so auditors can cryptographically confirm nothing was altered or deleted after the fact. For RAG pipelines specifically, Dike records which reference documents the model actually used to answer, satisfying the Article 12(2) requirement for retrieval evidence rather than just a chat transcript. Human oversight events — approvals, edits, overrides — are first-class log entries, exportable as the Article 14 answer instead of a narrative you have to write.

Dike fits EU-based teams that need compliance infrastructure fast and are comfortable with a hosted, cloud-only gateway. The fail-open design means audit storage failure never breaks production — requests pass through regardless. The constraint is that Dike is not self-hostable; teams with hard data-residency requirements beyond EU-region storage, or organizations that cannot route production traffic through a third-party proxy under their security policy, will need a different architecture. Similarly, teams needing custom compliance logic — branching rules based on user role, jurisdiction, or content classification — will find a passive proxy insufficient and end up building a layer on top.

Integration is a two-field change in any OpenAI-compatible SDK: set base_url to the Dike gateway endpoint and supply a Dike API key as the credential. The model parameter maps to your chosen downstream endpoint. Streaming is supported. The admin panel exposes trace browsing, audit log review, incident management, and evidence export — the outputs regulators will request under Articles 12, 14, 19, 26, and 73.