Limits & Quotas
Ocriva enforces usage limits at the organization level to ensure fair resource allocation and predictable costs. Every subscription plan includes a defined set of quotas. Understanding these limits helps you plan capacity and avoid unexpected service interruptions.
Limit Categories
Each organization is subject to the following types of limits:
| Limit | What It Controls |
|---|---|
| Storage (GB) | Total file storage across all projects in the organization |
| Templates | Number of extraction templates across all projects |
| AI Credits | Monthly credit allocation included in the subscription |
| Requests (Class A) | AI processing requests per billing period |
| Reads (Class B) | Read/retrieval API calls per billing period |
| Data Transfer (GB) | Outbound data volume per billing period |
| Webhook Endpoints | Number of active webhook destinations |
| Members | Maximum number of organization members (default: 10) |
NOTE
All limits apply at the organization level and are shared across every project within that organization. There are no separate per-project quotas — each project draws from the same organization-wide pool.
Limits by Plan
The following table shows the included limits for each subscription plan:
| Limit | Free | Starter | Pro | Business | Advance |
|---|---|---|---|---|---|
| Storage | 1 GB | 2 GB | 5 GB | 10 GB | 20 GB |
| Templates | 5 | 10 | 50 | 100 | Unlimited |
| Requests (Class A) | 1,000 | 5,000 | 10,000 | 25,000 | 50,000 |
| Reads (Class B) | 10,000 | 50,000 | 100,000 | 250,000 | 500,000 |
| Data Transfer | 1 GB | 2 GB | 2 GB | 5 GB | 10 GB |
| Webhook Endpoints | 0 | 1 | 5 | Unlimited | Unlimited |
| Webhook Feature | No | No | Yes | Yes | Yes |
| Priority Support | No | No | No | Yes | Yes |
| SLA Guarantee | No | No | No | No | Yes |
IMPORTANT
The Free plan disables features that exceed the quota rather than charging for overages. Paid plans charge for usage beyond the included allocation at the plan's overage rate.
API Rate Limiting
The public API does not currently enforce a per-token request rate limit. Rate limiting may be introduced in a future platform update.
If rate limiting is enforced in the future, the API will return HTTP 429 Too Many Requests and include X-RateLimit-* response headers indicating your current allowance and reset time. Check those headers if you receive a 429 response.
What Happens When a Limit Is Exceeded
The behaviour when a limit is reached depends on both the limit type and the plan:
| Limit Type | Free Plan Behaviour | Paid Plan Behaviour |
|---|---|---|
| Storage | Feature blocked — uploads rejected | Overage charged per GB per billing cycle |
| Templates | Creation blocked — upgrade required | Creation blocked — upgrade required |
| Requests (Class A) | Feature blocked — upgrade required | Overage charged at plan rate |
| Reads (Class B) | Feature blocked — upgrade required | Overage charged at plan rate |
| Data Transfer | Feature blocked — upgrade required | Overage charged per GB |
| Webhook Endpoints | Not available — upgrade required | Blocked — upgrade required |
| AI Credits | Processing blocked — top-up required | Processing blocked — top-up required |
IMPORTANT
Exceeding your AI credit balance blocks processing regardless of plan. Credits must be topped up separately — they are not automatically extended by the subscription.
Viewing Current Usage
You can monitor your organization's usage in real time from the limits page:
- Go to Organization → Limits
- The page shows a progress bar for each limit category with current usage vs. the plan quota
- Limits approaching capacity are highlighted with a warning indicator
- Use the Refresh button to reload the latest usage figures
Usage data is derived from live database counts — storage is the sum of all non-deleted uploaded file sizes, template counts include active and inactive templates, and request counts are tracked per billing period.
Viewing Usage via the Analytics Dashboard
The Analytics page provides a complementary view focused on processing activity:
- Document processing volume — total, this month, last month, growth percentage
- Storage utilisation — used vs. limit in MB
- Member activity — who is processing the most documents
See the Analytics & Usage Tracking doc for full details.
Requesting Limit Increases
If your usage regularly approaches or exceeds your plan's quotas, the recommended path is to upgrade your subscription plan from Organization → Billing. Each higher tier includes significantly larger quotas across all dimensions.
For the Advance plan, which requires manual onboarding, contact the Ocriva sales team directly. Advance includes unlimited templates, unlimited webhook endpoints, and the highest request quotas with a dedicated server option.
NOTE
Overage charges on paid plans are billed at the end of each billing cycle, not in real time. You will not be cut off mid-cycle on a paid plan — you will see the extra charge on your next invoice.
Best Practices
- Monitor usage before large batch runs. The Limits page shows live figures. Check it before submitting jobs that might push you over a quota.
- Delete processed uploads that are no longer needed. Soft-deleted files are excluded from storage calculations, freeing up quota immediately.
- Deactivate unused templates. Template count limits apply to all non-deleted templates, including inactive ones.
- Use the Free plan only for evaluation. The Free tier disables features rather than charging overages — unexpected blocks can interrupt workflows. Move to a paid plan for production use.
- Set up webhook notifications for processing failures. Failures still count against your request quota. Fixing misconfigured templates early avoids wasted usage.