Resources
Everything we wrote down so you don't have to work it out
Guides for the first fortnight, templates you can paste into your own board, comparisons we would rather you read before buying, and a walkthrough for the people who prefer watching.
Guides
Start here
Five walkthroughs, in the order most teams need them. Each one ends with something working rather than something understood.
Get your first request to production
Connect a repository, file one request, approve the plan, watch the tasks run on their own branches, and merge. The whole loop, once, on something small.
Read the guideChoose your autonomy level
What Manual, Supervised and Autonomous each change, what stays gated at every level, and the questions to answer honestly before you move up one.
Read the guideWrite a request that plans cleanly
Give the Project Manager an outcome, a constraint and a place to look. Includes worked examples of the same request written badly, then written well.
Read the guideConfigure a deployment target that can roll back
Set up the SSH host, deploy path, deploy command, health check, diagnostics command and rollback command — then break it on purpose to prove the rollback runs.
Read the guideAssemble a project team
Pick the specialists a project genuinely needs from the fourteen roles, decide which ones require human review, and see what capability substitution does with the gaps you leave.
Read the guideTemplates
Copy these rather than inventing them
Plain Markdown. Paste them into a request, a role contract or your own runbook and edit until they sound like your team.
Request templates for bugs, features and investigations
One structure per request type: what is happening, what should happen, where to look, and what must not change. The investigation template includes the fields a follow-up request needs to be useful.
Get the templatesA role contract template
The skeleton we use for our own roles: what this specialist owns, what it must escalate, where it must stop, and the shape of the report it hands back.
Get the templateA deploy runbook template
The commands, in order, with the failure branch written down beside each one. Fill it in before you connect the target, not after your first bad night.
Get the templateA health check checklist
Twelve questions that separate a check which proves your service works from one that proves your web server is answering the phone.
Get the checklistTeardowns & comparisons
What we are, next to what you are already considering
Written to be useful rather than flattering. Each one names the case where the other option is the better buy.
Capybari next to an AI coding assistant
An assistant speeds up the person in the chair. We are for the work that has to happen when nobody is in the chair: planning, review, deployment, the investigation afterwards. If you love your editor, keep it.
Read the comparisonCapybari next to hiring a contractor
Availability, context, review and what happens at 3am, compared honestly. A contractor who already knows your codebase is hard to beat; a contractor you have not hired yet is not.
Read the comparisonWhat a managed engineering organisation costs against staffing one
The roles a small team cannot justify hiring — QA, security, DevOps — priced against agent runs, with the method shown so you can put your own numbers in.
Read the teardownWatch
If you would rather see it move
The twelve-minute product walkthrough
One request, filed and shipped, with nothing cut. The plan, the approval, four tasks on four branches, the review gate, the deploy, the health check.
Request the recordingOffice hours recordings
Our engineers answer whatever turns up — usually autonomy, rollback and what to do with a plan you disagree with. Recorded and published afterwards.
Ask for an inviteWhich one
Pick by how much time you have
Four kinds of resource, four different jobs. Nothing here needs to be read in order.
| Resource type | Who it is for | How long it takes | What you end up with |
|---|---|---|---|
| Guides | Anyone in their first fortnight — technical or not | 10–25 minutes each | Something configured and working in your own project |
| Templates | Whoever files the requests and edits the role contracts | 5 minutes to copy, ongoing to refine | A house style for requests, contracts and runbooks |
| Teardowns & comparisons | The person deciding whether to buy | 9–14 minutes each | A straight answer, including where we are the wrong choice |
| Watch | Teams who want to see it before reading about it | 12–45 minutes | A clear picture of what the board looks like under load |
Looking for reference material rather than teaching material? That is the documentation.
Elsewhere
The rest of what we publish
Documentation
Reference for every part of the platform, from role contracts to deployment targets. Instructional, second person, no marketing.
Help centre
Answers to the questions support actually receives, plus how to reach a person when the answer is not there.
Community
Where teams compare role contracts, request patterns and health checks. We read it; we do not moderate it into silence.
Changelog
Dated, specific and honest about what is still missing. The roadmap covers what comes next.
The digest
Get told when a new resource lands
One email a month: new guides and templates, plus a short note on what shipped. One click to stop.
The first guide works better with a project open
Connect a repository, file the thing that has been on your list for a month, and read the plan. Manual autonomy — nothing runs without you.
No card required · Free plan forever · Export everything, any time