Enterprise · AI developers for your GitHub organisation

Your trusted partner for the software your business runs on

Our AI developers work around the clock on your own machines, use your own model keys, and merge only when the rules in your repository allow it. Every action is written to an audit log that is never edited afterwards, and access is by invitation only.

Request access Talk to us

We run the software side of your business.

No hiring rounds: Describe the work and the work starts.
Onboarded once: Every AI dev inherits your repository's rules, specialist roles and code map.
Consistent senior-level output: The same review and CI gates, Tuesday morning or Sunday night.

01The boundary

Your machines. Your keys. Your rules.

We sell orchestration, judgement and the trail. We never resell inference, and we never run the coding agent on our own hardware, on any plan.

You ownYour boxes

The machines, the keys and the policy

Where it runs: Your own VMs. The runner dials out to the control plane and opens no inbound port.
When it runs: Round the clock. It pulls the next task and streams every event back while you sleep.
Whose model keys: Yours. Every supported provider, plus any OpenAI-compatible endpoint. We never resell tokens.
Who sets the merge policy: Your own .dz/maintainer/maintainer.yml. Turn auto-merge off, or route a lane through a human, and that is the policy.
Who ships to production: Your own pipeline, after the merge. We do not operate your deploy.

We ownOur servers

Orchestration, judgement and the record

Who decides a merge: One gated merge call. The gate is re-asserted on a fresh read, bound to the commit it validated, and every refusal is a named code.
The record: Append-only and tamper-evident: each row carries the hash of the row before it, so a gap is visible.
Other bots: CodeRabbit, Copilot, Dependabot and Renovate are never answered: no bot argues with a bot. A Dependabot or Renovate bump is still work, reviewed and merged through the gate.

The line between what you own and what we are accountable for.

You bring · 01
Access
Repos, APIs, MCP servers and servers. Scoped credentials you can revoke in one move.
You bring · 02
VMs
The boxes the fleet runs on. Developers that do not sleep, on hardware you already pay for.
You bring · 03
AI tokens
BYOK across every supported provider, plus any OpenAI-compatible endpoint.

02Procurement

What your reviewer asks, answered in order

Some of this is built and some of it is not. Each row says which, because you find out either way.

Single sign on

Enterprise SSO routed by your verified email domain. It signs in people who already hold an account in your organisation.

How SSO works

Directory provisioning

Planned

SCIM is on the roadmap and not built. Until it ships, the account exists in your organisation before its owner can sign in, and a sign in with no account behind it is refused and recorded.

Service levels

Planned

We will not quote an availability target we have not signed. The service levels page gets written when there is one to publish.

Data processing terms

For the personal data we process on your behalf, you are the controller and we are the processor, acting on the instructions your installation and your policy file express. The addendum names the subprocessors and the transfer safeguards.

Read the data processing addendum

Before it goes to legal

The document behind every line above

Security and trust
The App scopes, BYOK, secrets at rest and the audit log, each linked to what documents it.
Data Processing Addendum
Roles of the parties, subprocessors, security measures and international transfers.
Security reference
The exact GitHub scopes, the encryption scheme, the audit log fields and how to report a vulnerability.
The policy file
Every switch your repository sets, including turning auto merge off and routing a lane through a person.
Privacy policy
What personal data we handle when you use the App, and on what basis.
Seats and terms
What a seat costs and what Enterprise includes.