+4
Daily
9,770
stars
1,388
forks
71
watchers
2,362
prs
2,485
issues
72
releases
README
AI Gateway
AI Native API Gateway
Official Site |
Docs |
Blog |
Roadmap |
MCP Server QuickStart |
Developer Guide |
Wasm Plugin Hub |
English | 中文 | 日本語
What is Higress?
Higress is a cloud-native API gateway based on Istio and Envoy, which can be extended with Wasm plugins written in Go/Rust/JS. It provides dozens of ready-to-use general-purpose plugins and an out-of-the-box console (try the demo here).
Core Use Cases
Higress's AI gateway capabilities support all mainstream model providers both domestic and international. It also supports hosting MCP (Model Context Protocol) Servers through its plugin mechanism, enabling AI Agents to easily call various tools and services. With the openapi-to-mcp tool, you can quickly convert OpenAPI specifications into remote MCP servers for hosting. Higress provides unified management for both LLM API and MCP API.
🌟 Try it now at https://mcp.higress.ai/ to experience Higress-hosted Remote MCP Servers firsthand:
!Higress MCP Server Platform
Production Adoption
Higress originated at Alibaba to address long-connection disruption during
gateway reloads and improve gRPC/Dubbo load balancing. It is now developed as
a vendor-neutral CNCF project and is used by organizations across multiple
industries. Public adopters and their use cases are listed in
ADOPTERS.md.
Summary
- Quick Start
- Feature Showcase
- Use Cases
- Core Advantages
- Community
Quick Start
Higress can be started with just Docker, making it convenient for individual developers to set up locally for learning or for building simple sites:
bash
Create a working directory
mkdir higress; cd higress
Start higress, configuration files will be written to the working directory
docker run -d --rm --name higress-ai -v ${PWD}:/data \
-p 8001:8001 -p 8080:8080 -p 8443:8443 \
higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/all-in-one:latest
Port descriptions:
- Port 8001: Higress UI console entry
- Port 8080: Gateway HTTP protocol entry
- Port 8443: Gateway HTTPS protocol entry
Higress publishes project images through dedicated regional registry
endpoints. Operators may mirror the images to a registry they control and
configure the Helm global.hub value accordingly.
If you experience a timeout when pulling image from higress-registry.cn-hangzhou.cr.aliyuncs.com, you can try replacing it with the following docker registry mirror source:
North America: higress-registry.us-west-1.cr.aliyuncs.com
Southeast Asia: higress-registry.ap-southeast-7.cr.aliyuncs.com
For Kubernetes deployments, you can configure the global.hub parameter in Helm values to use a mirror registry closer to your region. This applies to both Higress component images and built-in Wasm plugin images:
bash
Example: Using North America mirror
helm install higress -n higress-system higress.io/higress --set global.hub=higress-registrTop issues
#1023使用 Higress + LobeChat 快速搭建私人GPT助理(支持 RAG、联网)44 comments · 2024-05-31#938使用 Higress + NextChat 快速搭建私人GPT助理36 comments · 2024-05-14#459基于请求路径的动态路由功能支持34 comments · 2023-08-02#4290Design: GIE 显式 BuiltIn ai-endpoint-picker 与 External EPP 兼容 || Design: GIE explicit BuiltIn ai-endpoint-picker compatible with External EPP32 comments · 2026-08-07#4067ai-token-ratelimit 插件不生效:配置正确但从不连接 Redis(cx_total/cx_connect_fail 恒为 0,WasmPlugin config_fail 持续增长) || ai-token-ratelimit plug-in does not take effect: the configuration is correct but never connects to Redis (cx_total/cx_connect_fail is always 0, WasmPlugin config_fail continues to grow)32 comments · 2026-07-05#288dubbo-zk http转换dubbo协议如何配置31 comments · 2023-04-12#1424关于higress是否支持根据model路由的提问29 comments · 2024-10-23#425What features do you expect from Higress 1.x28 comments · 2023-07-10
Discussions
#5362helm安装的higress,监控面板的监控数据只保留了最近10小时左右,如何调大,如保留1个月0 comments · 2026-11-15#5361rerank and embedding model monitor1 comments · 2026-11-14#5356请问Higress 支持 Gateway API 的 BackendLBPolicy 资源吗?3 comments · 2026-11-13#5128申请 Higress Member 头衔(@ai-yang)0 comments · 2026-10-17#5046。0 comments · 2026-10-09#5037Complementary evidence layer: offline-verifiable attestation on top of MCP tool-call audit logs (iqa-mcp)0 comments · 2026-10-08#4700v2.2.4和v2.2.3模型请求参数是否做了调整?1 comments · 2026-09-14#4654为什么记录在opentelemetry traces里的guid:x-request-id信息和发给上游服务header里的x-request-id是不一样的?0 comments · 2026-09-07
Latest release
v2.2.6 v2.2.6 2026-11-10Higress 📋 Release Overview This release includes 76 updates, covering feature enhancements, bug fixes, performance optimizations, and more. Distribution of Updates - New Features: 2 - Bug Fixes: 49 - Refactoring & Optimizations: 8 - Documentation Updates: 10 - Test Improvements: 7 --- 📝 Full Changelog 🚀 New Features (Features) - Related PR: 5328 \ Contributor: @higress-release-automation[bot] \ Change Log: This PR prepares the plugin snapshot release v2.2.6 by introducing three core release metadata files (evidence, plans, snapshots) and updating the VERSION files for the ai-a