Ramp opens its internal AI Router to early users
Ramp says its Router service reduced the company's LLM costs by about 30 percent while handling more than 2.75 trillion tokens a month. The early-access product packages model selection, fallback and usage tracking, but its cost and quality case has yet to be shown outside Ramp's own workloads.
- Ramp says Router handles more than 2.75 trillion tokens a month internally and lowered its LLM costs by about 30 percent.
- The early-access service provides one OpenAI-compatible endpoint, automatic routing and provider fallbacks, while tracking model and spend data.
- Automatic multi-model routing is not new; the key unanswered question is how Ramp's internal cost and quality claims translate to outside workloads.
Ramp is opening early access to Router, a model-routing service it says has operated across more than 100 of its own AI use cases. In its launch page, the company says the system routes more than 2.75 trillion tokens monthly, adds 30 milliseconds of latency and has a 99.9% successful-route rate. It also says Router reduced its LLM costs by roughly 30%.
Those are sizable operating figures, but they are all Ramp’s own measurements. The company does not provide the time period or calculation behind the 30% reduction, a before-and-after cost base, or task-level quality results. That makes the claim evidence of Ramp’s internal deployment, not a savings estimate for a prospective customer.
Veeral Patel wrote in a LinkedIn post that Ramp built the internal router three years ago and that it powers AI products for 70,000 customers, initially to save money. He framed the public release around a familiar problem: model prices and capabilities change, while applications are often built around a chosen provider.

Ramp’s Router product page depicts its model-selection interface for an invoice-extraction request. Source: Ramp.
What Ramp is actually offering
Router is an intermediary, rather than a new model. Ramp says a developer can point an OpenAI-compatible integration at its endpoint; Router can then choose among eligible models on quality, cost and availability, handle provider updates and fall back to another available model during an outage or rate limit.
Its stated selection policy is more specific than “use the cheapest model.” Ramp says it tests new models on its real work and sends requests to the lowest-cost option that clears its quality bar. The product page illustrates the kinds of trade-offs it is attempting to make: high-volume invoice extraction, low-cost support-ticket classification, long-context summarisation, contract review, coding, translation and moderation do not call for the same capability or latency.