Deploying R2R

R2R (RAG to Riches) is designed to be flexible and scalable, allowing deployment in various environments. This guide provides an overview of deployment options and resource recommendations to help you get started with R2R in a production setting.

Deployment Options

1. Local Docker or Local Build: Ideal for development and testing. Start here.
2. Single Cloud Instance: Recommended for most small to medium-sized organizations.
3. Container Orchestration (Docker Swarm): Suitable for larger organizations or those requiring more granular resource control

Resource Recommendations

When running R2R, we recommend:

• At least 4 vCPU cores
• 8+GB of RAM (16GB preferred)
• 50gb + 4x raw data size (size of data to be ingested after converting to TXT) of disk space

Deployment Guides

For detailed, step-by-step instructions on deploying R2R in various environments, please refer to our specific deployment guides:

• Local Deployment
• Azure Deployment
• SciPhi Cloud

Choose the guide that best fits your infrastructure and scaling needs. Each guide provides specific instructions for setting up R2R in that environment, including necessary configurations and best practices.

By following these deployment recommendations and configuration guides, you’ll be well on your way to leveraging R2R’s powerful RAG capabilities in your production environment.