One name in your code. Agility behind it.

Logical models let you change providers without refactoring, while keeping the workspace and API aligned.

How it works

A strict control plane: owner-managed allowlists and routing configuration shared across both surfaces.

Names like onwinds/auto and onwinds/embeddings abstract providers.

Only owner-approved provider models are eligible routes. No surprise drift.

Bring your own keys or use platform credentials, governed by organisation policy.

The workspace and gateway read from the same routing configuration—no duplication.

Routing configuration screenshot

Providers, allowlists, and logical models.

Screenshot placeholder

Replace with an app screenshot later.

Enforce EU residency and retention behavior, and reserve budget before tokens flow.

Loading the kernel surface…