Watch everything, break nothing
Hal reads your clients’ environments over access you grant and revoke yourself, keeps every escalation he raises as a numbered report, and signs every report so you can prove it.
You are not evaluating this for one company. You are deciding whether to put it in front of every client you have, which makes the blast radius of a bad day the real question, ahead of any feature.
So these pages are about what Hal cannot do, where the boundary is drawn, and how you check it without asking us. Each one ends somewhere you can verify the claim yourself: in your own admin console, in the record of every escalation, or in a signature you can test in your browser against a fingerprint published in public DNS.
Architecture
Hal can watch everything and break nothing
Nothing Hal ships runs in the kernel, so the failure that took fleets down in 2024 has no path here.
OpenEvidence
Every escalation, every client, retained
Hal keeps every escalation he raises as a numbered report against the client it belongs to, with the model that judged it and the reasoning, for the life of your instance.
OpenMulti-tenancy
Built for MSPs from day one
Every client's security signals in one place, instead of a login per tenant.
OpenProof
Verify a security report
Check a signature yourself, in your browser. Nothing is uploaded.
OpenSee what Hal surfaces on your own clients.
No deck. Ask us anything first. When you want to see Hal on your own tenants, we sign a short evaluation agreement and stand up your instance; you connect one tenant, Hal watches it for 14 days, and we walk you through what he found.
- 01You ask us your questions. No deck, no demo dataset.
- 02You sign a short evaluation agreement, and we stand up your own instance.
- 03You connect one tenant from your own admin console. Hal watches it for 14 days.
- 04We walk through what he found. Keep going month to month, or revoke the scopes yourself and stop.