MirevoxGitHub (opens in a new tab)

Module 01 · Model routing

runnable

Smart Router

One intended path to cloud and local models.

View on GitHub (opens in a new tab)

Runnable v0.1 slice available on GitHub — architecture and scope below.

Problem

Model access gets scattered across provider keys, endpoints, deployment rules, and separate UIs. Even a VS Code assistant and a home chatbot can end up repeating the same integration work.

Where it sits

Sits between clients and the model platforms they call: Foundry, Bedrock, Vertex/Agent Builder, or local models. It is meant to give VS Code, a home chatbot, and other tools one stable endpoint.

The router is designed to onboard services by reference and poll them for current endpoint information—including UIs that live elsewhere. Provider interfaces stay where they are; Mirevox keeps the reference, central credentials, and routing policy.

A request can target on-prem or cloud capacity according to the activity, then fan out when several models or toolsets need to answer the same input. VS Code, a side agent, and a home chatbot are meant to call the same endpoint instead of each learning every provider. Works alongside LiteLLM-class proxies; it is not locked to one proxy stack.

How it fits

This is the path through the control plane. Evals & English Governance and Data Lineage are meant to observe requests on that path using request and trace IDs, while the thin hub composes the modules without absorbing their jobs.

Capabilities