apollographql/router

A configurable, high-performance routing runtime for Apollo Federation 🚀

Owned by Apollo GraphQL

View on GitHub ↗Jump to charts ↓

apollographql/router has 950+ stars and 300+ forks on GitHub, is written in Rust, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 9 minutes ago
Added to GitGenius on October 12th, 2026
Created on November 4th, 2021
Open Issues & Pull Requests: 314 (+0)
GitHub issues: Enabled
Number of forks: 347
Total Stargazers: 982 (+0)
Total Subscribers: 29 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 24.0 days
Mean response time: 278.1 days
90th percentile: 973.9 days
Tracked items: 472

Maintainer activity

6 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 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in about 5 days, while "component/rhai" waits about 5 months. Only 49% of issues opened in the past year have been closed. Three people close 77% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 124
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 731 days
Stale 30+ days: 119
Stale 90+ days: 111

Recent activity

Opened in 7 days: 2
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • raised by user (319)
  • component/open-telemetry (24)
  • documentation (16)
  • component/rhai (14)
  • bug (13)
  • component/coprocessor (12)
  • potentially-breaking (10)
  • component/cache (9)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Apollo Router is a configurable, high-performance routing runtime for Apollo Federation that serves as a gateway for federated GraphQL graphs.

Apollo Router solves the problem of efficiently routing requests across a federated GraphQL architecture where multiple subgraphs are composed into a single graph. It acts as the entry point that receives client queries, routes them to the appropriate subgraphs, and assembles the results. The tool is built in Rust to prioritize performance and handles the complexity of query planning and execution across distributed subgraph services.

Teams building federated GraphQL architectures should consider Apollo Router if they need a production-grade gateway with strong performance characteristics. It suits organizations that have already adopted Apollo Federation and want a dedicated routing layer rather than embedding federation logic in their application code. The tool is particularly relevant for teams operating multiple GraphQL subgraphs that need centralized request handling, composition, and execution.

The project shows active development with regular updates to core functionality and configuration options. Work spans both foundational improvements to the routing runtime and expansion of features for federation scenarios. The maintainers respond to issues and incorporate feedback from users operating federated graphs in production environments.