Automatic event logging, traceability and human-oversight metadata are emitted on every call — the artefacts the Act expects from a deployer of a high-risk AI system.
- Per-request event log
- Model & version provenance
- Operator identity captured
One API to access every LLM in Europe — with privacy, cost control, speed, reliability, and compliance proof built in.
Runs in your VPC or on your laptop. Full control of config, keys, and runtime — no SaaS lock-in.
Apache 2.0 codebase you can audit, modify, and white-label as your own internal product.
EU egress only by default. Any request leaving the region is blocked before bytes hit the wire.
Every request signed and hash-chained. Tamper-evident logs you can replay or export to your SIEM.
A working prototype of the control plane — engineers, DPO and finance see the same signed data, each from the angle they need.
Euronium Gateway moves the bytes. Euronium Protocol decides what is allowed to move. Euronium Dashboard turns the result into evidence anyone in the company can read.
An OpenAI-compatible endpoint that fronts every European provider and any model you self-host. One client, one base URL, one bill.
PII is masked before any token leaves your network. Non-EU destinations return 403, not a silent fallback. Every request emits an Ed25519-signed, hash-chained receipt.
Live observability for engineers, signed evidence for your DPO, virtual keys and budgets for finance — over the same ledger, with the same numbers.
Your client points at Euronium Gateway. Euronium Protocol decides what's allowed, redacts what shouldn't leave, and signs what does. Euronium Dashboard records it.
Names, emails, IBANs and national IDs are swapped for tokens in your own process. The model sees placeholders — your response is restored locally.
Every request is routed exclusively through EU-based providers. You choose the region — Frankfurt, Paris, Amsterdam — and the stack enforces it. No silent fallback to US servers.
Names, emails, IBANs and IDs are automatically replaced with tokens before the request leaves your network. The model never sees the real values, and responses are restored locally.
GDPR, EU AI Act, Schrems II and DORA controls are built into every call. You get the evidence trail regulators expect, without building it yourself.
Every call produces a signed, tamper-evident receipt. Your auditor can inspect the full chain from prompt to response, including which provider handled it and where.
No. Swap one line — your base URL — and every existing client, agent and notebook routes through Euronium. Same SDK, same models, new jurisdiction.
You stay in control. Failover to alternative EU providers happens automatically. Your logs, your data, your evidence trail remain intact — no vendor lock-in.
Every team in Europe rebuilds the same compromise. You wire your product to a US model because it's the fastest path to a demo. Then legal asks where the data went, finance asks why a single PoC cost €4k, and your DPO asks for a log no provider can give them. Euronium is the layer that answers all three questions before they're asked — without making your engineers learn a new SDK or your CFO sign a new vendor.
OpenRouter, Portkey and LiteLLM solved provider routing. Euronium adds the sovereignty, masking and proof European teams actually have to ship.
| Capability | Euronium | OpenRouter | Portkey | LiteLLM |
|---|---|---|---|---|
| EU-only egress (enforced, not promised) | ||||
| PII masked before request leaves your network | ||||
| Signed, hash-chained audit receipts | ||||
| GDPR · EU AI Act · DORA controls mapped | ||||
| Open source (Apache-2.0, self-hostable) | ||||
| OpenAI wire-compatible (one base_url) | ||||
| Hosted & operated in the EU | ||||
| Zero markup on provider tokens |
Want the full breakdown — including Helicone, Langfuse, AWS Bedrock, Azure OpenAI and Cloudflare AI Gateway?
See full comparisonEuronium Gateway speaks the OpenAI wire protocol. Swap yourbase_urland every existing client, agent and notebook starts routing through Europe — with redaction, signed receipts and per-team budgets, no rewrite required.
# any OpenAI-compatible client works — point it at Euronium
from openai import OpenAI
client = OpenAI(
base_url="https://gateway.euronium.eu/v1", # ← the one line
api_key="eur_live_…",
)
resp = client.chat.completions.create(
model="mistral-large",
messages=[{"role": "user", "content": "Summarise this invoice."}],
)the dev tier runs locally — no calls leave your machine
base_url change. Every framework keeps working.Don't see yours? If it speaks OpenAI, it speaks Euronium — no SDK fork required.
Stop maintaining your own retry, fallback, rate-limit and audit code. Euronium Gateway gives you a single endpoint with the features you'd otherwise build over six quarters.
Euronium Protocol turns vague AI policies into deterministic behaviour. The Dashboard turns that behaviour into evidence — formatted the way your DPO and auditor expect it.
The Protocol resolves destinations against an allowlist of European regions. Anything else returns 403 with the rule that blocked it.
Names, emails, IBANs, national IDs and free-text personal data are masked before the request leaves your network and restored in your own process.
Ed25519 receipts chain every request to the previous one. Tampering with a single row breaks the chain — and the Dashboard tells you which one.
The Gateway, the Protocol and the Dashboard are open source. Read the wire format, audit the redactor, fork the whole thing if you have to.
Adopting the Euronium stack moves a long list of AI-specific controls from something we should build to something the platform already does. Here is what your auditor, DPO and CISO get for free.
Automatic event logging, traceability and human-oversight metadata are emitted on every call — the artefacts the Act expects from a deployer of a high-risk AI system.
PII is masked before the request leaves your network. Receipts give you the lawful-basis trail, retention windows, and the DPIA evidence regulators ask for.
Non-EU egress returns 403 with the rule that blocked it — no silent fallback to a US region. Transfer impact assessments come pre-filled per provider.
Every model provider is registered as an ICT third-party with the contractual clauses, exit plan and concentration-risk view your financial-services auditors need.
Access, logging, cryptography and supplier controls are mapped to the relevant Annex A items, so your ISMS picks up Euronium as an existing control — not a new gap.
Tamper-evident receipts and per-tenant logs give your SOC 2 auditor the population and sample evidence for CC6, CC7 and CC8 without building a new pipeline.
Supply-chain visibility, incident telemetry and cryptographic integrity are surfaced in formats your CISO can drop into the required risk-management reporting.
Your prompts, outputs and receipts are yours — exportable as signed JSONL at any time, with no provider-specific lock-in on the evidence trail.
Euronium is a control layer, not a legal opinion. Your DPO still signs.
Token costs pass through at provider rates. We charge for support, hosting and the parts of compliance you don't want to operate yourself.
Full Euronium stack on your laptop. Local model, signed receipts, no account required.
Run the Gateway in your own VPC. We provide upgrades, audited releases and incident response.
Install Euronium in two minutes. Keep your SDK, change one line, and start collecting the evidence your auditor, your customers and your future self will ask for.