Skip to content
Glossary

Tenant Isolation

Tenant isolation is the guarantee that each customer's data and configuration in a multi-tenant system remain logically separated and inaccessible to other tenants. It is enforced at every layer — storage, retrieval, and access control — so one organization can never see or influence another's work.

Synonyms: multi-tenant isolation, tenant scoping, data partitioning, tenancy boundary

Tenant isolation is the security foundation of any multi-tenant platform. Rather than running separate stacks per customer, the system shares infrastructure while enforcing a strict boundary so each tenant’s data, embeddings, configuration, and audit logs stay private. The boundary is applied by default at every layer: storage carries tenant identifiers, retrieval is scoped to the requesting tenant, and access control denies cross-tenant reads. Done correctly, isolation lets a platform scale efficiently on shared resources without ever compromising the confidentiality each organization expects.

Frequently asked questions

How is tenant isolation enforced during retrieval?
Every query is scoped to the requesting tenant, and stored content carries a tenant identifier so vector and keyword search can only return that tenant's own evidence.
Is isolation only about data?
No. It covers configuration, policy, embeddings, and audit logs as well, so no aspect of one tenant's work leaks into another's, even on shared infrastructure.