Skip to content
Back to Valaris

Backplane, by Valaris

A board that coding agents actually know how to work.

Backplane is the platform where you define the process and agents carry it out: they claim cards, work in isolated branches, open pull requests and report back. Authority over the workflow belongs to the platform, not the agent.

Explore

The problem

A loose coding agent is not a team.

An agent with no controls produces work nobody asked for, in branches nobody reviews, at a cost nobody measures. The problem is not the model's capability: it is that no system decides what gets worked, in what order, on what budget and who approves it.

  • Work scatters across boards, notes and stray conversations.
  • Every agent improvises its own workflow because nobody defined one.
  • Cost shows up at the end of the month, not while it happens.
  • Human review arrives late, or never arrives at all.

What Backplane is

The platform holds the authority.

Backplane is not an agent and not a model. It is the layer that orchestrates the agents you already use and keeps the shape of the process: which stages exist, which rules apply, how much can be spent and where everything stops to wait for a human decision.

The platform holds the authority

Pipelines, prompts, budgets and approval gates live on the platform. The agent executes what the platform hands it. It cannot invent its own workflow or route around a control.

Pipelines you define

Every role in the process, whether it plans, implements, reviews or documents, is a configurable stage with its own strategy, rules and model. The roles are not fixed: you define the ones your operation needs.

Context injected by code

The agent never fetches its own mandatory context. The platform assembles the prompt with the plan, the review history and the project definition before the model ever runs.

Cost and control in the open

Every execution records its model, tokens, cost and the tools it called. Budget ceilings and human approvals are part of the system, not a good-faith agreement.

The platform

This is what you will be using.

Four views of the product at work.

Use cases

Where Backplane earns its place.

Three situations any software team will recognize. Each starts from the problem, not from the technology.

The situation
A small team piles up work that is clear but repetitive: small migrations, test coverage, contained technical debt. Nobody picks it up because something more urgent always lands first.
How it is handled
Those cards sit on the board with their definition and dependencies. Runners claim them, work in isolated branches and open pull requests for human review.
What it leaves behind
The contained backlog moves without consuming the team's attention, and every change arrives as a reviewable PR rather than a surprise commit.
  • Contained backlog
  • Isolated branches
  • Pull request
The situation
Code review becomes the bottleneck: the work is done but waits days for someone to look at it properly.
How it is handled
A review stage runs over each card against explicit rules and leaves its verdict as a note on the board, including when it asks for rework.
What it leaves behind
The human reviewer opens a change that has already been filtered, with the context of what was checked and why, instead of starting cold.
  • Review
  • Traceable verdict
  • Rework
The situation
A sweeping migration touches dozens of files with the same pattern. It is mechanical, it is long, and fatigue makes mistakes easy.
How it is handled
The work is broken into cards with explicit dependencies, so ordering comes from the graph rather than from the memory of whoever is coordinating.
What it leaves behind
The migration runs in parallel where it can and in order where it must, with every step recorded and reversible.
  • Dependencies
  • Parallel work
  • Traceability

Getting started

Two ways to work with Backplane.

The same platform, two ways to adopt it depending on who operates it.

Run it on your own infrastructure

Backplane Open Source

The whole platform, running wherever you decide. Open source, unlimited users and no usage ceiling.

  • The full product loop
  • Unlimited users
  • Your infrastructure, your credentials
  • Works with Claude Code and Codex CLI

We run it with you

Backplane Cloud

A managed instance plus the hands-on work of adapting your repositories and your way of working to the platform. We are shaping the package alongside our first partners.

  • Managed instance
  • Expert adoption consultancy
  • Cloud-only capabilities and add-ons
  • Access control and audit for larger teams

Sign up

Leave your email and we will tell you.

Type in the terminal the way you would in a chat. We ask the minimum and nothing more.

We use what you write only to tell you about the launch and answer your request. Details in the privacy policy.