Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for platform teams that want a vendor-neutral, Apache Software Foundation -governed API gateway with a first-class AI Gateway positioning for LLM traffic, for teams adopting the canonical mcp-bridge plugin to convert stdio MCP servers into scalable HTTP SSE services, for organizations that need token-based rate limiting and robust authentication on AI workloads, and for anyone wanting to
Where this stands now
apache/apisix ranks #5 of 10 tracked AI Gateway items by composite score (7.9 against a section median of 7.9). The section currently carries 6 Gold, 4 Silver. RepoRadar has retained observations for this record since 2026-08-21 (27 days in the current window). Signal extremes versus the section: novelty at the 30th percentile.
Who should use it
Who should skip it
Skip apache/apisix if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
apache/apisix is tracked by RepoRadar as a developer tool in the AI Gateway section. First seen 2026-08-21; the source record was last checked on 2026-08-21. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. The standout signals for apache/apisix are workflow potential (9.0) and open-source/build quality (8.4), while setup ease (7.0) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar captured from https://github.com/apache/apisix.
How this item is evaluated
The apache/apisix record combines a 7.9/10 composite score with separate popularity (100.0), risk (low), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The quickstart uses a piped remote installer (curl -sL https://run.api7.ai/apisix/quickstart | sh) -- a customer adopting apache/apisix must own the curl-piped-installer review and validate the script checksum against the documented release artifact before installing; The canonical mcp-bridge plugin targets stdio MCP servers specifically (the canonical Model Context Protocol surface for HTTP SSE remote MCP) -- a customer adopting apache/apisix for production MCP traffic should validate their existing stdio MCP servers against the bridge before adopting it for production traffic; The canonical AI proxying surface depends on per-provider plugin extensions (plugins/wasm-go/extensions/ai-proxy/provider) -- a customer adopting apache/apisix for production LLM traffic should validate the per-provider coverage against their LLM provider roster before adopting it; The project requires NGINX + etcd as the canonical architecture -- a customer adopting apache/apisix for production traffic should validate the etcd configuration store ownership against their etcd ownership policy before rollout.