Gatehouse
Gatehouse is the control plane for enterprise AI agents. It checks each action against a signed manifest, sends the cases that need judgment to one named approver and seals a record of each run. Surehand built it, and each deployment we run uses it.
- 5 gatesscope, role, limits, review, seal
- 1 named approverfor the hard calls
- 2 namesto override a block
- SHA-256chains each record, so an edit shows
We built Gatehouse so a client's reviewers can check what an agent did. Each deployment we run goes through it, and each run leaves a sealed record your team can read.
Each deployment runs under one signed manifest.
The manifest is versioned like code, and its five sections are the five gates. Below is manifest v14, which the simulated run on this page used.
Anything the manifest does not name is refused, and the refusal is recorded.
How the policy engine reads itINV-40218, held and declined.
Invoice INV-40218 for 2,400.00 matches its purchase order and goods receipt. The bank detail was first seen today, so the payment is held. The AP lead declines it because the supplier did not confirm the change.
The policy engine checks each action before it runs. (Runtime enforcement on the Gatehouse site)
14:31:52 · policy checkPASSHard calls wait for one named approver, with the evidence gathered. (Approvals on the Gatehouse site)
14:32:00 · payment heldHELDEach run is sealed into a record your team can read without Gatehouse. (Record on the Gatehouse site)
14:32:19 · record sealedSEALED
- invoice INV-40218 · 2,400.00
- bank detail · previous
- bank detail · first seen today
The eight capabilities of Gatehouse.
Each row opens that capability on the Gatehouse platform page, so you can send a reviewer only the part they need.
- P/01Policy engineYour rules, in one signed file.
- E/02Runtime enforcementEach action is checked before it runs. Anything the manifest does not name is refused.
- R/03RecordEach run is saved to the audit trail, chained by SHA-256.
- A/04ApprovalsHard calls wait for a named approver. Overriding a block takes two names.
- S/05Spend controlsA limit on what a run may spend or commit.
- L/06Least privilegeThe agent gets only the access the manifest names.
- C/07Continuous evaluationApprover decisions become labelled examples, and later changes are tested against them.
- X/08Data portabilityThe trail, policy history and examples export in open formats.
What you can check yourself.
Five things you can open and test yourself, on the Gatehouse site or on our trust page.
- 01The recordRUN-7F2K4, six events, as sealed.
- 02The manifestv14, five gates, signed.
- 03The chainChange a field and watch the SHA-256 chain break.
- 04The exportThe trail, policy history and labelled examples, in open formats, readable without Gatehouse.
- 05The answersOur written answers to the twelve questions to ask any AI vendor, on our trust page.
No SOC 2, no ISO 27001 today. The Gatehouse security page lists what is in place and what is not.
Each Surehand deployment runs on Gatehouse.
Surehand deploys and runs governed agents for clients. An engagement has three steps, and the last two happen on Gatehouse.
Teardown
We measure the volume and exception rate of one process, and you keep the document.
Deployment
We write the manifest with your team, you sign it, and the agent runs on Gatehouse under it.
Operation
We read the same audit trail you read. The trail, policy history and labelled examples export in open formats and read without Gatehouse.
Six pages on the Gatehouse site.
Each row opens one page of the Gatehouse site, in this tab.
- /01Platform The eight capabilities, one at a time.
- /02How it works Sign the rules, check each action, read the record.
- /03Security Written for your reviewer, with the certifications not held today.
- /04Work The three composite cases in brief. The full write-ups are on Surehand's Deployments page.
- /05Company How Gatehouse and Surehand fit together, and the claims the product does not make.
- /06Contact Book a 30-minute walkthrough.
A walkthrough or a teardown.
A walkthrough is 30 minutes on Gatehouse, with manifest v14 and the sealed record of INV-40218. A teardown is the first step of an engagement with Surehand, and you keep the document it produces.
support@surehand.io