One set of rules and one record for every gateway cluster you run
A separate gateway for each cluster, team or kind of traffic means separate rules, roles and records. G8 manages all the gateway clusters you run, for API and AI traffic, with one set of roles and one audit record.
More gateways, more places to look
Gateways tend to multiply: one for each cluster, one for each team and now one more for AI traffic.
A console for each cluster
Each gateway cluster is managed on its own, so the same change is made by hand in several places.
With G8Each cluster is an Environment in one G8 console. Copy a Route from one to another and see what changes first.
AI traffic on a separate product
Traffic to language models often goes through a tool with its own rules and its own records.
With G8Routes to models and MCP Routes sit beside your API Routes, with the same Plugins.
Roles and records in several places
Who may change what, and who did, is kept in each tool separately.
With G8One set of roles, granted per Environment, and one audit record for every change.
One console for every gateway cluster
G8 manages the G8 engine clusters you run. API Gateway, AI Gateway and API Security share the console, the roles and the audit log.
Every cluster as an Environment
An Environment is a gateway cluster, such as Development, Staging or Production. Add a cluster you already run: adding or removing an Environment doesn’t touch the G8 engine.
- Test before you saveIf the connection test fails, it names the problem, such as a wrong key, a wrong address or a certificate problem.
- Gateway nodesSee which nodes of each cluster receive traffic and which can’t be reached.
One set of roles for every area
Built-in and custom roles apply per Environment, to API and AI traffic alike. Map Microsoft Active Directory groups to roles, and give automation its own service accounts.
- Separate by EnvironmentA role granted for Staging gives no access to Production.
AI traffic on the same Routes
Send traffic to language models through Routes with the same identity, limits and request records as your APIs. Serve APIs to AI agents with OpenAPI to MCP on a Route of its own.
- One Plugin catalogAI Plugins sit in the same catalog as every other Plugin, with the Routes that use each.
Clusters set up by different teams
A typical setup, drawn to show how the parts fit together. It doesn’t describe a specific customer.
A company runs gateway clusters in more than one data center, each set up by a different team, and has started to send traffic to language models through a separate tool.
Each existing cluster is added to G8 as an Environment, without changes to the G8 engine.
Directory groups are mapped to roles for each Environment.
Traffic to language models moves onto Routes with ai-proxy-multi, under the same roles and audit record.