Agents act. You stay in charge.
Gatehouse sits between the agent and your systems.
Every action clears your rules first. The hard calls wait for one name. The record seals itself.
Surehand built it. Every deployment we run sits on it.
One worked example runs through these pages. The screens are simulated, the figures are invented, and each one says so.
- 5 gatesscope, role, limits, review, seal
- 1 namefor the hard calls
- 2 namesto override a block
- SHA-256chains each record, so an edit shows
Follow one payment.
One invoice, from the moment it lands to the moment the record seals. Five steps. At each one, the screen your team would see.
- [ 01 arrives ]
The invoice lands. The rules are already there.
Your rules are signed before the first invoice arrives. Which systems the agent may touch, which role it acts in, what it may spend, who signs the hard calls.
And the default: anything the file does not name is refused.
This invoice is for 2,400.00. It matches its purchase order and its goods receipt. One thing is different from last month: the supplier's bank detail.
/ fig. 02The invoice as it arrives. One field changed. Simulated. - [ 02 checked ]
Every step clears the rules before it runs.
Reading the invoice, matching the order, drafting the note to the supplier, scheduling the payment. Each one is checked against the signed rules as it happens. Each one passes.
Then the payment. The bank detail was first seen today, and your rules say a changed bank detail holds.
The payment stops before it reaches your bank portal. Not a review afterwards. A check in the path.
/ fig. 03Three actions pass, one is held. The rule that fired, expanded. Simulated. - [ 03 decided ]
The hard call goes to one name.
Not a shared inbox. Your AP lead, named in the rules. The evidence is gathered before they are asked: the invoice, the order and receipt, the bank detail on file and the one first seen today.
They decline it. The supplier had not confirmed the change. Their reason goes on the record with their name and the time.
Overriding a block takes two names. Both are saved beside the rule.
/ fig. 04The case as the approver sees it. Evidence, then the ask, then the decision. Simulated. - [ 04 sealed ]
The record seals itself. Try to change it.
Every event, in the order it happened, written while it happened. Each record holds the digest of the one before it. At the close, the run is sealed.
Change any field below and the chain breaks from that record on. Your team can run the same check on its own side, without Gatehouse installed.
Your AP lead's decision does one more thing. It becomes a labelled example, and the next change to a model, a prompt or a rule is replayed against it.
- record 01CHECKING
prev 000000000000
sha256 ············
- record 02CHECKING
prev ············
sha256 ············
- record 03CHECKING
prev ············
sha256 ············
- record 04CHECKING
prev ············
sha256 ············
Computing SHA-256 in your browser.
/ fig. 05Four records, hashed live in your browser. Edit any field and watch. Simulated records, real SHA-256. - [ 05 yours ]
Leave with everything.
The record, the history of your rules and the examples export in open formats. They read without Gatehouse.
Ask about this payment in a year and the run replays from the record: same inputs, same version of the rules, same outcome.
If you stop using Gatehouse, you keep all of it.
/ fig. 06One export. The run, the rules it used, the example it left. Simulated.
Everything between the agent and your systems.
Seven parts. Each has its own page, so you can send a reviewer only the one they asked about.
- 01The rulesYour rules, in one signed file.
- 02The checkEvery action clears the rules before it runs.
- 03The approverHard calls go to one name. Overrides take two.
- 04The limitThe limit lives in the rules, not in a spreadsheet.
- 05The examplesEvery decision becomes a test.
- 06The recordDon't take our word for it. Read the record.
- 07The exportLeave with everything.
Don't trust us. Test it.
Five things your reviewer can open today. No call needed.
- 01The recordOne run, six events, exactly as sealed.
- 02The rulesFive gates, signed, versioned.
- 03The chainChange one field. Watch the chain break.
- 04The exportRecord, rules and examples. Open formats. No Gatehouse needed to read them.
- 05The answersTwelve questions to ask any AI vendor, answered in writing.
No SOC 2, no ISO 27001 today. See what is in place, and what is not yet.
Built by the people who run it.
Surehand deploys and runs governed agents for clients. Every deployment sits on Gatehouse.
Teardown
We measure one process with you. You keep the document.
Deployment
We write the rules with your team. You sign them. The agent runs under them.
Operation
We read the same record you read. It exports in open formats and reads without us.
What buyers ask first.
Not here? Write to support@surehand.io. A person replies, usually inside two business days.
Book a walkthrough
What is Gatehouse?
Software that sits between an AI agent and the systems it works in. Before the agent acts, Gatehouse checks the action against rules your team has signed. Hard calls wait for a named person. Every action, hold and decision goes into a sealed record. Surehand built it and runs every deployment on it.
Who is it for?
Teams that want agents doing real work, like paying invoices or sorting claims, and need security, compliance and finance to agree first. If nobody will ever ask you to prove what an agent did, you probably do not need it.
What happens when a rule holds an action?
The run pauses and the case goes to one named approver, not a shared inbox. The evidence is gathered before they are asked. Their decision and their reason are saved with their name.
Can someone override a block?
Yes, but not alone. Overriding a block takes two names. Both are saved with the override, next to the rule it overrode.
Are the screens and cases real?
The screens are simulated and the payment you follow is a worked example. The three cases on the Deployments page are composites of client work, with names and figures changed. No customer data appears anywhere on this site.
Bring us the queue nobody wants.
A teardown measures one process, and you keep the document. A walkthrough is 30 minutes on Gatehouse, no slides. We bring the rules and the sealed record of one held payment. You bring one live process and your reviewers' questions.
support@surehand.io