Item detail
github.com

envoyproxy/ai-gateway

envoyproxy/ai-gateway is a developer tool that RepoRadar is tracking in its Radar section, currently rated Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 10.0 out of 10.

Score8.7
Popularity8.5
Risklow
TierGold
Score breakdown
Usefulness9.0
Novelty8.0
Momentum9.0
Maturity6.9
Open-source/build8.4
Evidence7.2
Workflow potential10.0
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for platform engineers, SREs, and Kubernetes operators who already run Envoy Gateway, because Envoy AI Gateway reuses the existing Envoy data plane for LLM routing and governance, which means a single control plane can govern both traditional microservice traffic and LLM-backed traffic without running a second proxy stack.

Who should use it

Platform engineers and SREs who already run Envoy Gateway and want LLM traffic on the same data plane Kubernetes operators who need to route, observe, and rate-limit LLM calls alongside microservice traffic Teams evaluating a CNCF-governed LLM gateway instead of a vendor-specific proxy

Who should skip it

Skip envoyproxy/ai-gateway if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.

About this signal

envoyproxy/ai-gateway is tracked by RepoRadar as a developer tool in the Radar section. First seen —; the source record was last checked on 2026-06-21. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. envoyproxy/ai-gateway leads on workflow potential (10.0) and practical usefulness (9.0); its lowest signal is setup ease (6.4), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The envoyproxy/ai-gateway record combines a 8.7/10 composite score with separate popularity (8.5), risk (low), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

It governs LLM traffic on the Envoy data plane, so audit which model providers are routed through the gateway, lock down credentials for upstream LLM APIs, and validate rate-limit and failover behavior before pointing production traffic at it.

Evidence links
Closest alternatives / related signals
ai-gateway envoy cncf kubernetes llm-routing inference api-gateway apache-2.0
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-13T20:20:15Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

44 dated snapshots retained from 2026-06-21 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.7 current · +0.0 net
Repository momentum9.3 current · +0.3 net
GitHub stars (observed)1,924 current · +95 net
GitHub stars1,924 exact observation
Versionv1.0.0
Last release2026-06-23T15:32:39Z
Maintenanceactive
Current risklow
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.79.31,924lowtry nowactive
2026-08-128.79.31,922lowtry nowactive
2026-08-118.79.31,919lowtry nowactive
2026-08-108.79.31,914lowtry nowactive
2026-08-098.79.31,912lowtry nowactive
2026-08-088.79.31,910lowtry nowactive
2026-08-078.79.31,890lowtry nowactive
2026-08-068.79.0Not recordedlowtry nownot recorded
2026-08-058.79.0Not recordedlowtry nownot recorded
2026-08-048.79.31,890lowtry nowactive
2026-08-038.79.31,890lowtry nowactive
2026-08-028.79.31,888lowtry nowactive

Why the record changed

stars changed

Stars changed: 1922 → 1924.

stars changed

Stars changed: 1919 → 1922.

stars changed

Stars changed: 1914 → 1919.

stars changed

Stars changed: 1912 → 1914.

stars changed

Stars changed: 1910 → 1912.

stars changed

Stars changed: 1890 → 1910.

stars changed

Stars changed: 1888 → 1890.

stars changed

Stars changed: 1886 → 1888.

stars changed

Source-observed stars changed: 1885 → 1886. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 1873 → 1875.

stars changed

Stars changed: 1840 → 1873.

stars changed

Stars changed: 1829 → 1840.