An organizational
brain. Built to act.

Business teams plan and inspect in Command Center. Engineers and agents build in Code Server, connected by work orders.

Command Center

Business + team leads + agents

Work orderImprove supplier
onboarding.
Plan
Scope + intended result
Inspect
Progress + evidence

Business teams follow the work without entering Code Server.

Work
orders
Progress
+ evidence

Code Server

Engineersagents

Agents + engineers notifiedAgents build.
Engineers guide.
+ supplier review step
Return for inspectionWork + checks

Small team? The same people can use both.

Control Tower

Odin’s operator console · not yet available to customers
  • Usage + token cost
  • Audit
  • Security
  • Ecosystem health
Command CenterCommand CenterCommand Center
Illustrative operating model. Connections and controls depend on setup.

Intelligence, context, action.
See how they come together.

Follow a piece of agent work, then explore the model access, project oversight and sourced knowledge around it.
Compare the products

HarnessIllustrative product preview

Give intelligence a process.

Harness connects a model to scoped work, tools and evidence.

Harness

Your mission

Supplier review workflow

Add a review step. Preserve existing access rules.

One repositoryNo deployment

Odin Harness

The structure around your model

ContextRepository + mission
Working memoryCurrent task

Scoped work. Inspectable actions.

Work to review

Change + evidence
Review step added
Existing approval ownerPreserved

Test result not attached

The change returns with evidence to inspect. A person decides what happens next.

Same Harness. Your choice of intelligence.

Illustrative model families. Available choices depend on your connected tools and configuration.

Inspect the model, skills + guards, or tools to see what each contributes.

Model choice is not a jurisdiction setting.

Explore how a Mistral model and a configured Gateway route work together.

The handoff stays human.

Inspect the change and its evidence.
Preparing a packet is not a release.

Release authority stays human

Attach the missing example result to prepare the review packet.

Look under the hood

The model supplies intelligence. Harness connects the mission, context, working memory, workflow skills, action guards and tools. Existing access rules stay in place.

Guards are not instructions the model is hoped to follow. Each one is a reviewed registry entry compiled into the agent runtime's own pre-action checks for the tools it covers, and the same registry is compiled for more than one agent runtime. A guard that cannot reach a verdict denies the action.

This example illustrates a scoped repository change; no work or tests run here. Working memory supports the current task. Odin Next is separate organizational knowledge. Preparing the illustrative packet neither deploys a change nor grants release permission.

Model identity, deployment location and routing policy are separate choices. The EU example pairs Mistral with a configured EU-jurisdiction route through Odin AI Gateway. An eligible EU-broker route also requires the applicable provider agreement and DPA attestation; choosing Mistral alone does not set processing location.

In Gateway, a residency setting is configured on the access key. Once Gateway has validated that key configuration, the setting applies to the routed model requests made with it, including requests that name a specific model. A request can tighten that setting but never loosen it. If no eligible route can serve the request, Gateway refuses it instead of sending it elsewhere. Unless the key records a DPA attestation for the EU broker, an EU-jurisdiction key narrows to operator-controlled EU routes only. The policy follows the route, whichever model family it serves.

Model names identify illustrative families, not a promise of availability or a provider endorsement. This local preview does not switch a live model, configure a provider, or send a request.

Harness mechanism story selected.

Give an agent a written task with clear limits. Guards block prohibited actions, and the result comes back with evidence for a person to review.

Explore Harness

Illustrative product previews. No live work runs here.

From a useful idea
to work your team can use.

Choose a result
worth building.

One recurring task. Clear inputs. A result your team can check.

Supplier onboarding
Task
Add a review step.
Inputs
Workflow brief + review notes
Outcome
A change to inspect

Illustrative workflow. Fictional example; no agent work runs here.

Explore an Innovation SprintCompare the session formats and published prices.Implementation with your team Inspect a worked example

What we learn,
we put to the test.

Our research makes the methods, results and limits inspectable. BCE turns declared engineering intent into executable checks.

Inside Odin Research

Blueprint Conformance Engine

Declared intentExecutable rule
Clean fixture · passViolating fixture · fail
Inspect the public source

New on the R&D floor.

The latest experiments, results and notes we have published.

  1. ResultsKill the database mid-session, does anyone notice?Single host: MongoDB fits four write-outage and two acknowledgement-gap scenarios; PostgreSQL two by feed gate. No acknowledged writes lost; no overall winner. Strict-ack and disturbance uncertainties remain.
  2. AmendmentKill the database mid-session, does anyone notice?The counted run is complete: 48 discards reconciled; strict acknowledgements and one disturbance window remain unresolved.
  3. AmendmentMongoDB on its home ground: where does it fit Odin?
Everything on the R&D site

When the answer
needs research.

Legacy code, security, vision and machine learning. Bring our R&D lab a question worth investigating, in the open or in confidence.

Work with our R&D lab

What could your
team do next?

Bring a piece of work. Let’s see what AI can make possible.

Explore the controls and limits
Build with Odin