Did a human decide first?
Your agents act for you and your organization: they send the proposals, run the campaigns, handle the invoices, write the replies.
Gatewerk is where human judgment enters the pipeline, exactly where you choose. Review the exact payload, edit it, decide.
Four moments worth a human.
Before sending
Email drafts, support replies, Slack messages, candidate outreach, client proposals.
Before executing
Code deploys, database migrations, transactions, infra changes, third party API calls.
Before publishing
Blog posts, social content, product listings, docs updates, press releases, reports.
Before approving
Expense reports, refunds, access grants, contract terms, insurance claims, POs.
The reviewer can be your team, or a client deciding by link with no account.
Between the moments, agents bring you the judgment calls: classify the edge case, pick the path, resolve the exception. Your answer returns typed, and the process continues.
One endpoint stands between the agent and the action.
Your agent submits work for review: a template slug and a payload. Two fields.
A human reads the actual payload in a structured form and fixes what needs fixing.
The decision returns over a signed webhook. The audit row is already written.
Integrate in minutes, not weeks.
Protocol first, not framework specific. Your agent already makes HTTP calls or speaks MCP. That is all you need.
Machine readable everywhere: llms.txt, OpenAPI, self describing MCP tools.
Do one thing well. Compose with everything.
An interrupt pauses one workflow inside one framework. Gatewerk is the review layer across all of them: one inbox, one record, any stack.
Primitives, not opinions
Gatewerk fires events and exposes an API. You wire it to Telegram, Slack, or your own service and decide what gets reviewed. A notification channel is a settings entry, not a project. No workflow is baked in.
Strength in the substrate
The guarantees hold at the database and worker layer, not by convention. They stay invisible until the moment they save you.
Open protocol, your infrastructure
Built on the Human Review Protocol. Self hosted, AGPL, no vendor lock in, no feature behind a sales call.
Built once, properly, so you don't have to build the fourth dashboard.
Three layers. One loop.
An open specification at the base, a complete station in the middle, optional managed hosting on top. Every review runs the same four step loop, whichever layer you deploy.
Managed hosting, teams, compliance. Everything below, run for you.
The engine, review UI, SDKs, and integrations. The whole product, self hosted.
The Human Review Protocol. How agents request review, how humans respond, how decisions flow back.
Built for production oversight.
Exactly one decision
Two reviewers can race. Exactly one decision lands; everyone else sees it settled. No double approves, no lost edits.
Tamper evident audit
Every decision lands in an HMAC chained log. History cannot be quietly rewritten, not even by whoever holds the database.
Seatless external review
Send a review link to a client or stakeholder. They decide. No account, no seat, no login wall.
Zero feature walls
Self host runs the entire product. No feature behind a sales call.
Escalation, not silence
If a review sits undecided, it escalates on a timer to the next person, and expiry notifies the agent. Silence never strands a workflow.
Replay safe webhooks
Decisions arrive HMAC signed with a replay safe scheme and stable delivery ids. A replayed delivery cannot become a second action.