AI traffic gateway

AISIX AI Gateway

Put one stable API contract in front of your AI providers

AISIX AI Gateway is a Rust-native gateway for LLM and AI-agent traffic. The open-source gateway runs as a single static binary and can operate standalone, or you can use AISIX Cloud for centralized management. In either case, applications call stable model aliases while the AI platform team controls provider credentials, routing, failover, rate limits, caching, guardrails, and observability. AISIX Cloud adds centralized usage and budget management.

Get started View supported endpoints

Start an on-premises AISIX Cloud deploymentlocalhost:8080

curl -fsSL https://run.api7.ai/aisix-self-hosted/quickstart | bash

# Starts the control plane and dashboard
# Dashboard: http://localhost:8080

How requests flow

Applications call AISIX first. AISIX authenticates the caller, resolves the model alias, applies policy, and forwards the request to the selected provider.

ApplicationsApps, agents, and servicesSend OpenAI-compatible requests with gateway-issued caller API keys.

AISIX gateway boundaryStable contract, controlled provider access

AISIX keeps client traffic on one API shape while resolving the provider-side target for each request.

Authenticate callerResolve model aliasApply limits, cache, and guardrailsSelect provider route

ProvidersOpenAI, Anthropic, Bedrock, Vertex, AzureReceive provider-authenticated requests from the gateway.

Provider responses return through AISIX using the same client-facing contract.

What changes when AI traffic goes through AISIX

Application teams keep calling a familiar API. AI platform teams move provider credentials, model aliases, routing, and policy into one operator-managed gateway. AISIX Cloud adds shared usage and budget controls.

AccessCaller API keys and model allowlistsAuthenticate applications and decide which model aliases each key can use.

ProvidersCentralized upstream credentialsKeep provider keys, base URLs, and adapter details out of application code.

RoutingStable aliases with failoverExpose one model name while AISIX selects target models behind it.

PolicyLimits, cache, guardrails, telemetryApply AI-specific controls and usage visibility before requests leave your gateway boundary.

Why AISIX if you already use APISIX or API7 Gateway?

APISIX and API7 Gateway can add AI behavior to regular gateway routes through AI plugins. That path fits teams whose main workload is API traffic and whose AI calls are part of a broader API gateway deployment.

AISIX is for teams whose main workload is AI traffic. It manages provider keys, model aliases, caller API keys, routing, policy, and AI usage telemetry as first-class resources instead of route-level plugin settings. AISIX Cloud adds centralized usage views and budgets.

APISIX

Add AI features to existing API routes.Use AI plugins when your existing API gateway route is the natural place to call or transform AI services.

AISIX

Run AI traffic through a dedicated gateway domain.Use AISIX when applications should call stable model names while an AI platform team owns provider keys, routing, policy, and usage visibility.

Choose Your Next Path

Start by choosing how to run AISIX. From there, explore AISIX Cloud, connect an application, or prepare a gateway for production.

Get started

Choose a product and deployment optionRun the open-source gateway standalone, or use AISIX Cloud and decide who hosts the control plane.

AISIX Cloud

Manage AISIX gateways with a control planeUnderstand the control-plane workflow, centralized usage reporting, and budget controls.

Integrations

Connect applications and AI toolsPoint client SDKs, coding agents, and application frameworks at an AISIX gateway.

Production

Prepare the runtime for productionReview deployment, security, health, metrics, and troubleshooting guidance for production gateways.