European Union

Runtime authority for EU sovereign AI.

When an EU regulator asks — under Article 9, 10, 14 or 15 of the AI Act, under DORA's third-party-risk regime, under GDPR Art. 22 automated-decision review, or under EDPB transfer-impact guidance — KYE Protocol™ answers from a record sealed at the moment of action. Customer-held keys, EU-region data residency, offline-verifiable from the publisher's JWKS.

KYE Protocol™ for the EU, step by step

Demo data

You learn: What happens at each step. You can: Step through it.

  1. Step 1 of 5

    KYE Protocol™

    Data residency

    deploy to EU-region Cloudflare resources (D1 + R2 + KV pinned to EU); per-tenant configurable.

  2. Step 2 of 5

    KYE Protocol™

    Customer KMS

    signing keys live in the customer's HSM or sovereign-cloud KMS; KYE™ never has access to the private key material.

  3. Step 3 of 5

    KYE Protocol™

    Open verifier

    any DPA, third-party auditor, or supervisory authority can replay an Evidence Pack™ using only the publisher's JWKS. No vendor dependency in the audit path.

  4. Step 4 of 5

    KYE Protocol™

    GDPR alignment

    PII referenced by URN, not embedded; right-to-erasure is a first-class lifecycle state; transfer-impact assessment is supported by signed routing records.

  5. Step 5 of 5

    KYE Protocol™

    Apache 2.0 schemas + vocabulary

    the contracts the customer relies on are open. The patent-track runtime construction is paid; the proof formats are not.

How this widget is built
Demonstrates
KYE Protocol™
Components
  • The steps this page describes
Flow
Each step in order, as the page sets it out. Architecture diagram
Used on

EU-sovereign deployment

EU data, EU keys, EU control.

  • Data residency — deploy to EU-region Cloudflare resources (D1 + R2 + KV pinned to EU); per-tenant configurable.
  • Customer KMS — signing keys live in the customer's HSM or sovereign-cloud KMS; KYE™ never has access to the private key material.
  • Open verifier — any DPA, third-party auditor, or supervisory authority can replay an Evidence Pack™ using only the publisher's JWKS. No vendor dependency in the audit path.
  • GDPR alignment — PII referenced by URN, not embedded; right-to-erasure is a first-class lifecycle state; transfer-impact assessment is supported by signed routing records.
  • Apache 2.0 schemas + vocabulary — the contracts the customer relies on are open. The patent-track runtime construction is paid; the proof formats are not.

EU pilot

Start in shadow mode. Evidence first, enforcement later.

EU pilots run in shadow mode — KYE™ observes the delegated-action chain and produces signed Evidence Packs™ without blocking production. After the pre-agreed evaluation window, the customer promotes specific Guards from shadow to enforce, one at a time, with first-class rollback.

Independent — no government affiliation. KYE Protocol™ is an independent protocol and is not affiliated with, endorsed by, or part of any government, regulator, or official “Sovereign AI” programme. References to regulators and frameworks describe the requirements KYE™ helps you evidence — not any official relationship.

Canonical KYE™ surfaces referenced on this page: Evidence Pack™ · KYE Protocol™.