NuRoute for teams in production

The same model selection that powers NuRoute Chat, inside your product, with the controls a company needs.

Where NuRoute sits

Your app

One request

model: "auto"

NuRoute Gateway

Step 1
Policy and budget checks
Allowed models, regions, PII redaction and spend limits are applied first.
Step 2 · Artemis by NuRoute
Artemis selects the model
It profiles the task and picks the model with the best expected quality for the cost.
Step 3
Provider and fallback
The request goes to an allowed provider. If it fails, NuRoute tries the next best.

Request trace. Every decision, with the candidates considered, is logged and can be replayed.

Providers

Your keys or NuRoute's

Commercial, European and self-hosted endpoints.

Artemis selects the model for each task. The Gateway manages provider access, governance, budgets, fallback and observability.

One integration: One endpoint for every provider. Use your own provider keys or NuRoute’s.
Budgets: Monthly budgets with hard limits per project, so spend can’t run away.
Policies: Allow-lists for models and providers, region rules and PII redaction, checked before a request leaves.
Fallback: If a provider fails, the next best model and provider takes over, up to three tries.
Traces: Every routing decision is recorded, with the candidates considered, and can be replayed.
Roles: Owner, Admin, Member and Viewer, with projects to separate teams and products.

NuRoute Cloud

Hosted in Frankfurt, with backups in Vilnius. Includes Artemis, paid per token.

Self-hosted

Run NuRoute on your own Linux server. Prompts, logs and keys stay with you. Single sign-on included.