Quotas and limits
This page describes usage quotas, rate limits, and hard limits for Pinecone.
Quotas
Quota type | Starter plan | Standard plan | Enterprise plan |
---|---|---|---|
Projects per organization | 1 | 20 | 100 |
Pods per organization | 0 | 100 | 100 |
Serverless indexes per project | 5 | 20 | 20 |
Serverless index storage per project | 2 GB | N/A | N/A |
Namespaces per serverless index | 100 | 10,000 | 100,000 |
Serverless backups per project | N/A | 50 | 50 |
Pod-based indexes per project | 0 | N/A | N/A |
Pods per project 1 | 0 | 2 | 2 |
Collections per project | 100 | N/A | N/A |
Projects per organization
Starter plan | Standard plan | Enterprise plan |
---|---|---|
1 | 20 | 100 |
When you reach this quota for an organization, trying to create projects will fail and return a 403 - QUOTA_EXCEEDED
status with the following error:
To increase this quota, upgrade your plan or contact Support.
Pods per organization
Starter plan | Standard plan | Enterprise plan |
---|---|---|
0 | 100 | 100 |
When you reach this quota for an organization, trying to create pod-based indexes in any project in the organization will fail and return a 403 - QUOTA_EXCEEDED
status with the following error:
To increase this quota, contact Support](https://app.pinecone.io/organizations/-/settings/support/ticket).
Serverless indexes per project
Starter plan | Standard plan | Enterprise plan |
---|---|---|
5 | 200 | 200 |
When you reach this quota for a project, trying to create serverless indexes in the project will fail and return a 403 - QUOTA_EXCEEDED
status with the following error:
To increase this quota, upgrade your plan or contact Support.
Serverless index storage per project
Starter plan | Standard plan | Enterprise plan |
---|---|---|
2 GB | N/A | N/A |
When you’ve reached this quota for a project, updates and upserts into serverless indexes will fail and return a 403 - QUOTA_EXCEEDED
status with the following error:
To continue writing data into your serverless indexes, delete records to bring you under the limit or upgrade your plan.
Namespaces per serverless index
Starter plan | Standard plan | Enterprise plan |
---|---|---|
100 | 10,000 | 100,000 |
When you reach this quota for a serverless index, trying to upsert records into a new namespace in the index will fail and return a 403 - QUOTA_EXCEEDED
status with the following error:
To increase this quota, upgrade your plan.
These quotas are intended to provide reasonable boundaries and prevent unexpected or unintentional misuse. To increase your quota beyond the standard allotment, contact Support.
Serverless backups per project
Starter plan | Standard plan | Enterprise plan |
---|---|---|
N/A | 50 | 50 |
When you reach this quota for a project, trying to create serverless backups in the project will fail and return a 403 - QUOTA_EXCEEDED
status with the following error:
Pod-based indexes per project
Starter plan | Standard plan | Enterprise plan |
---|---|---|
0 | N/A | N/A |
When you try to create a pod-based index on the Starter plan, the request will fail and return a 403 - QUOTA_EXCEEDED
status with the following error:
To create pod-based indexes, upgrade your plan.
Pods per project
Starter plan | Standard plan | Enterprise plan |
---|---|---|
0 | 2 | 2 |
The default limit on the number of pods per project is for organizations on Standard and Enterprise plans. This limit can be customized in the Pinecone console:
- Go to Settings > Projects.
- For the project you want to update, click the ellipsis (..) menu > Configure.
- In the Pod Limit section, update the number of pods.
- Click Save Changes.
When you reach this quota for a project, trying to create pod-based indexes in the project will fail and return a 403 - QUOTA_EXCEEDED
status with the following error:
Collections per project
Starter plan | Standard plan | Enterprise plan |
---|---|---|
100 | N/A | N/A |
When you reach this quota for a project, trying to create collections in the project will fail and return a 403 - QUOTA_EXCEEDED
status with the following error:
To increase this quota, upgrade your plan.
Rate limits
The following rate limits apply to serverless indexes only.
Limit type | Starter tier | Standard tier | Enterprise tier |
---|---|---|---|
Read units per month per project | 1,000,000 | N/A | N/A |
Write units per month per project | 2,000,000 | N/A | N/A |
Upsert size per second per namespace | 50 MB | 50 MB | 50 MB |
Query read units per second per index | 2,000 | 2,000 | 2,000 |
Update records per second per namespace | 100 | 100 | 100 |
Fetch requests per second per index | 100 | 100 | 100 |
List requests per second per index | 200 | 200 | 200 |
Describe index stats requests per second per index | 100 | 100 | 100 |
Delete records per second per namespace | 5,000 | 5,000 | 5,000 |
Delete records per second per index | 5,000 | 5,000 | 5,000 |
Read units per month per project
Starter plan | Standard plan | Enterprise plan |
---|---|---|
1,000,000 | N/A | N/A |
Read units measure the compute, I/O, and network resources used by fetch, query, and list requests to serverless indexes. When you reach the monthly read unit limit for a project, fetch, query, and list requests to serverless indexes in the project will fail and return a 429 - TOO_MANY_REQUESTS
status with the following error:
To continue reading from serverless indexes in the project, upgrade your plan.
To check how close you are to the monthly read unit limit for a project, do the following:
- Open the Pinecone console.
- Select the project.
- Select any index in the project.
- Look under Starter Usage.
Write units per month per project
Starter tier | Standard tier | Enterprise tier |
---|---|---|
2,000,000 | N/A | N/A |
Write units measure the storage and compute resources used by upsert, update, and delete requests to serverless indexes. When you reach the monthly write unit limit for a project, upsert, update, and delete requests to serverless indexes in the project will fail and return a 429 - TOO_MANY_REQUESTS
status with the following error:
To continue writing data to serverless indexes in the project, upgrade your plan.
To check how close you are to the monthly read unit limit for a project, do the following:
- Open the Pinecone console.
- Select the project.
- Select any index in the project.
- Look under Starter Usage.
Upsert size per second per namespace
Starter tier | Standard tier | Enterprise tier |
---|---|---|
50 MB | 50 MB | 50 MB |
When you reach the per second upsert size for a namespace in an index, additional upserts will fail and return a 429 - TOO_MANY_REQUESTS
status with the following error:
To increase this limit, upgrade your plan. Otherwise, you can handle this limit by automatically retrying requests with an exponential backoff.
Query read units per second per index
Starter tier | Standard tier | Enterprise tier |
---|---|---|
2,000 | 2,000 | 2,000 |
Pinecone measures query usage in read units. When you reach the per second limit for queries across all namespaces in an index, additional queries will fail and return a 429 - TOO_MANY_REQUESTS
status with the following error:
To handle this limit, automatically retry requests with an exponential backoff.
To check how many read units a query consumes, check the query response.
Update records per second per namespace
Starter tier | Standard tier | Enterprise tier |
---|---|---|
100 | 100 | 100 |
When you reach the per second update limit for a namespace in an index, additional updates will fail and return a 429 - TOO_MANY_REQUESTS
status with the following error:
To increase this limit, upgrade your plan. Otherwise, you can handle this limit by automatically retrying requests with an exponential backoff.
Fetch requests per second per index
Starter tier | Standard tier | Enterprise tier |
---|---|---|
100 | 100 | 100 |
When you reach the per second fetch limit across all namespaces in an index, additional fetch requests will fail and return a 429 - TOO_MANY_REQUESTS
status with the following error:
To handle this limit, automatically retry requests with an exponential backoff.
List requests per second per index
Starter tier | Standard tier | Enterprise tier |
---|---|---|
200 | 200 | 200 |
When you reach the per second list limit across all namespaces in an index, additional list requests will fail and return a 429 - TOO_MANY_REQUESTS
status with the following error:
To handle this limit, automatically retry requests with an exponential backoff.
Describe index stats requests per second per index
Starter tier | Standard tier | Enterprise tier |
---|---|---|
100 | 100 | 100 |
When you reach the per second describe index stats limit across all namespaces in an index, additional list requests will fail and return a 429 - TOO_MANY_REQUESTS
status with the following error:
To handle this limit, automatically retry requests with an exponential backoff.
Hard limits
- Query
-
The max value for
top_k
, the number of results to return, is 10,000. -
The result size limit for a query is 4MB. The result size is affected by the dimension of the dense vectors and whether or not dense vector values and metadata are included in the result.
If a query fails due to exceeding the 4MB result size limit, choose a lower
top_k
value, or useinclude_metadata=False
orinclude_values=False
to exclude metadata or values from the result.
-
- Upsert
- Max upsert size is 2MB or 1000 records, whichever is reached first. see Upsert limits for more information.
- Max metadata size per record is 40 KB.
- Max length for a record ID is 512 characters.
- Max dimensionality for dense vectors is 20,000.
- Dense vectors must contain at least one non-zero value.
- Sparse vectors can contain no more than 1000 non-zero values.
- Max dimensionality for sparse vectors is 4.2 billion.
- Fetch
- Max records per fetch request is 1,000.
- Delete
- Max records per delete request is 1,000.
Pinecone Assistant
See Understanding Assistant for limitations to Pinecone Assistant.
Inference API limits
See Understanding Pinecone Inference API for limits.
Was this page helpful?