Cloud Limits

SciPhi Cloud imposes limits to govern the maximum number of documents, chunks, and collections per user, as well as rate limits for requests and file-upload sizes. The same defaults apply when you deploy R2R locally (though you can override them in your local r2r.toml).

Overview of Limits

Default Limits

Below are the default per-user limits for all R2R Cloud deployments:

Note: Additionally, our Nginx ingress layer applies a 60 requests/minute per IP limit.
Thus, a single IP cannot exceed 60 requests/minute, regardless of user account.

File Upload Size by Extension

R2R Cloud enforces specific maximum file sizes for different file types. If no extension-specific limit is found, we fall back to the global 2 MB limit.

You can customize or override these limits in your own r2r.toml if deploying locally.

Route-Specific Rate Limits

In the cloud.toml example, certain endpoints have additional per-route limits. For instance:

These per-route limits are enforced in addition to the global 60 req/min user limit.
If a per-route limit is lower than the global limit, that route’s usage will be throttled sooner.

Starter Tier Overrides

When upgrading to the Starter Tier, these default limits increase:

All other limits (like file size and request rates) remain the same unless otherwise specified by your plan.

Local Deployment

If you deploy R2R on your own infrastructure, the same default limits apply out of the box. However, you can easily override them in your local r2r.toml or equivalent configuration. For example:

1
[app]
2
default_max_documents_per_user = 200
3
default_max_chunks_per_user = 50_000
4
default_max_collections_per_user = 20
5
default_max_upload_size = 10_000_000  # 10 MB

And for route-based limits:

1
[database.route_limits]
2
"/v3/retrieval/search" = { route_per_min = 50, monthly_limit = 10_000 }

Additional Notes

• User-Level Overrides: Admins can grant custom overrides to specific users. For example, a single user’s “max_documents” might be raised to 5,000.
• Monthly Limits: Resets on the 1st of each month.
• Request Logging: R2R logs usage for each route to track compliance with monthly or per-minute limits.
• Nginx Rate Limit: Cloud deployments also apply a 60 requests/minute limit per IP at the ingress layer.

Conclusion

R2R Cloud’s default usage limits keep the platform performant and equitable. When you need more capacity—such as uploading larger documents or making more requests—upgrading your tier or adjusting local r2r.toml (for self-hosted deployments) is straightforward.

By keeping usage within your plan’s limits and splitting large files where necessary, you’ll ensure a smooth experience with R2R’s ingestion, retrieval, and advanced AI features.