Beta: every feature is free of charge while we test
Approval workflows for teams, pipelines and AI agents
Your team — and your agents — ask. The right people decide. The record proves it.
DueReason routes spend, access and sign-off requests to the people who must approve them, captures their reason or attachment, and keeps a tamper-evident record. Built for people, pipelines and AI agents alike — REST API, SDK, MCP server and GitHub Action included.
REST API, TypeScript SDK, MCP server and GitHub Action. Hosted in the EU.
Approvals /apr_0192f3c8a1
Approved
Pay invoice INV-2026-118
payment · EUR 6,800 to ACME sp. z o.o.
What will be executed
- amount
- 6800
- currency
- EUR
- payee
- ACME sp. z o.o.
- purpose
- Invoice INV-2026-118
Payload hash (SHA-256) b41c09e7d25a4f3e8c61a0f9e2d7b3c45a1e6f08d9c2b7a4e3f1d60c8b5a9e27
Approval steps
- 09:12
Requested by ap-agent
Reason: due on 10 October, matches PO-77
- 09:31
Finance approved, with the invoice
Ana Nowak · invoice.pdf, its sha256 on the ledger
- 10:04
Management approved
A second person, required from 5,000 up
- 10:04
Signed grant issued
Bound to the payload hash, single-use, valid for an hour
- —
Waiting for the payment system
It verifies the grant, pays, then reports back
How it works
DueReason never carries out the action and never holds your payment or deploy credentials. It settles whether the action may happen, and keeps the proof.
- 1
The system asks first, with a reason
An agent, pipeline or service sends the action, the exact payload and why. A request that no workflow covers is refused, never waved through.
- 2
Your workflow picks the people
Conditions on the payload decide: payments of 5,000 and over go to Finance, then management; production deploys to an engineering lead, then security. Steps run in order, a person counts once, and nobody approves their own request.
- 3
People decide with evidence
Each step asks for what you require: one click, a written reason, a photo or a document. Approvers see the payload exactly as it will run, and the agent's reason apart from it. One rejection stops the action.
- 4
The executing system checks the grant
Approval returns a grant signed with your organization's key and bound to the payload's hash. The system that acts verifies it against your published keys, so a changed amount or payee is refused, and each grant is used once.
What teams route through DueReason
These are approval chains teams can set up with the same mechanism: route the request to the right people, in order, with the evidence you need.
Payments and refunds
Internal control
An agent or a person asks to pay an invoice or issue a refund. Under 100 goes through, up to 4,999 needs Finance, and 5,000 and over needs Finance with the invoice, then management.
Segregation of duties: nobody pays out money without a second person looking at it first.
Purchase requests with a quote
Procurement
A requester attaches a vendor quote; Finance approves under a threshold, Finance and management above it.
The same threshold-based routing as payments, for spend that hasn't happened yet.
Vendor onboarding
Procurement
A new vendor is checked by Procurement before onboarding, with a written justification; vendors at 10,000 and over in estimated annual spend also need Management sign-off with their registration document.
Keeps new supplier relationships, payment terms and tax details out of one person's hands.
Discount exceptions
Pricing governance
A discount outside the standard price list is approved by a sales manager; 25% and over also needs sales leadership to sign off.
Internal pricing governance: a steep discount needs more than one set of eyes.
Production deployments
Change management
A pipeline or a coding agent asks before deploying to production: an engineering lead with a written reason, then security. Staging goes through.
Good practice anywhere a mistake in production is expensive to undo.
Account and access actions
Access governance
Restricting, suspending or revoking someone's account or system access is decided by people: two reviewers for a revocation, one for a restriction or suspension.
Keeps IT offboarding and access changes out of one person's hands.
Data access, export and deletion requests
Data governance
A request to access, export or delete someone's data is checked by a data owner with a written justification; a deletion request also goes to Security.
Evidence for a data-subject or data-governance request, however your organization is obliged to handle one.
Content and publication sign-off
Editorial sign-off
Before a post, release or public statement goes out, a content lead approves it; anything making a legal or financial claim also goes to Legal.
Catches a costly claim before it's public, not after.
Contract sign-off
Contract governance
Before a contract with a client or vendor is signed, an account lead approves the draft with a written reason; contracts of 10,000 and over also need Legal with the draft.
A larger contract doesn't get signed without a second, legal set of eyes.
Hiring offers
Compensation governance
A hiring manager proposes a role, level and salary; HR confirms it fits the band, and an offer outside the band also goes to an executive.
A record of who signed off on the offer and why, before it reaches the candidate.
Policy and hiring exceptions
HR and policy
A manager asks for an exception to policy, or proposes a salary or level; HR or Finance approves it with a written reason.
A record of who approved the exception and why, not just that it happened.
For developers
Anything that can send an HTTP request can ask. Agents, scripts and pipelines get ready-made clients.
- REST API
/api/v1/approvals - Create, read, wait for and cancel requests, report executions and verify grants. An OpenAPI description, idempotency keys and signed webhooks.
- TypeScript SDK
@duereason/sdk - requestApproval, waitForApproval and verifyGrant, which checks a grant against your organization's published keys. No runtime dependencies.
- MCP server
@duereason/mcp - For Claude, Cursor and other MCP clients. Its tools tell the model not to act until a request is approved, and to hand the grant to whatever executes.
- GitHub Action(coming soon -- duereason/approve@v1 isn't resolvable as an action yet)
duereason/approve@v1 - Holds a deploy job until the right people approve, then passes the grant to the next step. Rejection or expiry fails the job.
- Agent gate
duereason-gate - A policy that blocks an agent's own shell, write and MCP calls until a request is approved, then hands back a signed grant. Real adapters ship for Claude Code, Cursor, Hermes, OpenCode, Codex, Gemini CLI, Windsurf, git hooks and a standalone MCP proxy.
Stop AI agents from deploying, paying or deleting without approval
agent.ts
import { createClient, verifyGrant } from "@duereason/sdk";
// The agent asks, then waits for people to decide
const duereason = createClient({ apiKey: process.env.DUEREASON_API_KEY });
const payload = {
amount: 6800,
currency: "EUR",
payee: "ACME sp. z o.o.",
purpose: "Invoice INV-2026-118",
};
const request = await duereason.requestApproval({
action: "payment",
title: "Pay invoice INV-2026-118",
reason: "Due to the reason of: invoice due 10 October, matches PO-77.",
payload,
});
const decided = await duereason.waitForApproval(request.id, {
timeoutMs: 60 * 60 * 1000,
});
if (decided.status !== "approved") {
throw new Error(`Not paying: the request is ${decided.status}`);
}
// The payment system checks the grant against this exact payload, then pays
const { grant } = decided;
const claims = await verifyGrant({
grant, payload, organization: "acme", action: "payment",
});
await bank.transfer(payload);
await duereason.reportExecution(claims.sub, { grant, outcome: "succeeded" });Evidence an auditor can check
Built to show what happened, not only to say it.
Append-only and hash-chained
Each event carries the hash of the one before it, and the sha256 of every evidence file. A scheduled check re-verifies the chain and raises an alert on any break.
Grants bound to the payload
Ed25519 signatures, keys you can rotate and a public JWKS. A grant names the action, the approvers and the payload's hash, expires an hour after approval at the latest and is single-use.
EU hosting, pseudonymous by default
EU hosting by default, or self-host on your own infrastructure. Requesters and approvers are referenced by your own pseudonymous ID; contact details are optional and can be erased without breaking the ledger.
Tooling, not legal advice
You remain the decision-maker and the controller. We work alongside your lawyers, not instead of them.
Pricing
DueReason is in beta: every feature is free of charge for every organization. The prices below apply after the beta. We will email you at least 30 days before it ends, and nothing is charged unless you then choose a plan.
ApprovalsStart here
Free during the beta
from EUR 300
per month after the beta
The pilot price for your first workflow. Wider use is priced with you once the volume is known.
Human approval for what your agents, pipelines and services want to do.
- Actions, workflows, approver groups and 10 templates
- Evidence as a written reason, a photo or a document
- Signed grants your executing systems verify
- REST API, TypeScript SDK, MCP server and GitHub Action(coming soon -- not resolvable as uses: duereason/approve@v1 yet)
- Hash-chained ledger, signed webhooks and an audit log
Custom workflows
Free during the beta
Agreed with you
by workflow and volume
We agree the scope and price with you, starting with a pilot.
For larger teams that need multi-step approval workflows built around how they work, self-hosted or in our cloud.
- Multi-step workflows with attachments, set up with your team
- Approver groups and evidence requirements tailored to your organization
- Everything in Approvals
Prices in EUR. Polish customers are invoiced in PLN at the day's exchange rate.
Before an agent does something that matters, it asks a person
Create an account, install a template, add people to its groups and send your first request from an agent, a script or a pipeline.