Coding agents can write code. Organizations need orchestration to operate them.

BranchRunner is coding-agent orchestration software for engineering organizations. It coordinates agents, isolated workspaces, validation, approvals, and issue-to-pull-request evidence; it is not a coding model or IDE assistant.

Why we are building it

We were running several coding agents across a handful of repositories and kept solving the same problems with scripts: which agent has the checkout, where did that environment go, what was actually verified before this pull request opened, and who said yes.

Those are orchestration problems, not model problems. They do not get better with a larger context window. So we built the control plane we wanted: durable tasks, isolated workspaces, real validation, and human authority as a first-class state rather than a notification.

What we will not claim

No percentage productivity claims until customers measure them and let us publish the numbers.

No testimonials we wrote ourselves, and no logos we do not have permission to use.

No compliance badge before the certification exists. The status page lists what is planned as planned.

No claim that agents replace engineers. The product is built around the assumption that they do not.

How we build

Truthful availability first

We will publish the source and release artifacts when ready. The initial release is self-hosted on Ubuntu 24.04 and 26.04 LTS; Cloud, Enterprise services, and the VS Code extension are outside this release. Release validation is still in progress.

Provider-neutral

Roles come first and providers sit behind them, so you can change model vendor without changing how work is governed.

Evidence over assertion

An agent's claim is labelled as a claim until something independent confirms it. That rule shapes the whole interface.

Boring infrastructure

Docker, Git worktrees, PostgreSQL. No cluster requirement, no bespoke runtime to learn before the first run.

Honest about state

Failures name what broke, what was preserved and what to do next. Beta means beta; planned cannot be installed.

Humans keep authority

Approval, intervention and budgets are product surfaces. Autonomy is bounded on purpose, not by accident.

Company details

Legal entity

Savelkouls Ventures, LLC

Trading name

BranchRunner

Managing Partner

Brian Savelkouls

Potential future Cloud provider

Roborian, Inc.

Business address

800 N King Street, Suite 304-4197, Wilmington, Delaware 19801, United States

Delaware file number

10400146

Jurisdiction

Delaware, United States

Formed

November 12, 2025

VAT

Not applicable

BranchRunner is the trading name of the verified legal operator below. The published address is the company business and correspondence address, not its registered-agent address.

Where to go next

Brian SavelkoulsManaging Partner of Savelkouls Ventures, LLC; founder and CTO of Roborian, Inc.Future Cloud directionRoborian, Inc. may operate a future BranchRunner Cloud offering. No customer Cloud deployment or support service currently exists.Contact and salesSupport routes, sales, security and press.Self-managed operating modelReview the documented model and its current availability limits.How we think about thisEngineering writing and industry analysis.CareersOpen roles, when we have them.

Careers

We hire slowly and post roles when they are real. If you have operated agents at scale and have opinions about why it is hard, write to us anyway.

Introduce yourself

Press and brand

Brand assets are being finalized. Until then, please use the BranchRunner wordmark as written, one word with a capital B and R, and ask before altering it.

Press enquiries

Design partners

We work with a small number of teams in exchange for direct access to engineering. Results are published only with approval.

Become a design partner

Judge it by running it

The Community edition is the whole orchestration model. Read the source, run a task, then decide whether we are worth talking to.

Review Community requirements Talk to us