Multi-tenancy strategies in Pinecone

Today, we published a piece about how to handle multi-tenancy in Pinecone as part of a larger series on tips for getting into production. What questions do you still have? Tips to share? We’d love to hear from you!

2 Likes

How does it provide security and isolation for each tenant as data resides in the same index?
Eg: Tenant might have some data that is very much critical and we can use metadata for isolation. But do you think its secure full fledgedly?

Hey @tirushv9 - Thanks for joining the Pinecone community forums!

While namespaces reside in the same index, they are stored separately, providing physical isolation of data between tenants/customers.

There are a few added benefits of namespaces over using metadata to isolate:

  • Reads and writes always target a single namespace, so the behavior of one tenant/customer does not affect other tenants/customers
  • 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.
  • Easy to off-board a tenant by deleting a namespace.

You can read more about this here, but if you have more questions, please feel free to create a new post for the specific issue.