For MSPs and consultancies
Your clients are already using AI. You are already the one they will ask about it.
One parent account, a client organisation for each of yours, and a roll-up that shows all of them at once. Packs go out under your name. Nothing crosses between clients.
Client A · logistics41,208observedQ3 · signedClient B · dental group6,114observedQ3 · signedClient C · legal2,930attestedQ3 · signed+ 17 moreSelling a dashboard is a renewal conversation. Selling proof is a retainer.
Every client has this problem and none of them has a list.
Somebody in accounts pasted a customer file into a chatbot last quarter. Nobody can say what, when, or where it went. You can be the one who can.
A quarterly pack with your logo on it.
Signed evidence, mapped to the frameworks your client answers to, produced without you assembling screenshots the night before the meeting.
Your price, not ours.
$199 per client per month, from five clients. Bill your client whatever the engagement is worth. We are not in that conversation and do not want to be.
How tenancy works
Access you can explain to a client without them going quiet.
Separate keys, separate chains
Each client organisation signs with its own key and keeps its own receipt chain. A receipt from one client cannot be verified against another's key, which is the technical form of the promise.
Every time you look, it is recorded
Opening a client organisation from the parent account writes an entry on that client's own activity log, visible to them. You get convenience; they get the record. Both, or neither.
Hand over the keys whenever they ask
Promote a client contact to owner and the organisation is theirs, including on the day they leave you for another MSP. Evidence held hostage is not evidence.
You cannot quietly widen your own access
The permissions a client grants the parent account are the client's to change, not yours. The console refuses the controls a role is not given rather than showing them and failing later.
It lands in the stack you already run on.
Evidence goes where your team already works, rather than asking them to open one more tab.
ConnectWise
Tickets raised from a held request or a failed control.
Autotask
The same, against your existing queues and boards.
Microsoft 365
Entra sign-in, Purview labels, and Copilot routes where they are reachable.
Your SIEM
Sentinel, Splunk or an HTTP endpoint, with presets for each.
Scope it accurately and the engagement lands every time.
We hand your client evidence, not our certificate.
We produce evidence their auditor can use. Where a client's questionnaire needs a certified vendor, self-hosting is how they start, and it changes the question entirely.
Coverage is a map, not a promise.
A native app with its own HTTP client, a hardcoded endpoint, Bedrock and Vertex sit outside the path. The browser extension covers four AI sites and nothing else. Coverage is a page inside the product, so you can show a client exactly where the edges are and bill for closing them.
Windows installs warn until our certificate lands.
The device agent installs on macOS, Linux and Windows. On Windows it warns until our code-signing certificate is issued. Everything else, gateway, receipts, packs, is unaffected.