higress-group/higress

πŸ€– AI Gateway | AI Native API Gateway

View on GitHub β†—Jump to charts ↓Open shareable report β†’

higress-group/higress has 9.5k+ stars and 1k+ forks on GitHub, is written in Go, and was last pushed on Oct 8, 2026. Data as of . Signed-in members get hourly updates β€” create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 7th, 2026
Created on October 27th, 2022
Open Issues & Pull Requests: 1,307 (+5)
GitHub issues: Enabled
Number of forks: 1,346
Total Stargazers: 9,563 (+1)
Total Subscribers: 74 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.9 hours
Mean response time: 13.9 days
90th percentile: 13.2 days
Tracked items: 1,653

Maintainer activity

37 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

About 19% of issues opened in the past year have never received a reply. 86% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "issue-spec/proposal" is answered fastest, typically in under an hour, while "type/enhancement" waits about 2 days. 38% of tracked open issues have had no activity in three months. Only 46% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 865
New in 7 days: 35
Closed in 7 days: 20
Avg open age: 260 days
Stale 30+ days: 700
Stale 90+ days: 518

Recent activity

Opened in 7 days: 20
Closed in 7 days: 6
Comments in 7 days: 7
Events in 7 days: 15

Top labels

  • area/ai (111)
  • sig/wasm (102)
  • level/normal (88)
  • help wanted (76)
  • type/enhancement (50)
  • good first issue (43)
  • type/bug (39)
  • level/challenge (36)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Higress is a cloud-native API gateway based on Istio and Envoy that emphasizes AI-native capabilities and extensibility through WebAssembly plugins.

The tool addresses the need for unified API management across traditional services and AI workloads. It originated at Alibaba to solve specific problems including long-connection disruption during gateway reloads and improved load balancing for gRPC and Dubbo protocols. Higress extends the Envoy proxy with WebAssembly plugins written in Go, Rust, or JavaScript, providing dozens of ready-to-use general-purpose plugins alongside AI-specific functionality. Its AI gateway capabilities support mainstream model providers both domestic and international, and it can host Model Context Protocol servers, enabling AI agents to call various tools and services. The project includes an openapi-to-mcp tool for converting OpenAPI specifications into remote MCP servers.

Higress suits organizations running cloud-native infrastructure who need to manage both traditional API traffic and AI model access through a single gateway. It is particularly relevant for teams building AI agent systems that require integration with multiple external services and LLM providers. The tool offers an out-of-the-box console for management and can be started with Docker for local development. Teams already invested in Istio and Envoy ecosystems will find natural integration points, though Higress functions as a standalone gateway as well.

The project maintains active development with regular updates to its AI provider integrations and plugin ecosystem. The codebase shows ongoing refinement of core gateway functionality alongside expansion of AI-specific features. Documentation is comprehensive, covering architecture, plugin development, and deployment patterns. The project operates as a vendor-neutral CNCF initiative with adoption across multiple industries documented in its community materials.