Charterdesk
A multi-client agency control plane that versions agent purpose, data, tools, spending, disclosures, approvals, and stop conditions, enforces only observable deterministic controls, and preserves client evidence, incidents, waivers, readback, and correction.
The research confirms an active open-source charter runtime and several managed governance competitors. None in the supplied review is explicitly packaged for an agency managing many client accounts, but no structural incumbent copying cost is evidenced. Multi-tenancy is a product requirement, not automatically a moat.
A written charter is not self-enforcing. Runtime policy can constrain observed tool calls, fields, destinations, rates, amounts, credentials, and approvals when the integration exposes them. It cannot prove model intent, hidden behavior, legal classification, lawful basis, disclosure sufficiency, risk management, human oversight, or compliance. Article references and audit-bundle claims require current primary legal review for the actual provider, deployer, importer, distributor, product, territory, and use.
Charterdesk should isolate every client, agent, credential, policy, log, reviewer, incident, and export. The agency drafts from client-approved facts; the client and qualified advisers approve. Evidence bundles name sources, gaps, exceptions, waivers, provider acknowledgments, and corrections. No report is handed to a regulator as a certification or signed on the client's behalf.
Professional-services, training, and implementation firms deploying and operating agents for multiple clients that need isolated charters, runtime controls, and source-linked evidence.
Active governance products and regulatory attention create demand.
Professional-service firms deploying agents for clients are specific.
Several shadow, manifest, spending, and agency-console neighbors support the direction.
The agency buyer, live open and managed category, client isolation, observable charter controls, and evidence bundle are concrete.
Several competitors exist, no structural moat is shown, runtime coverage depends on integrations, legal classification is complex, and managed service and security costs may be high.
Discussion
No comments yet — be the first to weigh in.
