Skip to content
AnnouncementInitial release: self-hosted on Ubuntu 24.04 and 26.04 LTS. More platforms planned; Cloud and managed services are outside this release.First release: self-hosted on Ubuntu LTS.Release status
Register Cloud interest
BranchRunner Cloud

BranchRunner without the infrastructure work

The initial BranchRunner release is self-hosted only. Cloud is a future offering; the capabilities below describe its planned operating model and are not included in this release.

Future offering — outside the initial self-hosted release. The operating model below is planned, not a current service offer.

No payment or automatic renewal occurs through this page. Review the current pricing and availability information.

Future-interest process3 steps
01Register interestShare the operating needs that would matter to a future managed offering.
02Describe your prioritiesTell us about likely repository scale, data boundaries, and workflow needs without granting repository access.
03Follow future availabilitySubmitting interest creates no account, service commitment, support entitlement, or launch date.
No infrastructure to installYour provider credentialsSame product model as Community

What a future Cloud offering is intended to operate

Planned managed scope
·The control plane, its database and its backups
·Managed worker capacity, scaled to your plan's concurrency
·Docker runtime, mirrors and workspace storage
·Version upgrades and migrations
·Monitoring, patching and incident response
You keep
·Your model provider credentials and choice of agents
·Your Git provider authorization and repository scope
·Workflows, permissions, budgets and approval rules
·Every human decision in the loop
·The option to move to self-hosted at any time
Availability
Future offering; no current deployment
Capacity
Not yet offered
Data location
Not yet announced
Retention and backups
Not yet announced

Locations, retention, backups, support, capacity, pricing, and terms have not been offered or committed.

What is BranchRunner Cloud?

Cloud is a future managed offering outside the initial self-hosted release. No customer Cloud deployment exists today.

Can Cloud run in our environment?

No Cloud deployment is currently offered. The interest form records which repository, capacity, data-boundary, and workflow needs matter to potential users.

What controls remain with our team?

Your team retains repository authorization, model-provider choices, workflow permissions, budgets, and human approval decisions, as described in the published operating model.

What is included in Cloud?

No Cloud plan, pilot, capacity, support, location, backup policy, or commercial scope is currently offered.

How is Cloud usage measured?

The proposed billing dimensions are organization scope, concurrency, worker time, storage or retention, and optional managed usage; no public rates are asserted.

Concept diagram of responsibilities spanning an organization, BranchRunner, and external providers in a possible future Cloud model.
A product-direction diagram, not a current deployment, region, capacity, retention, backup, support, or availability commitment.

Included capabilities

The planned Cloud model is based on the same product direction as the self-hosted release. These rows describe intent, not a current service entitlement.

Durable tasks, runs and requirement ledgersPlanned
Multi-agent delegation and parallel worktreesPlanned
Isolated workspaces with preview environmentsPlanned
Validation, evidence and diff reviewPlanned
Approvals, budgets and the audit logPlanned
Single sign-onPlanned
SCIM provisioningEnterprise planned
Organization-wide policyEnterprise

Model credentials and data handling

You decide which provider sees which work. Two options, and the difference is explicit on the billing page as well as here.

Bring your own keysPlanned

The planned model uses your provider account, rate limits, and provider terms. Final managed-service handling has not been offered.

Managed model usagePlanned

Premium access to managed open-weight models remains a possible future capability.

Where your data sits
Data location
Not yet announced
Repositories
Handling model to be defined before any service offer
Evidence and audit logs
Retention model to be defined before any service offer
Backups
No managed backup commitment
Potential infrastructure provider
Customer-data providers

Plans and what affects the bill

Full pricing and comparison
Cloud
Future offeringNo managed service, capacity, or commercial terms are currently offered
No charge is made through this website.
Register Cloud interest
Future offering — outside the initial self-hosted release. The operating model below is planned, not a current service offer.
Dimensions that can affect your bill
Base subscriptionPer organization, per period
Included concurrencySimultaneous runs in the plan
Additional concurrencyAdded per slot when you need more
Managed worker timeBuild and execution minutes beyond the plan
Workspace storage and retentionLonger retention costs more

Cloud questions

Can I start Cloud from this website?

No. The initial release is self-hosted only. You can register interest in a future Cloud offering, but no service, timing, pricing, or terms are currently offered.

Will I be charged when I request access?

No. The form records future interest; it is not access, a trial, checkout, subscription, or automatic renewal.

Which model providers can I use?

Connect your own provider account and use supported frontier models from OpenAI, Anthropic, Google Gemini, Azure OpenAI, AWS Bedrock, OpenRouter, and OpenAI-compatible endpoints. Exact model availability depends on your provider account, region, and API access. Premium access to managed open-weight models is planned.

Where does Cloud run and where is data stored?

No Cloud deployment location has been announced. Any future location and data-handling model would be published before a service is offered.

How long is run data kept?

No managed retention or backup policy has been announced. Self-hosted operators control their own data lifecycle.

Can I move to self-hosted later?

Yes. Community is the same platform. Nothing is migrated automatically: you connect the repositories to your own deployment and re-import the work items you want to continue.

Does Cloud see my source code?

Managed workers clone your repositories to run the work, inside the isolated workspace for that run. The security page documents the data flows, retention and subprocessors.

How is concurrency counted?

By simultaneous runs. A run holds its worker slot for its whole life, including while it waits for approval. Additional concurrency can be added to a plan.

Register interest in a future Cloud offering

Tell us which operating needs matter to you. This creates no access, service promise, response commitment, or launch date.

Register Cloud interestReview Community requirements
Future offering — outside the initial self-hosted release. The operating model below is planned, not a current service offer.