solo-io/gloo

The Cloud-Native API Gateway and AI Gateway

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on November 14th, 2024
Created on November 7th, 2024
Open Issues & Pull Requests: 1,874 (+0)
GitHub issues: Enabled
Number of forks: 12
Total Stargazers: 170 (+0)
Total Subscribers: 2 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.6 hours
Mean response time: 35.4 hours
90th percentile: 8.5 hours
Tracked items: 7,166

Maintainer activity

7 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 7, 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

Roughly one issue in three opened in the past year never receives a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "Zendesk" is answered fastest, typically in under an hour, while "trivy" waits about 8 days. 68% of issues opened in the past year have been closed, leaving a working backlog. Three people close 99% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1,867
New in 7 days: 6
Closed in 7 days: 0
Avg open age: 494 days
Stale 30+ days: 1,853
Stale 90+ days: 1,844

Recent activity

Opened in 7 days: 6
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 10

Top labels

  • stale (2,038)
  • trivy (81)
  • vulnerability (81)
  • Zendesk (22)
  • Prioritized (14)
  • Source: CSE/FE (14)
  • Type: CI Test Flake (14)
  • Type: Enhancement (14)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Gloo is an Envoy-powered API gateway and ingress controller built by Solo.io as a cloud-native solution for Kubernetes environments. Written primarily in Go, the project implements the Kubernetes Gateway API specification and serves as both a feature-rich ingress controller and next-generation API gateway. The repository is classified across multiple domains including service mesh, microservices, canary deployments, traffic shifting, load balancing, observability, traffic management, routing, and security.

The core functionality of Gloo centers on function-level routing, which distinguishes it from conventional API gateways. This capability allows requests to be routed directly to various backend types including serverless functions like AWS Lambda or Google Cloud Functions, microservice APIs, legacy applications, and message queues such as NATS or AMQP. This hybrid application support enables organizations to gradually migrate from legacy systems to cloud-native architectures while maintaining existing codebases, allowing different teams to adopt different architectural paradigms simultaneously.

Gloo Gateway recently achieved full conformance with the Kubernetes Gateway API specification while maintaining backward compatibility with existing Gloo Edge APIs. The platform provides comprehensive API gateway features including rate limiting, circuit breaking, retries, caching, request transformation, service mesh integration, security controls, and external authentication and authorization mechanisms. The architecture emphasizes integration with vetted open-source projects, incorporating technologies like gRPC, OpenTelemetry, and NATS to deliver broad functionality without vendor lock-in.

A distinctive feature of Gloo is its automated discovery system, which creates and continuously maintains a catalog of available destinations across IaaS, PaaS, and FaaS providers. This discovery extends to Swagger and gRPC specifications, reducing manual configuration burden and ensuring new services become available to the gateway automatically upon deployment. The platform is designed to support hybrid applications spanning various technologies, architectures, protocols, and cloud providers.

The repository shows active maintenance and community engagement.

Documentation is comprehensive, with a dedicated devel folder serving as the entry point for understanding the codebase and contributing to the project. The project emphasizes security, requesting that potential security issues be reported privately to [email protected] rather than through public GitHub issues, demonstrating a mature approach to vulnerability disclosure.