Aforo supports five enterprise API gateways via native plugin mechanisms. Zero application code changes. Drop-in metering across your entire gateway estate.
Aforo ships production-grade integrations for all five major enterprise API gateways. Each integration uses the gateway's native extension mechanism — no sidecars, no service mesh changes, no infrastructure modifications. The plugin installs in minutes and metering begins immediately.
Every gateway integration follows the same two-phase architecture: a synchronous entitlement check in the request path, and an asynchronous metering event in the response path. The gateway's native extension mechanism is the execution container — Aforo provides the logic.
All five plugins share the same ingest protocol: a compressed HTTPS POST to ingest.aforo.ai/v1/ingest with an idempotency key derived from the request correlation ID. Events are deduplicated server-side — safe to retry on failure.
Most teams run a single gateway. Pick the guide that matches your stack and follow the step-by-step setup. If you run multiple gateways — common in enterprise organizations that have run through acquisitions or multi-cloud mandates — see the Multi-Gateway section below.
PRO TIP
Not sure which gateway you have? Check your team's infrastructure-as-code repo for kong.yml, apigee, or CloudFormation / Terraform references. Aforo Support can also review your architecture diagram and recommend the right integration path.
Product Discovery✓ auto✓ via API✓ via API✓ via API✓ via API
Monetized Tagging✓ service tags✓ attributes✓ tags✓ tags✓ tags
Gateway Restore✓ full✓ full✓ full✓ full✓ full
Config Capture✓ routes+plugins✓ product detail✓ resource tree✓ API + ops✓ asset meta
INFO
All capabilities ship enabled by default. Individual capabilities can be disabled per-integration via the Aforo Admin Panel under Integrations → select gateway → Feature Flags. This is useful when incrementally rolling out metering across a large existing estate.
Enterprise organizations often run multiple gateways simultaneously — a legacy Apigee estate alongside new Kong clusters, or AWS API Gateway for serverless workloads beside Azure APIM for enterprise B2B APIs. Aforo is designed for this.
multi-gateway-topology.txt
Tenant A subscription
├── Kong (Kubernetes cluster) ──────► Aforo Ingest ──► Single billing record
│ └── aforo-metering plugin ▲
├── AWS API Gateway (serverless) ──► Lambda ─────┘
│ └── CloudWatch Logs subscription ▲
└── Azure APIM (enterprise B2B) ─► Policy ───────┘
└── Outbound policy fragment
All three gateways write to the SAME tenant billing context.
Aforo deduplicates, rates, and routes to a single invoice.
Multi-Gateway Setup Steps
1
Create an integration per gateway
In Aforo Admin Panel → Integrations, add each gateway as a separate integration entry. Each gets its own API key and ingest routing config.
2
Deploy the plugin to each gateway
Follow the individual gateway guides. Each plugin is independent — deploy and verify one at a time.
3
Map products across gateways
Use the Product Catalog to link the same Aforo Product to multiple gateway integrations. Usage from all gateways accrues to the same product meter.
4
Verify unified billing
After all gateways are live, use the Event Log to confirm events from each gateway are arriving under the same tenant context. Run a test bill cycle.
WARNING
When running multiple gateways, ensure all plugins use the same tenant header name (X-Tenant-Id) and that your API clients send it consistently. Aforo uses this header to correlate usage across gateways into a single billing record. Mismatched headers cause split billing contexts.