RVO pricing is based on explicit throughput and request limits. Every plan defines clear boundaries, so available capacity is predictable and transparent.
Limits are enforced consistently across all plans. You upgrade only when your workload requires more capacity.
All plans run on the same production RPC infrastructure. Capacity scales — behavior does not.
Higher tiers increase sustained throughput, daily limits, and retention thresholds.
Designed for teams that require stable performance, explicit limits, and operational clarity.
Choose the package that matches your workload. All plans run on the same infrastructure — only capacity scales.
Development & testing
Free tier for local development and early integration.
Small production workloads
Predictable capacity for early production systems.
Balanced production
The default choice for most production workloads.
High throughput
For demanding systems with sustained high traffic.
Detailed limits, retention, and feature differences are listed below.
Limits are enforced per API key and define the maximum sustained capacity available to a workload. All plans follow the same enforcement model — only the thresholds differ.
Capacity limits and operational characteristics per plan. All plans run on the same production infrastructure.
| Category | Developer | Essential | Core | Scale |
|---|---|---|---|---|
| Monthly price | €0 | €29 | €99 | €250 |
| Requests per second (RPS) | 2 | 10 | 50 | 100 |
| Requests per day | 2,000 | 100,000 | 500,000 | 1,500,000 |
| Usage & metrics retention | 1 day | 30 days | 60 days | 90 days |
| Request payload logging | Disabled | Disabled | Disabled | Disabled |
| Routing behavior | Shared capacity | Preferential handling | Higher scheduling priority | Strong isolation bias |
| Support | Community | Priority email | Priority |
Limits are enforced per API key. Short-term bursts above the listed RPS may be permitted when unused capacity is available.
Usage metrics include request counts, error rates, and method-level aggregates. Request payloads are never stored.
RVO is designed to accommodate workloads with additional capacity, isolation, or architectural requirements. The extensions below describe supported and planned capabilities, evaluated based on operational readiness.
Adjustments to sustained request-per-second limits and daily quotas beyond standard plan thresholds. Evaluated for workloads with non-linear traffic patterns or specialized backend requirements.
Available on a case-by-case basis depending on workload characteristics and operational impact.
Support for isolated, dedicated RPC capacity is part of RVO’s long-term architecture. Dedicated infrastructure introduces additional operational complexity and requires sufficient maturity under real production load.
This capability is planned but not generally available. Provisioning depends on proven scaling behavior and operational readiness.
Support for additional blockchain networks is part of RVO’s roadmap and will be integrated into standard pricing tiers once reliability, isolation, and scaling requirements are met.
Multi-chain access is planned but not available at this stage. Rollout depends on operational experience and verified stability.
Ready when you are
Create a free API key and send requests immediately. Limits are explicit, upgrades are instant, and nothing is hidden.
