Wanda Gateway
Wanda works with the gateway you already have
Enforcement, bundled or bring your own. Keys, rate limits and quotas decided in about a millisecond, with no Wanda code running inside the gateway itself.
- Keys, limits and quotas
- Bundled or bring your own
- No gateway-resident code
What the decision path actually does
The four checks a call passes, and what it gets back when it fails one.
| The call | Result | What comes with it |
|---|---|---|
| Valid live key on a subscribed resource | 200 | with a signed context delivered upstream carrying tenant, consumer, plan, plan version, scopes, resource, method and a 60 second expiry |
| Unknown credential, or none at all | 401 | unknown_credential |
| GET on a resource the plan permits only for POST | 403 | method_not_allowed |
| A resource outside the plan | 403 | not_in_plan |
| Quota capped at 3 with 200 already used | 429 | quota_exceeded, with limit, remaining and reset on the response |
| The same call after the override is deleted | 200 | propagated with no restart |
| A test-mode key in the test environment | 200 | and its usage never reaches a statement |
How it is put together
The gateway you already run
Adapters for the gateways enterprises run in production, so bring-your-own is a supported shape rather than a promise.
Migration without a cutover weekend
Dual credentials let an old key and a new one run against the same traffic while an estate moves across.
No Wanda code inside the gateway
The gateway carries configuration only. Every enforcement decision is made in Wanda's own service behind a forward-auth boundary, which is why an upgrade on either side does not become a joint release.
Bring the one you already run
An estate with a gateway keeps it and adds Wanda behind it. The existing investment becomes a complement rather than something to rip out and re-procure.
Configuration written from the catalogue
Publish an API version and the platform renders the gateway configuration for you, deterministically, with a diff that answers what changes before it changes. A hand edit to the live file raises an alert rather than drifting quietly.
Bundled when there is nothing yet
A greenfield deployment gets a gateway wired by configuration, so there is one thing to install rather than two to integrate.
Identity fails closed
If Wanda cannot decide who is calling, the call is refused. That direction is not configurable.
Quota fails open, within a bound
If the counter store is unreachable, postpaid traffic is allowed within a per-plan bound rather than a customer's business stopping. Prepaid and hard-cap plans may declare the opposite.
Visible to your monitoring
Request counts by status are queryable from the gateway tier, enabled by configuration, still with no gateway-resident code.
Which gateway do you run?
That question decides the shape of the work, not whether the work is possible. A greenfield estate takes the bundled path and installs one thing. An estate with a gateway already in production keeps it, and Wanda sits behind it deciding and metering. Either way the commercial layer stops being a spreadsheet.
Four checks, in order
A call passes them in order. Failing any one returns its own status and its own reason, so a developer knows what to fix without opening a ticket.
Tell us what you already run.
The interesting question is not whether you need a new gateway. It is what it costs to meter and bill the one you have.