OdinLabsTalk to Odin
Menu

We set Odin up
with your team.

From a first experiment to a full setup. We work in your repositories and tools, next to your people, and leave you with something your team can run and check on its own.

Discuss your workflow

The easiest
way to start.

Start with a 1:1 session for a concrete next step on your question. To build and validate a workflow on your own material, choose a one-day Kickstart for one to three people, a two-day team sprint at your office or a team off-site at our venue.

See the options and prices

Bring a real piece of work.

An existing process. A recurring question. A change you want to deliver.

Understand

Agree on the problem, the context and the boundaries: which repository, which data, who reviews the result.

Build

Connect the tools you need, write the work order and run the workflow against your own material.

Review

Inspect the change and its evidence together, then decide what is worth taking forward.

What we
set up.

We scope each engagement with you first: the systems, the people and the controls involved. Here is what we set up in each area.

Model access & integration

Connect your applications and developer tools to AI Gateway through its OpenAI-compatible API, usually by changing a base URL and key.

  • A key for each person or application, stored only as a hash
  • A default routing profile for each key (quality, balanced or cost). Individual requests can pick a profile or a specific permitted model
  • A residency policy for each key’s chat completions, including EU-only
  • Budgets, with usage broken down by person, model and application in Command Center
Explore AI Gateway

Agent workflows

Bring agent-assisted engineering into your existing repositories and review practices.

  • Work orders with an objective, explicit scope, success criteria and a definition of done
  • Harness workflow skills and action guards for Claude Code or Codex
  • For agent runs on Odin’s own execution integration, sandboxed execution when a sandbox is configured and reachable (otherwise a local process with a filtered environment), plus a scope enforcer for paths and commands where the integration supports it
  • A review and release path in which people keep release authority
Explore Harness

Organizational knowledge

Choose the sources worth trusting, then make them answerable.

  • Ingestion that scans for secrets and records where each item came from
  • Questions answered from retrieved sources with citations, or an explicit “no grounded answer” when retrieval finds too little
  • Saved memory that records why it was kept, who owns it and what depends on it
  • Odin Next enabled and configured for your workspace
Explore Odin Next

Team enablement

Your team learns by doing real work with us.

  • Your team writes and reviews work orders alongside us
  • Clear responsibilities for review, release and budgets
  • Command Center set up so the team can follow sessions and inspect results
Discuss your team

What you
keep.

A 1:1 session gives you a concrete next step. For a Kickstart or team sprint, the handover includes the working workflow, setup and evidence below.

01

A working workflow

Running in your own repositories and tools, on real work rather than a demo.

02

A documented setup

Keys, routing profiles, residency policies, budgets and guards, written down where your team can find them.

03

An evidence trail

Work orders, sessions and review records you can inspect after we have gone.

04

A decision on the next step

What to extend, what to stop and who owns it.

Longer work,
with our R&D lab.

For work that runs over months, such as untangling legacy code, security work or experiments in robotics, vision models, machine learning and space, our R&D lab works with you in the open or behind closed doors. Scoped together, by proposal.

Work with our R&D lab

Tell us what
you want to change.

Start a conversation