Factory.ai

Frontier performance at lower cost

AI coding costs are rising across organizations.

Enterprise AI costs are climbing, and a bigger token bill does not mean more work is getting done. To avoid losing on performance, engineers usually default to the most performant model for all tasks. Simple questions, mechanical refactors, documentation updates, small bug fixes, and search-heavy investigations end up on the same premium path as work that truly needs frontier performance. Budgets get exhausted without a clear increase in organization-level output.

Stop choosing a model for every task.

Today you pick a model per task and lean on the most expensive one to be safe. With Factory Router you choose once and it picks the best model for each session.

Same prompts. Different cost.
Without RoutingAlways Claude Opus 4.7
reset my passwordClaude Opus 4.7$0.00
add a copyright headerClaude Opus 4.7$0.00
design a caching layerClaude Opus 4.7$0.00
Total session cost$0.00
With Factory RouterRouted per task
reset my passwordKimi K2.6$0.00
add a copyright headerMiniMax-M2.7$0.00
design a caching layerKimi K2.6$0.00
Total session cost$0.00
Savings on identical work0%

Proven in production.

When measured against what the same workload would cost at Opus rates, most routed sessions complete at a fraction of frontier pricing, while frontier models stay on the work that needs them.

52%

Aggregate cost savings across all routed sessions

73.5%

Median session savings vs Opus pricing

44.8%

Of sessions are at least 80% cheaper

3 in 4

Sessions cost less than half of Opus pricing

Measured in production across all routed sessions · billed usage vs the same workload priced at Opus rates

On our enterprise engineering benchmarks.

Compared with Claude Opus 4.7, Factory Router maintains frontier performance at lower cost per session. At enterprise scale, those savings apply across every Droid session, with spend tied to the work being done rather than a blanket default to the most expensive model. Results in production have exceeded these benchmarks.

TERMINAL-BENCH 2PASS RATE · vs OPUS 4.70%of Claude Opus 4.7 pass rateCOST PER SESSION · vs OPUS 4.70%lowerFactory Router runs at 80% of Opus costCost per successful run · 80.5% of OpusLEGACY-BENCHPASS RATE · vs OPUS 4.70%of Claude Opus 4.7 pass rateCOST PER SESSION · vs OPUS 4.70%lowerFactory Router runs at 75% of Opus costCost per successful run · 78.0% of OpusReported relative to Claude Opus 4.7 · cost measured as full-session cost · averaged across multiple runs

Reliability you can count on.

When a provider degrades, rate limits hit, or capacity gets constrained, your sessions keep going. Factory Router routes across models, providers, and capacity to deliver 99.9%+ request reliability.

Claude Opus 4.7Bedrock· degraded
reroute
Claude Opus 4.7Vertex· healthy

Routing that reflects how your organization works.

Routing guidance brings your team's context into Factory Router, so automatic model selection reflects how work actually happens inside your organization. The same policy surfaces that govern other Factory models apply here, so admins manage access, compliance, and eligibility without a separate control plane.

Admin routing guidance
Automatic model selection for every Droid session
Routing rules & context
Routine refactors, formatting, and doc updatesfavor cost-efficient modelsauth/ and payments/ need deeper reasoningkeep on frontier modelsSearch-heavy investigationroute to open-source models
CancelSave

Use Factory Router in the Factory CLI and Desktop App.

Factory Router is generally available in the Factory CLI and Desktop App. It appears in the model picker for every user with no setup required. Mission workers can use it too, so long-running autonomous work gets the same automatic model selection and savings as interactive and headless sessions.

start building

Ready to build the software of the future?

Start building

Arrow Right Icon