This page provides recommendations and best practices for preparing your Pinecone indexes for production, anticipating production issues, and enabling reliability and growth.
One of the first steps towards building a production-ready Pinecone index is configuring your project correctly.
Consider creating a separate project for your development and production indexes, to allow for testing changes to your index before deploying them to production.
Ensure that you have properly configured user access to the Pinecone console, so that only those users who need to access the production index can do so.
Ensure that you have properly configured access through the API by managing API keys and using API key permissions.
Before you move your index to production, make sure that your index is returning accurate results in the context of your application by identifying the appropriate metrics for evaluating your results.
In order to enable long-term retention, compliance archiving, and deployment of new indexes, consider backing up your production indexes by creating a backup or collection.
If you need help, contact Support, or talk to the Pinecone community. Ensure that your plan tier matches the support and availability SLAs you need. This may require you to upgrade to Enterprise.