Implement multitenancy using namespaces
Multitenancy is a software architecture where a single instance of a system serves multiple customers, or tenants, while ensuring data isolation between them for privacy and security.
This page shows you how to implement multitenancy in Pinecone using a serverless index with one namespace per tenant.
How it works


In Pinecone, an index is the highest-level organizational unit of data, where you define the dimension of vectors to be stored in the index and the measure of similarity to be used when querying the index.
Within an index, records are stored in namespaces, and all upserts, queries, and other data plane operations always target one namespace.
This structure makes it easy to implement multitenancy. For example, for an AI-powered SaaS application where you need to isolate the data of each customer, you would assign each customer to a namespace and target their writes and queries to that namespace (diagram above).
In cases where you have different workload patterns (e.g., RAG and semantic search), you would use a different index for each workload, with one namespace per customer in each index:


Understand the benefits
Understand the benefits
-
Tenant isolation: In the serverless architecture, each namespace is stored separately, so using namespaces provides physical isolation of data between tenants/customers.
-
No noisy neighbors: Reads and writes always target a single namespace, so the behavior of one tenant/customer does not affect other tenants/customers.
-
No maintenance effort: Serverless indexes scale automatically based on usage; you don’t configure or manage any compute or storage resources.
-
Cost efficiency: With serverless indexes, you pay only for the amount of data stored and operations performed. For queries in particular, the cost is partly based on the total number of records that must be scanned, so using namespaces can significantly reduce query costs.
-
Simple tenant offboarding: To offboard a tenant/customer, you just delete the relevant namespace. This is a lightweight and almost instant operation.
1. Create a serverless index
Based on a breakthrough architecture, serverless indexes scale automatically based on usage, and you pay only for the amount of data stored and operations performed. Combined with the isolation of tenant data using namespaces (next step), serverless indexes are ideal for multitenant use cases.
To create a serverless index, use the spec
parameter to define the cloud and region where the index should be deployed. For Python, you also need to import the ServerlessSpec
class.
2. Isolate tenant data
In a multitenant solution, you need to isolate data between tenants. To achieve this in Pinecone, use one namespace per tenant. In the serverless architecture, each namespace is stored separately, so this approach ensures physical isolation of each tenant’s data.
To create a namespace for a tenant, specify the namespace
parameter when first upserting the tenant’s records. For example, the following code upserts records for tenant1
and tenant2
into the multitenant-app
index:
When upserting additional records for a tenant, or when updating or deleting records for a tenant, specify the tenant’s namespace
. For example, the following code updates the dense vector value of record A
in tenant1
:
3. Query tenant data
In a multitenant solution, you need to ensure that the queries of one tenant do not affect the experience of other tenants/customers. To achieve this in Pinecone, target each tenant’s queries at the namespace for the tenant.
For example, the following code queries only tenant2
for the 3 vectors that are most similar to an example query vector:
4. Offboard a tenant
In a multitenant solution, you also need it to be quick and easy to offboard a tenant and delete all of its records. To achieve this in Pinecone, you just delete the namespace for the specific tenant.
For example, the following code deletes the namespace and all records for tenant1
:
Alternative: Metadata filtering
When tenant isolation is not a strict requirement, or when you need to query across multiple tenants simultaneously, you can store all records in a single namespace and use metadata fields to assign records to tenants/customers. At query time, you can then filter by metadata.
For more guidance on this approach, see Multitenancy in Vector Databases.