Run it yourself. Prove every change. Keep your data.
G8 installs in your own infrastructure, on OpenShift, Kubernetes, Docker or virtual machines. Every change passes a role check and the G8 engine and is recorded before it’s applied. Analytics and request records stay in your own data stores.
Elasticsearch
external services
What G8 does differently
Rate limits, identity and AI routing are on the platform pages. This is what sets G8 apart: where it runs, how it controls change, where its data stays and who supports it.
Every part of G8 runs in your infrastructure
G8, its console and management API, its database and the G8 engine clusters it manages run where you install them: OpenShift, Kubernetes, Docker or virtual machines. Analytics, alerts, request records and the audit log stay there too.
Traffic leaves your infrastructure only where a Route sends it: to the LLM providers you choose, and to the services a few AI Plugins connect to. Each of those is marked “Connects to an external service.”
Elasticsearch, OpenSearch
moderation
vector search
Lakera Guard
Every change checked and recorded before it’s applied
Ask an auditor what they need from an API gateway and you get three questions: who changed it, what exactly changed, and could anyone have changed it without a trace. G8 is built so that the answer to the third is no.
A change made through G8 is refused unless the person’s role allows it and the G8 engine accepts it, and it is not applied until its audit record has been written. A refused attempt is recorded as well.
The record keeps the actor, the Environment, the time and the values before and after, with secret fields masked. Export records as CSV, or take every one to your SIEM as a structured log line.
One console for every Environment
Most teams end up with a gateway per cluster and a different way of working on each. In G8, Development, Staging and Production are Environments of one installation: the same Routes, Plugins and roles, seen side by side.
Access is granted per Environment and promotion is a deliberate step, so what runs in Production got there through someone with the right to put it there.
- Clusters you already runAdd a gateway cluster as an Environment, or remove one, without touching the G8 engine that serves it.
- Roles stop at the EnvironmentEditor on Staging means nothing on Production until someone grants it there.
- Promotion you review firstCopy a Route to Production and G8 lists what will change there, and what is missing, before you save.
Analytics and request records in your own data stores
Analytics reads request counts and response times from the Prometheus of each Environment. Traffic Explorer keeps the gateway’s own request records in your Elasticsearch or OpenSearch, for as long as you set.
G8 evaluates alert rules itself and sends alerts by email or signed webhook. System alerts tell your team when the G8 engine or Prometheus can’t be reached.
Support in Turkish and English, included in the license
You get engineering support in Turkish and English, and our engineers work with your team when you install and upgrade G8. Support and help with installation and upgrades are included in the G8 license.
Turkish and English.
Our engineers work with your team when you install G8 and when you upgrade it.
Customers open support requests in the support portal.
Five questions to ask any gateway vendor
Ask these before you choose a gateway, us included. Here is how G8 answers each one.
Where does the console run, and what happens when the internet link is down?
A control plane you don’t host is a dependency you can’t audit.
Every part of G8 runs in your infrastructure. The license is a signed file checked locally, so a network without internet access changes nothing.
Can a change reach Production without a record?
If the answer is “in theory, yes”, the audit trail is optional.
No. A change through G8 is applied only after its audit record is written, and a refused attempt is recorded as well. Automation takes the same path with service accounts.
Can AI agents call our existing APIs with the rules they already have?
Rebuilding every API as an MCP server is a second codebase to secure.
Yes. openapi-to-mcp serves an API you already run as MCP tools, on a Route that keeps its authentication, rate limits and request records.
Where do request records and analytics live?
Observability data is production data.
In your Prometheus and your Elasticsearch or OpenSearch. G8 reads them for Analytics, Traffic Explorer and Alerts; it doesn’t copy them anywhere.
Who answers when something breaks, and what does that cost?
Support that isn’t in the license becomes a ticket about the ticket.
Engineering support in Turkish and English is included in the Enterprise license, and our engineers install and upgrade G8 with your team.
One license for every area
One console, one set of roles and one audit record cover all four. Each page shows what its area does.
Rate limits, identity, logging and traffic rules, with Analytics and Traffic Explorer
LLM providers with fallback, token limits and OpenAPI to MCP
Authentication, access rules, roles and an audit record of every change
A catalog of your APIs with documentation and self-service access