Design partner programme
We are looking for three.
Sentinel is built and tested. What it has not had is a bank running it against real traffic, telling us where it is wrong. That is what a design partner is for, and we would rather say so plainly than dress an evaluation up as a purchase.
The exchange
What you get
- Deployment support, hands on. Self-hosted in your infrastructure. We help you stand it up rather than sending a link to the docs.
- Direct access to the person who wrote it. Not a support queue. A one-person company has exactly one escalation path and you are already on it.
- Pricing locked for the term of the partnership and the first renewal after it.
- Roadmap influence. What you need next moves ahead of what we assumed you would need.
- The evidence artefacts — shadow-mode report, evidence bundles, examiner walkthrough — whether or not you continue.
What we ask
- A real workflow. Production or near-production. A sandbox that never sees real traffic teaches neither of us anything.
- Weekly feedback for the pilot period, including the parts that are not working.
- A referenceable outcome if it goes well — a conversation with another institution, on your terms.
- Logo rights on success, and only on success. We will not list you while you are still deciding.
Why three, and not thirty
Because a design partnership that works requires more of our attention than a sale does, and we would rather three institutions get a serious engagement than thirty get an onboarding email. When these are filled we will say so on this page rather than quietly keep collecting.
How a pilot runs
Ninety days, structured so the risky part comes last. Nothing enforces until you have seen what enforcement would have done.
Deploy and watch
Self-hosted install, one agent workflow, governance mode set to OBSERVE. Sentinel evaluates every decision and enforces nothing. Your systems behave exactly as they do today. At the end you have a report quantifying decisions that fell outside policy, and which policy each one hit.
Tune against your own traffic
Flags and escalations start enforcing so human review begins working. Blocks are downgraded and annotated, so nothing stops in production. Thresholds get tuned against your decisions rather than our defaults. Monthly QA sampling starts producing a disagreement rate.
Graduate, on your evidence
Promotion to ENFORCE on the agent types where the shadow record justifies it — a governed change requiring a policy owner and a stated reason, recorded on the audit chain. Then an examiner walkthrough of one evidence bundle, end to end.
Success criteria we would propose, in the language your risk committee already uses: the shadow-mode report quantifies decisions outside policy; a walkthrough of one evidence bundle survives scrutiny; and the disagreement rate between the gate and human reviewers is measured rather than assumed.
What we are not going to pretend
- We have no customers yet. The logos and quotes on the pricing page are illustrative and labelled as such. You would be among the first, with everything that implies in both directions.
- We are not SOC 2 certified. Our current posture is stated plainly rather than implied, and self-hosting means your decision data never reaches us.
- The security stages detect known attack families. They are defence in depth, not a solved problem, and we publish what we do not catch.
- Published numbers describe stated conditions. Our latency benchmarks name the hardware and the payloads, and you can reproduce them.
- A verdict is not a regulatory determination. Sentinel enforces the policy you configure. The obligation stays yours.
If any of that is disqualifying, better that we both find out in the first email than in the third month.
Design partners
Bring the workflow you are most nervous about.
Tell us what your agents do today and where the exposure is. If shadow mode does not show you something you did not know, the pilot has cost you a deployment and a fortnight, and we will say so.
The plan, in writing
The 90 days above as a document you can take into an internal conversation without us: phase-by-phase success criteria, the scope outline an agreement needs, and a plain list of what a pilot this length will not tell you.
Read the pilot plan Download the PDF