Multi-tenant Architecture
Multi-tenant architecture is a software design pattern in which a single software instance serves multiple independent user groups (tenants) simultaneously. Tenants share the same underlying infrastructure and application while maintaining logical isolation at the data and configuration levels. This architecture is widely used in cloud computing and SaaS services, offering high resource utilization, centralized operations, and support for per-tenant customization. Common implementation strategies include shared database, separate schema, and separate database isolation levels.
Core Facts
At the database level, multi-tenant data isolation mainly has three classic solutions: shared database + shared schema (field-level isolation), shared database + separate schema (schema-level isolation), and separate database (physical-level complete isolation).
Multi-tenancy is a foundational architectural pattern in cloud computing services, referring to multiple tenants sharing the same underlying computing resources and software instance while their data remains logically fully isolated from one another.
Multi-tenancy is a platform challenge that requires serving multiple business units and model versions within a single system while guaranteeing resource isolation, fair scheduling, and security.
Timeline (last 90 days)
Public clouds use a multi-tenant architecture in which different customers' virtual machines, storage and network resources share the same physical infrastructure and are isolated through a virtualization layer.
Under a multi-tenant architecture, flaws in the isolation layer (such as VM escape, metadata service abuse, or misconfigured network policies between tenants) may allow attackers to move laterally across tenants.
Creating inboxes on demand through a mail service provider's API allows a dedicated inbox to be created automatically when an agent starts and reclaimed automatically when it goes offline, binding identity to lifecycle, and suits scenarios with a dynamically changing number of agents or a multi-tenant architecture.
Tool calls in AI Agent endpoints pass tenant context from the HTTP request all the way to the tool execution context, and agentRunner.ts explicitly extracts the tenantId and passes it into the tool execution context.
Each tenant has its own independent set of encryption keys, so if a tenant requests data deletion, destroying its keys is enough to make the data unreadable without re-encrypting the entire database.
Security leads will pay particular attention to whether an Agent's memory persists across tenants, whether sessions are isolated, and whether tool-returned content is treated as untrusted input.
Under multi-tenant or shared-memory architectures, the harm of prompt injection is amplified: a single successful injection may poison persistent memory, affecting other sessions or tenants.
Multi-tenant architecture can serve a massive number of customers at extremely low marginal cost, but when an underlying component fails, the impact spans all tenants.
Salesforce uses a multi-tenant architecture in which all customers share the same underlying infrastructure, with data security ensured through logical isolation.
Multi-tenancy is a platform challenge that requires serving multiple business units and model versions within a single system while guaranteeing resource isolation, fair scheduling, and security.
1 more timeline events
All Facts (15)
At the database level, multi-tenant data isolation mainly has three classic solutions: shared database + shared schema (field-level isolation), shared database + separate schema (schema-level isolation), and separate database (physical-level complete isolation).
80%VerifiedMulti-tenancy is a foundational architectural pattern in cloud computing services, referring to multiple tenants sharing the same underlying computing resources and software instance while their data remains logically fully isolated from one another.
75%VerifiedMulti-tenancy is a platform challenge that requires serving multiple business units and model versions within a single system while guaranteeing resource isolation, fair scheduling, and security.
65%Unverified三种多租户数据隔离方案可以在同一平台中混合使用
85%Unverified电商/支付类商户平台场景中，小商户可采用共享Schema方式降低成本，大客户或有严格合规要求的商户应升级为独立Schema甚至独立数据库
85%UnverifiedThe scenario of managing multiple subsidiaries within a group company represents a moderate isolation requirement, for which the shared database + shared schema solution is generally the optimal choice.
60%UnverifiedUnder a multi-tenant architecture, flaws in the isolation layer (such as VM escape, metadata service abuse, or misconfigured network policies between tenants) may allow attackers to move laterally across tenants.
50%UnverifiedPublic clouds use a multi-tenant architecture in which different customers' virtual machines, storage and network resources share the same physical infrastructure and are isolated through a virtualization layer.
50%UnverifiedCreating inboxes on demand through a mail service provider's API allows a dedicated inbox to be created automatically when an agent starts and reclaimed automatically when it goes offline, binding identity to lifecycle, and suits scenarios with a dynamically changing number of agents or a multi-tenant architecture.
50%UnverifiedEach tenant has its own independent set of encryption keys, so if a tenant requests data deletion, destroying its keys is enough to make the data unreadable without re-encrypting the entire database.
50%UnverifiedTool calls in AI Agent endpoints pass tenant context from the HTTP request all the way to the tool execution context, and agentRunner.ts explicitly extracts the tenantId and passes it into the tool execution context.
50%UnverifiedUnder multi-tenant or shared-memory architectures, the harm of prompt injection is amplified: a single successful injection may poison persistent memory, affecting other sessions or tenants.
50%UnverifiedSecurity leads will pay particular attention to whether an Agent's memory persists across tenants, whether sessions are isolated, and whether tool-returned content is treated as untrusted input.
50%UnverifiedSalesforce uses a multi-tenant architecture in which all customers share the same underlying infrastructure, with data security ensured through logical isolation.
50%UnverifiedMulti-tenant architecture can serve a massive number of customers at extremely low marginal cost, but when an underlying component fails, the impact spans all tenants.
50%