Weave Router Review: Does It Cut LLM Costs 40-70%?
By Matt Cullerton, founder of Mavric and Apso
Weave Router is a drop-in proxy for Anthropic, OpenAI and Gemini that picks a model for each request using a small on-box embedder. A TikTok from @github.signals says it cuts AI bills 40 to 70 percent without making models "dumb." Those figures come from the repository's one-line description, not from any published measurement, and the repo's own benchmarks show it saving money against frontier models while scoring 2 to 6 points lower.
What is Weave Router?
The README's tagline is "One endpoint. Every model. Always the right one." It describes the tool as "A drop-in proxy for Anthropic, OpenAI, and Gemini that picks the best model for every request: using a tiny on-box embedder, not a vibes-based prompt." It routes per action, supports open-source models through OpenRouter, lets you bring your own keys, and emits OTLP traces. The quickstart is npx @weave-os/router.
On the GitHub API, weave-os/router had 4,535 stars, 125 forks and 131 open issues, written in Go, created 2026-04-27 and last pushed 2026-09-20. Weave Router 2.0 was #1 Product of the Day on Product Hunt on September 16, 2026, with 341 upvotes.
Is Weave Router open source?
No. The video's description says "Open source," but the README badge and LICENSE file say Elastic License v2. ELv2 forbids offering the software to third parties as a hosted or managed service and forbids getting around license key features. The OSI does not list it as open source, and GitHub reports the license as NOASSERTION. The accurate term is source-available. Running it internally is fine. Reselling routing as a service is not.
Where do the 40-70% and under-50ms figures come from?
Both appear in the repository description: "Routes every prompt to the right model in <50ms. Cut costs 40-70% with just an endpoint change." The README body contains neither number.
Weave's other materials give different figures:
- The Avengers-Pro paper, which Weave's scorer is based on, reports a 27 percent cost reduction at matched accuracy and a 7 percent accuracy gain over GPT-5-medium at matched cost.
- Weave's launch post says "60 to 70 percent of requests are short, structurally simple completions that an open-source model handles at parity." That is a share of requests, not of cost.
- The same post claims "80 to 85 percent cost reductions with no observable quality regression" on production Claude Code traffic, and routing overhead of "low single-digit milliseconds."
None of these come with a published workload mix, model pair or baseline.
What do Weave Router's own benchmarks show?
The README links a benchmark harness, bench/README.md, that runs Codex CLI through the router against Codex pinned to one model, and against OpenRouter's auto-beta router as a control. The published results:
| Comparison | Router | Control | Cost |
|---|---|---|---|
| Atlas vs Sol | 47.6% pass | 53.2% pass | $262 billed vs $445 list |
| Atlas vs Astra (max) | 55.6% pass | 57.7% pass | $573 billed vs $1,250 list |
| Atlas vs Luna | 60.1% pass | 46.4% pass | $692 billed vs $127 list |
| Atlas vs OpenRouter auto-beta | 60.1% pass | 60.9% pass | $692 vs $612 |
| TB4 vs Sol | 24.6% pass | 30.3% pass | $399 billed vs $633 list |
| TB4 vs Luna | 25.8% pass | 0.8% pass | $651 billed vs $36 list |
| TB4 vs OpenRouter auto-beta | 25.8% pass | 19.0% pass | $651 vs $668 |
Against the frontier models Sol and Astra, the router costs less and scores lower: 5.6 and 2.0 points lower on SWE-Atlas and 5.7 points lower on Terminal-Bench 4.0. The confidence intervals cross zero, so neither a quality loss nor quality parity is statistically established. Against the cheap Luna model, the router scores much higher and costs five to eighteen times more. On SWE-Atlas it roughly ties OpenRouter's auto-beta, which needs no installation.
Routing moves you along a cost and quality curve. The Avengers-Pro paper describes the same tradeoff, with settings for efficiency first, performance first, or a band in between.
The harness also notes that "router-billed" costs use Weave's own catalog rates, while "list" costs come from Codex's client-side usage times a generated price book. They are different accounting bases.
What are the risks of LLM routing?
Weave embeds each request, scores it against clusters, and picks a model. Three tradeoffs follow:
- Added latency. The embedding pass is cheap but runs on every request, including ones that end up on the frontier model anyway.
- Uneven mistakes. Sending an easy task to an expensive model wastes cents. Sending a hard task to a cheap model can produce a wrong answer that an agent retries at full price, and a bad tool call returns HTTP 200 like a good one.
- Many decisions per request. The router decides per action, as documented in
docs/SEMANTICS.md, so one agent task triggers dozens of routing choices, and small error rates add up.
Weave Router alternatives
- LiteLLM (
BerriAI/litellm): 59,214 stars, the most widely deployed self-hosted AI gateway, with configuration-based routing, fallbacks, budgets and key management. - Portkey Gateway: 13,040 stars, MIT licensed, with guardrails, observability and a hosted tier.
- RouteLLM from LMSYS: 5,510 stars, Apache-2.0, a framework for training and evaluating routers. LMSYS reported about 35 percent cost reduction on GSM8K at 95 percent of GPT-4 quality.
- OpenRouter: the hosted aggregator whose
auto-betarouter Weave uses as a benchmark control. - Avengers-Pro: the academic implementation behind Weave's scorer.
For a neutral comparison, RouterArena (arXiv:2510.00202) evaluates 12 routers across 9 domains on accuracy, cost, optimality, robustness and latency, and keeps a live leaderboard. It found that no single router is best across the accuracy and cost frontier.
Bottom line
Weave Router is a real, active project that publishes honest benchmarks: it saves money against frontier models at a small, statistically uncertain accuracy cost, and ties OpenRouter's router on one benchmark. The 40-70% figure has no published method behind it, and the license is source-available, not open source. Test it on your own traffic before trusting any savings number.
Sources
- weave-os/router: the repository.
- bench/README.md: benchmark harness and results.
- Avengers-Pro paper: the routing method Weave builds on.
- ZhangYiqun018/AvengersPro: the paper's code.
- Introducing Weave Router: Weave's launch post.
- RouterArena paper: neutral router benchmark.
- RouteWorks/RouterArena: RouterArena code.
- BerriAI/litellm: LiteLLM gateway.
- Portkey-AI/gateway: Portkey gateway.
- lm-sys/RouteLLM: RouteLLM framework.
- RouteLLM results (LMSYS): LMSYS cost results.
- Elastic License 2.0: the license text.
Published September 18, 2026. Based on a TikTok by @github.signals. Full video notes (markdown)