DigitalOcean Launches Inference Router to Optimize LLM Routing
Configure your application to use the Inference Router by prefixing the model field with "router:" and test routing with the provided API or Playground.
Configure your application to use the Inference Router by prefixing the model field with "router:" and test routing with the provided API or Playground.
Summary
DigitalOcean has released its Inference Router, a new AI-native proxy that automatically selects the most suitable large language model for each request based on task intent, cost, and latency. The router is powered by a 30‑billion‑parameter Mixture‑of‑Experts model fine‑tuned for intent detection, outperforming GPT‑5.1 and Claude Sonnet 4.5 on multi‑turn conversations. It ships with preset routers for Software Engineering, General, Writing, and Knowledge Base workflows, each offering Optimal, Cost‑Efficiency, and Speed‑Optimization selection policies. Developers can also create custom routers by defining tasks, model pools, and fallback models, and test routing behavior in the DigitalOcean Model Studio Playground. The underlying Plano engine classifies intent with a small language model and ranks candidate models using live cost and latency data from DigitalOcean’s pricing API and Prometheus. The router exposes a simple API endpoint where the model field is prefixed with “router:”, and the response includes the chosen model and matched task.
The Inference Router also provides an Evals feature for dataset‑based quality assessment and a dashboard that tracks total requests, token usage, task match rate, and fallback rate. By integrating the router, teams can reduce overpayment for frontier models, lower inference costs, and avoid brittle routing logic in application code.
Key changes
- DigitalOcean’s Inference Router automatically selects the best LLM per request using a 30B Mixture‑of‑Experts intent model
- Preset routers for Software Engineering, General, Writing, and Knowledge Base with Optimal, Cost‑Efficiency, and Speed‑Optimization policies
- Custom routers allow task definition, model pools, selection policies, and fallback models
- Plano engine classifies intent and ranks models using live cost and latency data
- API endpoint uses "router:" prefix and returns selected model and task match
- Evals feature enables dataset‑based quality assessment
- Dashboard tracks requests, token usage, task match rate, and fallback rate