Architecture
You decide the direction. We do the architecture pass.
Read each request. Write down what happens next: a plan, or the reason it stops. Your rules set the limits, and the work stays inside them.
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.
What you can read before any code exists
A write-up of your repository
We read your repository and write down how it works: its rules, its commands, and a small set of specialists for it. It comes as a pull request, so you can edit or remove any of it.
A written plan
What you ask for becomes one written plan, kept as its own record. Open it to see how the work was shaped before any code was written.
A yes or no, with the reason
Every request gets one answer: it goes ahead as work, or it stops with the reason written down. If something interrupts it, the answer is reached again. You still see one.
You decide. We deliver.
The architecture pass is work, not authority. What may be touched, which checks have to pass, which lane keeps a human and whether anything merges without you are all written in your own maintainer.yml, versioned in your repository and read on every run. Change it and the next pass happens inside the new boundary. Nothing here overrules a decision you have already made, and nothing merges outside your rules.
Event flow
From a webhook to a merge
A webhook from GitHub, or any connected source on its own signed lane, is verified at ingest and put on the queue. Our workers judge it, and the next ready task is claimed for an idle box of yours, where an AI dev writes the pull request. Checks and review report on the pull request, and the merge gate passes it under your policy.
- an event in flight
- merged on GitHub
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.
The machines, the keys and the policy
- Your own VMs. The runner dials out to the control plane and opens no inbound port.
- Round the clock. It pulls the next task and streams every event back while you sleep.
- Yours. Every supported provider, plus any OpenAI-compatible endpoint. We never resell tokens.
- Your own .dz/maintainer/maintainer.yml. Turn auto-merge off, or route a lane through a human, and that is the policy.
- Your own pipeline, after the merge. We do not operate your deploy.
Orchestration, judgement and the record
- 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.
- Append-only and tamper-evident: each row carries the hash of the row before it, so a gap is visible.
- 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.
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.
What we do not do
We do not deploy your software
Your own pipeline ships the merge, exactly as it does today. What we record is the verdict your deployment reports back, and putting anything into your production stays a decision you take with your own tools.
UI and UX are planned, not built
The roster of jobs a run can be doing is a closed list, and there is no design role on it. Until there is, nothing on this site sells you a visual design pass.
The code is written on your machines, with your keys
We stay a thin orchestrator: the pass settles the shape, and your AI devs do the writing on your own box, under your own keys. We never run that work on our hardware, on any plan.
Read next
- The whole run
Every stage from the ask to the merge, one at a time.
- The AI devs
Which job each one does, and which one it never does.
- Your stack
How a repository is recognised, and what recognition actually buys.
- The policy file
Every boundary and gate this page hands you, in the file that holds them.
Ship more. Maintain less.
We expect software to be written faster than any team can review it. Bring your repos, your boxes and your keys. We bring the org that keeps up.