vllm-project/semantic-router

A programmable Mixture-of-Models router for heterogeneous LLM inference

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 7 minutes ago
Added to GitGenius on September 11th, 2026
Created on August 26th, 2025
Open Issues & Pull Requests: 538 (+0)
GitHub issues: Enabled
Number of forks: 937
Total Stargazers: 5,759 (+2)
Total Subscribers: 62 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.1 hours
Mean response time: 4.7 days
90th percentile: 8.4 days
Tracked items: 1,433

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 21% of open issues come from outside the core team — the tracker reads mainly as internal planning. Almost all tracked open issues have seen activity in the last three months. Only 4% of issues opened in the past year have been closed. Three people close 80% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 371
New in 7 days: 128
Closed in 7 days: 73
Avg open age: 32 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 121
Closed in 7 days: 70
Comments in 7 days: 60
Events in 7 days: 405

Top labels

  • enhancement (553)
  • accepted (445)
  • bug (354)
  • priority/P1 (196)
  • roadmap (163)
  • in-progress (148)
  • wg/router-models-inference-runtime (125)
  • needs-acceptance (113)

Detailed Description

Semantic Router is a programmable routing layer for building Mixture-of-Models systems across heterogeneous LLM infrastructure.

The tool addresses the fragmentation of modern LLM deployments where models specialize in different tasks, compute resources span GPUs, accelerators, edge devices, and cloud environments, and inference needs to respect data locality and privacy boundaries. Semantic Router evaluates request signals, user preferences, and application policies to select or compose the appropriate model path for each request, allowing routing decisions to be made dynamically without embedding logic into applications.

Teams should adopt this tool when managing multiple specialized models across diverse infrastructure and needing to route requests based on quality, cost, latency, privacy, or safety considerations that vary by user or workload. It suits systems where the optimal model choice depends on factors beyond a single metric and where keeping data within specific boundaries matters. The tool is particularly valuable for organizations operating edge, private, and cloud infrastructure simultaneously and wanting to compose personalized model paths rather than hard-coding routing decisions.

The project's open issues are raised mostly by its own members, reading more as internal planning than inbound user demand. Maintainers typically respond to new issues and pull requests within hours. Work in the issue tracker is dominated by enhancement, accepted, and bug labels.