R&D lab

Bring us a hard problem.
We’ll work on it with you.

Some work takes months, not days: modernising legacy code, security work, and experiments in robotics, vision models, machine learning and space. Our R&D floor takes it on with you, in the open or behind closed doors.

In the open, or
behind closed doors.

You choose how visible the work is. The rigour is the same either way.

In the open

We run the work as a public experiment.

The plan is written down and frozen before we start. The results are published, including the ones that do not go our way, and the code is released as open source. Anyone can check the work, and your name can be on it.

  • A written plan, published before the work starts
  • Results published as they come out, good or bad
  • Open-source code under a licence we agree together
  • Credit for your team, if you want it

Behind closed doors

Private, confidential work.

We work in your repositories and on your infrastructure, and nothing is published unless you decide to. Confidentiality and who owns the results are agreed in the proposal. The method is the same: a written plan, checks that run, and evidence you can inspect.

  • Confidentiality agreed before we go into detail
  • Work in your own repositories and infrastructure
  • Nothing published without your sign-off
  • The same written plan, checks and evidence

What we
take on.

Four kinds of work, each with a way to check the result.

01

Legacy code

Old systems that still run the business. We work out what the code actually does, pin that behaviour down with checks, and then refactor in small steps that are each verified against the old behaviour.

See the migration witness demo
02

Security

Reviews of code, access and infrastructure, followed by fixes that land with tests. Where it makes sense, the checks go into your pipeline so they keep running on every change.

How we handle controls
03

Frontier experiments

Robotics, vision models, machine learning and space: questions where nobody knows the answer yet. We design the experiment, build the prototype and measure what happens, so you decide on results rather than on hope.

Browse our public experiments
04

Blueprints

Your architecture rules, written down as code. Set up as a CI gate, our open-source Blueprint Conformance Engine fails the check when it detects a breach of a supported rule, so the rule doesn’t depend on a reviewer remembering it.

Read about the engine

How an
engagement runs.

Engagements run over months. We scope them together and agree each one by proposal, so there is no price list here.

  1. 01

    A conversation

    What you want to find out, build or fix, and whether the work should run in the open or behind closed doors.

  2. 02

    A written proposal

    Scope, plan, what counts as done and how we will measure it. You see it before anything starts.

  3. 03

    Work in cycles

    We work in cycles agreed in the proposal. Each cycle ends with something you can run or check, and a decision about the next one.

  4. 04

    Results you can use

    Code, evidence and documentation, handed over as agreed in the proposal. In the open, the results are published as well.

Tell us what you
want to work on.

Start a conversation

Prefer a shorter, fixed-price start? See the AI Innovation Sprint.