api7/aisix

The open-source, Rust-native AI gateway for LLMs and AI agents
**One OpenAI-compatible API in front of every model.** Route, govern, secure, cache, and
observe all your LLM and AI-agent traffic from a single control point — shipped as one
static binary with low per-request overhead. Run it in your infrastructure for free,
forever.
*Built by the original creators of Apache APISIX.*
**Start free** ·
**Documentation** ·
**Quickstart** ·
**AISIX Enterprise and AISIX Cloud** ·
**Roadmap**
---
**AISIX OSS** is the open-source product built around the Rust-native AISIX gateway. The
gateway puts a single, OpenAI-compatible API in front of every LLM provider — OpenAI,
Anthropic, Google Gemini, AWS Bedrock, Azure OpenAI, DeepSeek, and any OpenAI-compatible
endpoint. It gives platform teams one place to route, govern, secure, and observe LLM
traffic, with first-class SSE streaming and low gateway overhead.
It runs as a **single static binary** — low cold-start, lock-free config reads, and hot
configuration reloads with no restarts: declare resources in one resources.yaml and
reload on SIGHUP, or point the gateway at etcd for a multi-replica cluster. Run the
gateway in your infrastructure, or connect it to **AISIX Enterprise** or
**AISIX Cloud**
for centralized management with team governance, budgets, audit, and a dashboard.
> **AISIX OSS (this repo)** is the open-source product. It runs without a control plane
> using declarative configuration or etcd. The same gateway binary serves as the data
> plane in the commercial products: customers host the control plane with **AISIX
> Enterprise**, while API7 hosts it with **AISIX Cloud**. In all three products, the
> gateway runs in your environment and calls providers directly; live AI traffic does not
> pass through either control plane. The proxy API is identical throughout.
> **Talk to us about AISIX Enterprise or AISIX Cloud →**
⚡ Quickstart
One container. No control plane, no database, no configuration store — the gateway reads
every dynamic resource from one declarative resources.yaml.
Then call the gateway exactly like OpenAI:
Edit resources.yaml and send SIGHUP (docker kill -s HUP aisix) to apply changes with
no restart — an invalid file is rejected whole and the last good configuration keeps
serving. Check a file before booting with aisix validate --resources resources.yaml.
Full walkthrough: the
Gateway Quickstart ·
every field: the resources file reference.
For a multi-replica cluster, point the gateway at etcd instead — resources_file and
etcd are mutually exclusive.
✨ Why AISIX
- **One API, every model.** Speak the OpenAI *or* Anthropic wire format in; the gateway
translates to whichever provider each model points at. Point an OpenAI or Claude SDK at
one base_url and switch models without changing code.
- **A real gateway, in Rust.** Single static binary, low cold-start, lock-free config reads
on the hot path, native streaming.
- **Open source, free forever.** Apache-2.0 licensed and built to run in your
infrastructure. Choose AISIX Enterprise or AISIX Cloud when you want centralized
management through a control plane and dashboard.
- **Production controls built in.** Routing & failover, rate limits, guardrails, caching,
and observability ship in the box. (Budgets and spend caps are AISIX Enterprise and
AISIX Cloud features — the gateway enforces the control plane's decisions.)
🧩 Features — available today
Covered by 183 end-to-end scenario files (496 cases) that run against real gateway processes.
- **OpenAI-compatible proxy** (:3000) — chat/completions, completions, responses,
embeddings, rerank, images/{generations,edits}, audio/{speech,transcriptions,translations},
videos (submit → poll → fetch), files, batches, fine_tuning/jobs, realtime,
GET /v1/models, plus a root-level /passthrough/:provider/* escape hatch. Native SSE streaming,
tool/function calling, JSON mode, vision/multimodal input, and reasoning-content support.