higress-group/higress
🤖 AI Gateway | AI Native API Gateway
What it solves
Higress is an AI-native API gateway designed to handle the specific demands of AI workloads. It solves the problem of managing multiple LLM providers through a unified protocol, while providing essential production-grade controls like token rate limiting, multi-model load balancing, and AI observability. It also simplifies the deployment of AI agents by hosting Model Context Protocol (MCP) servers, allowing agents to access tools and services more reliably.
How it works
Built on Istio and Envoy, Higress uses a Wasm (WebAssembly) plugin architecture. This allows it to extend gateway logic using plugins written in Go, Rust, or JavaScript without restarting the gateway. It supports true streaming processing for request and response bodies, which is significantly reduces memory overhead for high-bandwidth AI streaming protocols like SSE (Server-Sent Events).
Who it’s for
- AI Developers: Those building agents or LLM-powered apps who need a unified way to connect to various model providers.
- Platform Engineers: Teams needing a production-ready Kubernetes ingress controller or microservice gateway with low resource overhead.
- Enterprise AI Teams: Organizations requiring fine-grained security, audit logs, and rate limiting for their AI tool calls and LLM APIs.
Highlights
- AI Gateway Capabilities: Unified protocol for LLM providers, token-based rate limiting, and inference-aware routing on Kubernetes.
- MCP Server Hosting: Ability to host and manage remote MCP servers, including a tool to convert OpenAPI specifications into MCP servers.
- Production Grade: Eliminates traffic jitter during configuration changes, ensuring stable long-connections for AI streaming.
- Wasm Plugin System: Memory-safe, sandbox-isolated plugins that support hot updates without traffic loss.
- Cloud Native: CNCF Sandbox project compatible with Kubernetes Ingress and Gateway APIs.
Related
- Project
- Project
- Project
- Project
- Project