Nested tenancy
You hold one parent account. Your system provisions a sub-tenant per customer through our API and applies an AOP template by customer type: packs plus response rules, applied in one call. Governance becomes part of your onboarding, not a services project.
Escalations stay in your product
When a customer's agent needs a human, our engine does not hold the decision and does not store the conversation. It fires a webhook with the context, you route it to the right reviewer inside your own interface, and the decision is recorded against the sub-tenant for reporting. Your customers experience governance as part of your product.
What this changes for your business
Per sub-tenant metering gives you the basis to package governance into your own plans.
a new retail customer signs up; your system provisions their sub-tenant with the retail template and their jurisdiction pack; weeks later one of their agents drafts a reply contradicting their refund policy; the response check escalates, your reviewer resolves it in your interface, and nothing of the conversation lives on our side.
Why now, for a platform
The era of open-ended bots on the big messaging channels is closing: Meta's January 2026 policy blocks open-ended general assistant bots on WhatsApp while explicitly allowing structured business bots for support, bookings, orders, and sales. Structure is now a platform mandate, and governed structure is what our engine produces. Selling governed agents is becoming the only way to sell agents at all.
Shadow per customer type
The first time you onboard a kind of customer you have not governed before, run that sub-tenant in shadow, let the ledger teach you the right template, then enforce.