Tenant Isolation

Tenant Isolation

Tenant Isolation

In multi-tenant architecture, multiple customers share infrastructure while their data remains logically separated. Isolation is enforced through access controls, separate encryption keys, and query-level restrictions.

Single-tenant deployment provides physical separation at higher cost.

Alternative Names:

Multi-Tenant Isolation, Data Segregation

Why it Matters?

Isolation is the control that matters most when a legal vendor serves opposing parties in the same litigation, which is common for widely adopted platforms. A firm should be able to state that its matter data is not reachable from another tenant's environment, including through search, analytics, and AI retrieval. Isolation failures in AI systems are a newer risk, since embeddings and indexes derived from one tenant's documents must be scoped the same way the documents are.

Frequently Confused with

Related terms

Frequently asked questions

Is multi-tenant architecture less secure?

Is multi-tenant architecture less secure?

Not inherently. Properly implemented logical isolation is widely accepted. The question is whether isolation extends to search indexes, analytics, and AI retrieval as well as stored documents.

When is single-tenant deployment warranted?

When is single-tenant deployment warranted?

Where client requirements or regulatory obligations demand physical separation, though it carries higher cost and often slower feature delivery.