Skip to navigation

Learn the key concepts

Fabric AI Gateway manages how your applications, tools, and agents reach LLM providers, MCP servers, and internal, external, or public APIs. You connect a provider or API, expose it through a gateway route, and then attach plugins to the route to control authentication, routing, and other behavior. You can review every request in the console.

This topic shows how the main parts fit together. For the definition of any term, see the Glossary. To learn which sidebar items you can see and set up your first route, see Explore the console.

How the pieces fit together

  • An organization is isolated from every other organization. It holds connections, members and their roles, invitations, API keys, and namespaces. A namespace separates teams’ connections, analytics, traces, and users.
  • A connection links the gateway to an upstream. A route sends requests to one or more connections.
  • A plugin is attached at a scope: globally, or to a connection, a route, a consumer, or a consumer group. The data plane runs each plugin on the requests that match its scope.
  • A consumer is the caller that a gateway key or token identifies. An access mode on a connection or route decides whether a consumer needs a grant.
  • The control plane holds the configuration that you set up, and the data plane carries the requests. Requests are recorded in analytics, and in traces when they’re sampled, which you can view for the current namespace or, under Admin, for the whole organization.

Next steps