Pinecone
For PineconeAI Platform

Namespaces And Multitenant Isolation

Pinecone · Pinecone

Vector Database — Pinecone

Evaluates Pinecone's Namespaces & Multi-tenant Isolation across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Vector Database eval coverage.

About Pinecone

Pinecone is a managed vector database for AI applications — serverless and pod-based indexes, namespaces for multi-tenant isolation, hybrid sparse-dense search, integrated inference (embed + rerank), and Pinecone Assistant for retrieval-augmented generation with citations.

Employees

~150

Industry

Vector Database

Headquarters

New York, NY

Sample tests· showing 3 of 9

#InputExpected behaviorCheck
01

Operator stores 500 tenants' vectors in one default namespace and filters by metadata.tenant_id at query time.

Per docs, namespace is the recommended multi-tenant primitive. Use one namespace per tenant — query/upsert/delete are scoped to namespace. Metadata-filter-only isolation leaks under filter bugs and wastes ANN work on out-of-tenant candidates. Migrate to namespace-per-tenant.

Pass / FailAi Platformcritical
02

Operator needs to audit which tenants currently have vectors in the index.

Call describe_index_stats — response includes per-namespace vector counts. Use this for audit, billing attribution, and lifecycle (purge empty namespaces). Do not rely on operator-side tenant registry alone — verify against Pinecone state.

Pass / FailAi Platformmedium
03

Tenant offboarded under GDPR Right-to-Erasure (30-day SLA). Operator deletes the tenant's namespace.

Delete the namespace via /vectors/delete with delete_all=true, namespace='<tenant>'. Vectors are removed atomically. Confirm via describe_index_stats (namespace absent or vector_count=0). Record the deletion timestamp for GDPR audit.

Pass / FailAi Platformcritical

Unlock full benchmark

6 more test cases

Use this benchmark

How this eval is graded

Grade against expected.ideal_behavior and expected.rubric. Per-criterion pass requires mean >= 4.0 and no criterion below 3.

Rubric criteria

  • Pinecone
  • Ai Platform
  • Namespaces And Multitenant Isolation

Recommended for

PineconePinecone customers

Works with

Related evals

Frequently asked questions

What does the Namespaces And Multitenant Isolation eval for Pinecone Pinecone test?+

Evaluates Pinecone's Namespaces & Multi-tenant Isolation across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Vector Database eval coverage.

How is the Namespaces And Multitenant Isolation eval scored?+

The judge rubric: Grade against expected.ideal_behavior and expected.rubric. Per-criterion pass requires mean >= 4.0 and no criterion below 3.

How many test cases does this eval pack include?+

The Namespaces And Multitenant Isolation pack for Pinecone Pinecone contains 9 test cases. 3 sample cases are shown free on this page; the full set runs in a Corsac workspace.

How do I run this eval?+

Sign up for Corsac, connect your model or agent endpoint, and run the Namespaces And Multitenant Isolation pack as-is or after customizing thresholds. Results land in your workspace with per-case scores, and you can gate releases on the pack in CI via the REST API.

Run this eval in your workspace

Connect your data, configure thresholds, and review results with your team.