Entity, licensing and data processing
Everything a security review or procurement assessment needs, in one place, stated as facts rather than reassurances. If something you need is missing, ask in a briefing and we will add it here rather than answering it once by email.
From a Wäg deployment: nothing
Not a minimal amount. None. There is no telemetry channel, no online licence check, no usage counter, no crash reporting, and no analytics in the gateway or the console. The licence is verified offline. This is not a setting you turn off — there is no mechanism, and you can confirm that by watching your own egress.
Not as a configuration option — as a property of the software. Check it at your own network layer.
- No prompts
- No completions
- No provider keys
- No logs
- No telemetry
- No online licence check
- No usage analytics
No outbound connection is required for the gateway to operate: offline price book, local policy engines, in-process semantic cache. Deployable with no internet egress at all.
Who you would be contracting with
| Legal entity | Bitkaio Ltd |
|---|---|
| Jurisdiction | Registered in the United Kingdom. European, outside the European Union. |
| Role | Copyright holder and maintainer of Wäg. Not a processor of your AI traffic — see above. |
| Contact | info@waeg.ai |
We state the UK/EU distinction explicitly rather than describing ourselves as simply "European", because sovereignty assessments should be made on facts. Where a framework assesses the supplier's ownership and control, we are a non-EU supplier and do not claim otherwise.
The specifics, including the counter-arguments
Vague claims lose this argument; specific ones win it. Here is our actual position, including the two objections most likely to be raised against us.
| Topic | Position |
|---|---|
| FISA 702 / EO 12333 | Not applicable. Section 702 reaches US electronic communication service providers, permitting collection of non-US persons' communications without individualised warrants, notice, or meaningful redress. It is the authority the Court of Justice identified in Schrems II when invalidating Privacy Shield. Bitkaio Ltd is outside its scope. |
| US export-control directives | Not applicable. In June 2026 a US Commerce directive required a US model provider to suspend access for all foreign nationals worldwide. A UK-incorporated company cannot be issued that order. |
| EEA → UK transfers | Covered by adequacy. The European Commission renewed the UK's GDPR and LED adequacy decisions on 19 December 2025 for six years, to 27 December 2031, following its assessment of the Data (Use and Access) Act 2025. No supplementary transfer mechanism is required. |
| UK–US Data Access Agreement | Exists, and we would rather address it than have you find it. It is a law-enforcement channel restricted to serious crime, limited to targeted non-bulk orders, subject to independent authorisation, reciprocal, and it prohibits US orders from targeting persons located in the UK. It is not equivalent to a US provider's direct compellability. It also has no bearing on a Wäg deployment: there is no data in our hands to order us to produce. |
| UK Investigatory Powers Act | The UK has domestic investigatory powers, and this is the objection most often raised against a UK supplier. The answer is architectural: a notice served on Bitkaio cannot reach prompts, completions, keys or logs that never leave your perimeter, because no mechanism delivers them to us. |
| Where we are a third country | Where a sovereignty framework assesses the supplier's ownership, control and personnel — for example the EU ownership criterion in the proposed Cloud and AI Development Act — we are a non-EU supplier. Where it assesses the deployment, the answer is your organization, because you operate it. |
The full sovereignty argument, including how CADA levels map
How the licence works
- The core is Apache-2.0: routing, HA, failover, caching, hierarchical budgets, the policy chain, the MCP gateway, jobs, realtime, multi-tenancy, residency, the evidence ledger, the console and observability.
- Enterprise modules are compile- and licence-gated, and the gate is always on. An evaluation licence is free and issued as a key, so every entitlement is testable before any commercial conversation.
- Enterprise is licensed per deployment environment, not per token, per seat or per request. Growing your AI traffic does not create a commercial event.
- There is no contributor licence agreement surprise, no planned relicensing, and no BSL or SSPL conversion planned.
The licence is a signed token verified offline: no licence server, no phone-home. We have no channel to reach a deployment. An expired, revoked or missing licence switches the Enterprise modules off — an expired one after its grace period — and the open-source gateway keeps running.
The website and the product are different things
This website collects minimal, privacy-preserving usage statistics. The Wäg gateway is self-hosted software running in your infrastructure and processes none of your data on our behalf. Nothing in our privacy policy applies to data processed by your own deployment — we have no access to it.
What Wäg supports, and what Bitkaio holds
Wäg supports
- OIDC single sign-on and SCIM 2.0 provisioning
- Customer-managed key material with AES-256-GCM envelope encryption, and a FIPS posture flag (not a FIPS-validated binary)
- Secrets resolution from HashiCorp Vault, Azure Key Vault, AWS Secrets Manager, GCP Secret Manager
- OpenTelemetry and Prometheus, with long-retention audit packs
- Air-gapped operation with no required network egress
- A signed, hash-chained evidence ledger of every provider call, verifiable offline against a pinned Ed25519 key
- A read-only auditor role and signed agent evidence packs mapped to AI Act and DORA provisions (Enterprise)
Bitkaio currently holds
We hold no third-party security certifications, and we will not imply otherwise — a procurement reader who finds one overstated certification claim is right to re-read everything else with suspicion. What exists instead is verifiable rather than attested:
- Properties you can check on the running software — no outbound connection to us, an offline licence — rather than a report you have to take on trust
- Every image signed keyless with cosign, an SBOM per release, and SLSA provenance where the release notes list it
- A deployment model where you are the operator, so most controls are yours to evidence
Documents for a security review
The set most reviews ask for, linked rather than requested. Naming this explicitly saves several email round-trips per assessment, which is the main thing a trust centre is for.
One endpoint. Every model. Complete control.
Run it in your own infrastructure
Everything you need to run a control plane in production is Apache-2.0 and stays that way — routing, HA, caching, failover, budgets, policy, MCP, jobs and observability. Self-hosted, no account, no phone-home.
$ docker run -p 4000:4000 <registry>/waeg-gateway:<version>Not a working pull: the images are not public yet. Design partners receive the registry details privately.
Deploy in 5 minutesShape it as a design partner
Wäg is not publicly released yet. We are working with a small cohort of teams running multi-provider AI in production, and serious about governance and sovereignty, to harden the control plane on real workloads.
- Every Enterprise capability included, at no licence cost
- Hands-on migration — we do it with you, including from LiteLLM
- A direct line to the engineers building it, and real influence on what ships next