Head to head
Iteradian vs dRPC
Iteradian and dRPC both run managed RPC. dRPC bills in compute units, sold per million requests; Iteradian bills a fixed monthly plan price in requests, at $39 per month for 25,000,000 requests, $169 per month for 80,000,000 requests, with overage capped per billing period. Iteradian has a free plan, Free RPC, across all 12 networks.
Iteradian
- Bills in
- Requests — one call is one request
- Entry paid plan
- Developer RPC: $39/month for 25,000,000 requests
- Free option
- Free
- Bittensor
- Native Subtensor JSON-RPC, every plan
dRPC
- Bills in
- compute units, sold per million requests
- Entry paid plan
- Growth — pay-as-you-go, $6 per 1M requests
- Free option
- Yes — 210M CU per month at 100 requests per second, routed to public nodes.
- Bittensor
- Bittensor EVM (chain 964) on the paid tier; native Subtensor RPC not documented
Every dRPC figure on this page was read from drpc.org/pricing on . Providers change pricing without notice — check the source before deciding. dRPC is a trademark of its owner; Iteradian is not affiliated with dRPC.
Why teams pick Iteradian over dRPC
Subtensor, not just the EVM
Native Substrate JSON-RPC for Bittensor — the interface the Bittensor SDK, miners and validators speak. dRPC documents the EVM side only.
Our nodes, not a public pool
Every request lands on nodes Iteradian operates, health-checked and failed over across up to three of them.
A plan you can budget
A fixed monthly price with a published overage cap, instead of topping up a balance.
Side by side
| Feature | Iteradian | dRPC |
|---|---|---|
| Billing unit | Requests — one call is one request | compute units, sold per million requests |
| Heavy methods cost more? | No — every call counts as one request | No — every call costs the same |
| Entry paid plan | Developer RPC: $39/month for 25,000,000 requests | Growth — pay-as-you-go, $6 per 1M requests · 5,000 requests/second |
| Free option | Free | Yes — 210M CU per month at 100 requests per second, routed to public nodes. |
| Past the allowance | $0.005 per 1,000 requests, capped at $150 per period, then HTTP 429 | None — dRPC states no monthly limits, no overage fees and no expiry on purchased requests. |
| Bittensor | Native Subtensor JSON-RPC, every plan | Bittensor EVM (chain 964) on the paid tier; native Subtensor RPC not documented |
| Networks | 12 in the catalogue, all on every plan | dRPC states 130+ chains across 231 networks |
| Per-key controls | IP allowlist (up to 50), allowed networks, rate limit and expiry on every key | Per-key limits and restrictions |
| Failover | Health-checked; a failed read tries up to 3 nodes | Not stated on the pages we read |
How the bill is built
How dRPC bills
dRPC charges a flat 20 compute units for every method and sells paid usage at $6 per 1M requests, pay-as-you-go, with no monthly limits, no overage fees and no expiry on purchased requests.
How Iteradian bills
One JSON-RPC call is one request, whether it is eth_blockNumber or a heavy eth_getLogs range; a batch of N calls counts as N. Past the monthly allowance, requests keep being served and are billed per 1,000, up to a spend cap per billing period. Past the cap the gateway answers HTTP 429 and the bill stops — so the worst case is known before the traffic arrives.
Both price lists, unconverted
Units differ, so nothing here is converted into the other side’s currency. Compare against your own traffic.
Iteradian — live from the control plane
| Plan | Price | Included | Throughput |
|---|---|---|---|
| Free RPC | $0/mo | 3,000,000 requests/month | 25 requests/second |
| Developer RPC | $39/mo | 25,000,000 requests/month | 250 requests/second |
| Professional RPC | $169/mo | 80,000,000 requests/month | 500 requests/second |
| Dedicated RPC | Custom | — | — |
dRPC
| Plan | Price | Included | Throughput |
|---|---|---|---|
| Free | $0/mo | 210M CU per month, public nodes | 100 requests/second |
| Growth | $6 per 1M requests | Pay-as-you-go, no expiry | 5,000 requests/second |
| Enterprise | Custom | From 300M requests/month | Unlimited RPS |
Where each one is strong
What dRPC does well
- A large free tier: 210M CU a month at 100 requests per second, on public nodes.
- 5,000 requests per second on the Growth plan.
- 130+ chains across 231 networks.
- Flat per-request pricing with no overage fees and no expiry.
Where Iteradian differs
- dRPC lists Bittensor’s EVM side; Iteradian serves Subtensor’s native Substrate JSON-RPC, the interface the Bittensor SDK and validators use.
- dRPC routes free-tier traffic to public nodes; Iteradian routes every request to nodes it operates.
- Iteradian charges a fixed monthly plan price with capped overage; dRPC draws down a prepaid balance per million requests.
- dRPC lists 99.99% uptime on Growth. Iteradian does not publish an uptime figure.
Choose dRPC when…
You need 130+ chains, a very large free tier, more than 1,000 requests per second on a self-serve plan, or a provider that publishes an uptime figure.
Choose Iteradian when…
You need Bittensor’s native Subtensor RPC, you want a fixed monthly plan instead of prepaid request packs, or you want every request served by operated nodes.
Start the trialQuestions people ask
Is Iteradian cheaper than dRPC?
It depends on your method mix, because the two meter differently. dRPC bills in compute units, sold per million requests, while Iteradian bills a fixed monthly plan price in requests: $39 per month for 25,000,000 requests, $169 per month for 80,000,000 requests. Past the allowance, overage is capped per billing period, after which the gateway returns HTTP 429 — so the worst-case bill is known in advance. Compare against your own traffic before switching.
Does dRPC have a free tier?
Yes — 210M CU per month at 100 requests per second, routed to public nodes.
Does dRPC support Bittensor?
On the pages we read: Bittensor EVM (chain 964) on the paid tier; native Subtensor RPC not documented. Iteradian serves Bittensor’s native Subtensor JSON-RPC on every plan, alongside the other networks in its 12-network catalogue.
When should I choose dRPC over Iteradian?
You need 130+ chains, a very large free tier, more than 1,000 requests per second on a self-serve plan, or a provider that publishes an uptime figure.