Gateway vendors

Not in the preview yet. This feature is built in the repository but is off in the v2.2.6 preview (test mode). Do not treat this page as available on a preview core. See ../preview.md and the release notes.

Status: Live with mock upstreams.

A gateway plugin checks a Dynamo allowance credential on every request, in process, against pinned keys, with no network call in the request path. Metering happens afterwards. An absent, unverifiable, exhausted or revoked credential is refused with a 402.

One vector set for every gateway

Every gateway passes the identical shared vector set: the denial classes, their order and the 402 challenge schema never differ between gateways. If a gateway's architecture forces a difference, that is raised as an open question, never adapted silently.

The shared vectors (@dynamo/conformance-vectors 1.5.0) cover:

signer, metering stopped, not yet synced, stale, revoked, stopped by Dynamo, exhausted);

only canonical base64url: the URL-safe alphabet only, no padding, and each segment re-encoding to itself;

Gateways built today

GatewayHow Dynamo runs on it
Kong, APISIXa plugin with a shared core
Kong AI Gatewaythe Kong plugin, unchanged
Envoy, agentgatewayan external-processing adapter (@dynamoprotocol/gateway-envoy 0.4.0)
Bifrostthe official image with a provider pointed at the Dynamo guard, or a native plugin built with Bifrost from source

A native Bifrost plugin that fails to load leaves Bifrost serving with no check; confirm that an unauthenticated request answers 402 before taking traffic.

Test suites

The container suites need Docker.

Mocks today

Mock upstreams and pinned public images. No vendor account is needed.

Certification steps

  1. Every shared vector passes, byte for byte, including all 12 canonical

credential cases.

  1. The meter journal reconciles exactly with Dynamo's records.
  2. No network call sits in the request path.
  3. The gateway refuses (402) when the check cannot run.