CoeOS
How CoeOS works
Section titled “How CoeOS works”CoeOS has two pieces: a client, where you work, and the CoeOS box, the router. The client ships no provider URL and no API key: it knows one address, the box’s. Every model call goes through it. There is therefore a single way out, governed, logged and tested.
No component holds a fixed model. Agents, workflows and memory all point to a
CoeOS meta-model. The box classifies each request on a competence axis (writing, law,
reasoning, code…) and sends it, whole and once, to the model that scores highest on that
axis on the TMB benchmark. Every answer names the axis, the model and the provider. You
choose the function, CoeOS chooses the model.
Three levels
Section titled “Three levels”The same client and the same box, at three levels. What changes: where confidential work goes, and what stays in the cloud. Everything is configurable.
- Open: the best open models, in the cloud. With no privacy constraint, through OpenRouter, at a fraction of the price of closed models; or with European providers under DPA and ZDR.
- Hybrid: confidential work goes to a model hosted on your premises; the rest keeps the power of the cloud.
- Local: everything stays on site.
In detail: the three levels.
Two ways to work
Section titled “Two ways to work”- The web app: chat, work on documents, review agents, team memory and the company knowledge base. Nothing to install.
- CoeOS Desktop: the agent on your machine, with full access to it, for macOS, Windows and Linux.
Both only talk to the box: same routing, same confidentiality rules, same memory split by class.
The pillars
Section titled “The pillars”- Agents: a main assistant that delegates to specialised sub-agents, under guardrails and allow-listed tools. Regulated reviews go through compartmentalised workflows with human validation.
- Confidentiality: one class per conversation, a lock, a table of safe models, a tamper-evident log.
- Memory: what the assistant remembers about you, and the company’s knowledge, split by class.