explaingit

higress-group/higress

8,370GoAudience · ops devopsComplexity · 4/5Setup · moderate

TLDR

An API gateway built for both AI and regular web traffic that sits in front of your services to handle routing, authentication, rate limiting, and monitoring, with special support for connecting to AI language model providers and hosting AI agent tool servers.

Mindmap

mindmap
  root((repo))
    What it does
      API gateway
      AI model routing
      MCP server hosting
    AI features
      Multi-provider interface
      Token rate limiting
      Response caching
    Kubernetes
      Ingress controller
      Helm deployment
      nginx annotation compat
    Plugins
      WebAssembly based
      Go Rust JavaScript
      Web admin console
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Replace your existing Kubernetes ingress controller with Higress to gain AI gateway features without rewriting your routing rules.

USE CASE 2

Connect your app to multiple AI model providers through one gateway instead of managing separate API keys and formats for each.

USE CASE 3

Host MCP tool servers as plugins inside Higress so AI agents can call external tools with centralized auth and rate limiting.

USE CASE 4

Convert an existing REST API described in OpenAPI format into an MCP server automatically, making it callable by AI agents.

Tech stack

GoRustJavaScriptWebAssemblyIstioEnvoyKubernetesHelm

Getting it running

Difficulty · moderate Time to first run · 30min

Local start requires only Docker, full production use on Kubernetes requires Helm and an existing cluster.

License not specified in the explanation.

In plain English

Higress is an API gateway built on Istio and Envoy, originally created inside Alibaba to handle internal production traffic at scale. An API gateway sits in front of your services and controls how incoming requests are routed, authenticated, rate-limited, and monitored. Higress is specifically designed with AI use cases in mind, in addition to handling ordinary web traffic. The AI gateway side of Higress connects to a wide range of language model providers through a single unified interface. Instead of your application handling separate connections, authentication tokens, and formats for different AI providers, Higress acts as a central point that translates requests and manages concerns like token-based rate limiting, load balancing across multiple models, response caching, and usage observability. This applies to both major international providers and Chinese domestic ones. A second major capability is hosting MCP servers. MCP (Model Context Protocol) is a standard that allows AI agents to call external tools and services. Higress can run these MCP servers as plugins and expose them through its gateway, providing centralized authentication, rate limiting, audit logs, and monitoring for every tool call. There is also a companion tool that converts existing OpenAPI service descriptions into MCP servers automatically. For teams deploying on Kubernetes, Higress can also serve as a standard ingress controller, compatible with most configuration annotations already used with the common nginx ingress controller. This means it can replace an existing gateway without rewriting routing rules. Plugins are written in WebAssembly using Go, Rust, or JavaScript, and dozens of ready-to-use plugins ship with the project. A web-based admin console is included for managing configuration. Higress can be started locally with a single Docker command and deployed to Kubernetes via Helm. It is a CNCF Sandbox project with an enterprise edition available on Alibaba Cloud.

Copy-paste prompts

Prompt 1
I want to try Higress locally with Docker. Give me the single Docker command to start it and a curl request that proves it is working.
Prompt 2
How do I configure Higress to load-balance requests across two different AI model providers, falling back to the second if the first is rate-limited? Show me the plugin config.
Prompt 3
I have an OpenAPI spec for my REST API. How does Higress convert it into an MCP server so AI agents can call my endpoints as tools?
Prompt 4
Walk me through writing a simple Higress plugin in Go compiled to WebAssembly that adds a custom response header to every request.
Prompt 5
How do I deploy Higress to Kubernetes using Helm? Give me the minimal install command and explain what the ingress controller mode means.
Open on GitHub → Explain another repo

← higress-group on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.