Multi-Gateway

Apiway is gateway-agnostic. You define your APIs once; Apiway deploys them to any supported gateway. Your governance, security, and metering rules follow — regardless of which gateway serves the traffic.

Supported Gateways

Gateway	Worker	Status
Alpha Gateway	alpha-worker	Full feature support
Kong	kong-worker	Supported
Azure API Management	azure-worker	Supported
Apigee	apigee-worker	Supported
Tyk	tyk-worker	Supported
Zuplo	zuplo-worker	Supported

How It Works

Apiway’s deployment model is abstract — it describes what should happen (routing, security, rate limits), not how a specific gateway implements it. Workers are the translators:

Apiway Deployment Model → Worker → Gateway-native configuration

Each worker knows how to translate Apiway’s model into the native format of its target gateway — proxy and policy docs for Alpha, routes and plugins for Kong, APIs and policies for Azure APIM, proxies for Apigee.

Mixed Gateway Environments

You can run different gateways in different environments:

Environment	Gateway	Reason
Development	Alpha Gateway	Fast iteration, full feature support
Staging	Kong	Match production gateway
Production	Kong	Battle-tested, existing infrastructure

Or run the same gateway everywhere — it’s your choice. Apiway’s governance and metering work identically across all gateways.

Alpha Gateway Exclusive Features

Some advanced features are exclusive to Alpha Gateway:

Feature	Alpha	Others
RU metering	Yes	No
Consumption cost guard	Yes	No
Dependency enforcement	Yes	No
MCP server	Yes	No
Operational risk tracking	Yes	No
Blue-green revisions	Yes	Varies

Note

These features require deep gateway integration that Alpha Gateway provides natively. Other gateways support core functionality (routing, auth, rate limiting) through their native capabilities.

Gateway Registration

Platform API

curl -X POST https://operations.api.apiway.net/v1/gateways \
  -H "Authorization: Bearer $TOKEN" \
  -d '{
    "name": "Production Kong",
    "type": "kong",
    "environment": "production",
    "credentials": { ... }
  }'

Management UI

Navigate to Operations > Gateways to register and configure gateway instances.

Migration

Moving from one gateway to another? Apiway makes it straightforward:

1. Register the new gateway instance
2. Deploy your APIs to the new gateway (in a staging environment first)
3. Validate behaviour
4. Switch production traffic

Your API definitions, governance history, subscriptions, and compliance scores remain unchanged — only the runtime gateway changes.