How we build DueReason
This product is built by AI agents. Every start of work and every merge needs an approval in DueReason; the merge bot verifies the signed grant before it merges. We use what we sell, on our own code, every day.
How a change reaches production
- Proposal — An idea for a change -- ours or an agent's -- becomes a card. It waits for a person.
- Approval — A person approves the work to start, in DueReason, bound to exactly what the card says.
- Worker — An AI agent picks up the approved card, writes the change in its own branch, and runs the full test suite locally before anyone else sees it.
- Pull request — The agent pushes the branch and opens a pull request, already passing the same checks the main branch requires.
- Merge approval — The agent asks DueReason for a written approval to merge this exact commit, with the diff, the risk and how to roll it back.
- Grant verification — Once approved, a small service verifies the signed grant is for this exact commit before it ever touches the main branch.
- Merge — Only then does it merge. A public, verifiable receipt proves the approval and the grant matched -- the same receipt our customers get for their own decisions.
From our own use
- Approvals processed through DueReason
- 852
- Share covered by a mandate, approved instantly
- 51%
- Median time to a decision
- Under 1 minute
- Merges to the main branch through this loop
- 433
A dated, static snapshot, not a live counter: a person reviews the numbers before they are published here. As of 9 November 2026, covering our dogfooding loop since 18 October 2026. The exact query behind each one is public in our repository (docs/duereason/case-study-numbers.md).
Start with DueReason
Create a free account, try it live, or talk to us about your workflow.