One Console, Nine Doors: Notes on the nRouter DashboardDocumentation usually describes a dashboard screen by screen. nRouter's dashboard guide does something more useful: it describes the console as a map, and spends most of its length on the decisions an1d ago · 3 min readnrouter.hashnode.dev
Lowest Recent p95 Wins: Latency Routing Without Retry CodePin an application to one model name and you inherit that provider's worst day. This article covers the gateway configuration that replaces per-service retry code: a router alias with the Latency stra1E1d ago · 4 min readnrouter.hashnode.dev
Verify from the Response, Not from Hope: Notes on the nRouter Migration GuideMigration guides usually end at "change these settings." The nRouter migration guide keeps going, into the part teams actually get wrong: proving the switch worked. Its standard is worth borrowing for1d ago · 3 min readnrouter.hashnode.dev
Two Constructor Arguments: The Whole Migration to One Key for Every ProviderHere is the entire diff between "we use one provider" and "we can reach every provider in our catalog": - client = OpenAI(api_key=os.environ["OPENAI_API_KEY"]) + client = OpenAI( + base_url="https2d ago · 3 min readnrouter.hashnode.dev
One Key Per Job: Per-Key Budgets, Rate Limits, and Audit Trails in nRouterThe most common API key setup in production is also the worst: one shared key, used by every service, every environment, and every teammate, with no way to answer the question "which system made this 2d ago · 2 min readnrouter.hashnode.dev
