Wäg OSS is the product
Everything required to run a control plane in production is Apache-2.0, and stays that way. Not a trial, not a community edition with production features removed, and not a funnel into a paid tier that unlocks the parts you actually need.
What stays free, forever
- Multi-provider routing, failover, retries, circuit breakers
- Multi-node HA with shared budgets and rate limits
- Intelligent, cost, latency and weighted routing
- Four-tier semantic cache with safety gates
- Virtual keys, hierarchical token and spend budgets, rate limits
- Guardrail chain with pluggable engines
- MCP gateway, A2A gateway, jobs and realtime
- Agent identity, run limits, tool policies and approvals
- Managed egress and the egress proxy
- Evidence ledger, data residency and regional data planes
- Wäg Edge device sign-in and reporting of local model use
- Secrets connectors, OpenFGA multi-tenancy, admin console
- OTEL and Prometheus observability · air-gap · no phone-home
We would rather you standardize on the open source and buy support than evaluate a deliberately limited version. A gateway that strips HA or routing to sell them back is not something you can bet a platform on — and betting a platform on this is exactly what we are asking you to do.
Identity, evidence and the controls large estates add
Enterprise is how large organizations connect Wäg to their identity provider, hand their auditors evidence packs, govern agent payments, devices and inspected outbound traffic, and get support from a supplier. The gateway's production path stays Apache-2.0.
Enterprise modules are compile- and licence-gated, and since 1.0 the gate is always on: there is no preview mode and no switch that turns the check off. Evaluating them still costs nothing, because an evaluation licence is a signed key we issue free of charge. What has not changed is that the gateway never contacts us to verify it, so there is no channel through which we could switch a running deployment off.
Apache-2.0, with no asterisk
- Apache-2.0: use it commercially, modify it, redistribute it, run it forever, fork it if we disappoint you.
- No planned relicensing. No BSL or SSPL conversion planned — we are stating that explicitly because after several years of high-profile infrastructure relicensings, it is a fair question to ask.
- No contributor licence agreement surprise: Bitkaio Ltd holds copyright on its own contributions and does not require assignment of yours to use the project.
- No licence server and no phone-home, so nothing about your deployment depends on a commercial relationship continuing.
Check what you can
Much of this page can be checked from the running software. Images are signed keyless with cosign and recorded in a public transparency log, with provenance and SBOM attestations where the release notes list them. The gateway makes no connection you did not configure, and the licence verifies offline. If you find a gap between what we say here and what the software does, that is a bug and we want to hear about it.
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