Gatehouse
The control plane every deployment runs on. Signed rules checked on each action, holds that go to a named approver, spend limits, and a record chained so any edit shows.
Careers
Build the software agents answer to.
We built Gatehouse. We run clients' agents on it. You would do both. Hiring has three steps, and you get the answer in writing.
Open applications
We are small and we hire rarely. Built something like Gatehouse? Write to support@surehand.io and show us. A person reads it.
What helps most: a link to something you built and ran, a short note on the worst time it broke and how you found out, and what you would change about it now. No cover letter needed.
Show us what you builtWhat you would work on
Deployments
A client brings one queue. We study it, build the agent, and run it on Gatehouse under rules the client signs. The same people who build it answer for it after launch.
The reference
What we learn goes into the articles on this site: holds, limits, records, and where each standard stops. Writing it down is part of the job, not a side project.
Who tends to fit
- You have run software that other people depended on, and you were the one paged when it broke.
- You would rather an agent stop and ask than guess, and you can explain why to someone who signs off.
- You write clearly. Most of our work ends as a document a client keeps.
- You can say “not worth automating yet” to a client and mean it.
How we hire
A call
With the people you'd work with. Your work, then ours.
A short exercise
Real work, small size. You keep what you make.
An answer
In writing. With the reason. Yes or no.