Head to head
Iteradian vs QuickNode
Iteradian and QuickNode both run managed RPC. QuickNode bills in API credits; 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
QuickNode
- Bills in
- API credits
- Entry paid plan
- Build — $49/month, 80M API credits
- Free option
- A one-month free trial rather than a permanent free tier — 10,000,000 API credits at 15 requests per second, no card required.
- Bittensor
- Not listed on its chains page
Every QuickNode figure on this page was read from www.quicknode.com/pricing on . Providers change pricing without notice — check the source before deciding. QuickNode is a trademark of its owner; Iteradian is not affiliated with QuickNode.
Why teams pick Iteradian over QuickNode
No credit multipliers
One request is one request. Moving to heavier methods changes your latency, not your invoice.
A lower first step
The entry plan starts below QuickNode’s $49 Build plan, with a 7-day trial and no card to start.
Bittensor included
Subtensor mainnet over native Substrate JSON-RPC, on every plan. QuickNode does not list Bittensor.
Side by side
| Feature | Iteradian | QuickNode |
|---|---|---|
| Billing unit | Requests — one call is one request | API credits |
| Heavy methods cost more? | No — every call counts as one request | Yes — cost depends on the method |
| Entry paid plan | Developer RPC: $39/month for 25,000,000 requests | Build — $49/month, 80M API credits · 50 requests/second |
| Free option | Free | A one-month free trial rather than a permanent free tier — 10,000,000 API credits at 15 requests per second, no card required. |
| Past the allowance | $0.005 per 1,000 requests, capped at $150 per period, then HTTP 429 | $0.62 per 1M additional API credits on Build, falling to $0.50 on Business. Additional usage above $200 is billed immediately. Annual billing is discounted. |
| Bittensor | Native Subtensor JSON-RPC, every plan | Not listed on its chains page |
| Networks | 12 in the catalogue, all on every plan | QuickNode states 79 chains and 138 networks |
| Per-key controls | IP allowlist (up to 50), allowed networks, rate limit and expiry on every key | Not stated on the pages we read |
| Failover | Health-checked; a failed read tries up to 3 nodes | Not stated on the pages we read |
How the bill is built
How QuickNode bills
QuickNode bills in API credits, and heavier methods consume more of them than a simple block-number read. The same traffic can cost very different amounts depending on the methods behind it.
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 | — | — |
QuickNode
| Plan | Price | Included | Throughput |
|---|---|---|---|
| Free trial | $0 (1 month) | 10M API credits | 15 requests/second |
| Build | $49/mo | 80M API credits | 50 requests/second |
| Accelerate | $249/mo | 450M API credits | 125 requests/second |
| Scale | $499/mo | 950M API credits | 250 requests/second |
| Business | From $999/mo | 2B API credits | 500 requests/second |
| Enterprise | Custom | Custom | Custom, dedicated clusters |
Where each one is strong
What QuickNode does well
- A wide self-serve ladder, from $49 up to Business+ tiers, before Enterprise.
- A published support response time on paid plans, from 24 hours on Build.
- WebSockets, streams, webhooks and IPFS alongside RPC, across 79 chains.
- Dedicated clusters and contractual uptime SLAs on Enterprise.
Where Iteradian differs
- Iteradian meters requests, not credits, so a trace-heavy workload does not cost several times more than a read-heavy one.
- Iteradian serves Bittensor, which QuickNode does not list.
- QuickNode publishes a support response time on paid plans. Iteradian offers email support and in-app tickets, and agrees SLA terms only on Dedicated.
Choose QuickNode when…
You need streams or IPFS, a published support response time on a low-cost plan, dedicated clusters with an uptime SLA, or 79 chains under one account.
Choose Iteradian when…
You want request-based metering instead of credit multipliers, you need Bittensor, or your volume fits an entry plan below $49.
Start the trialQuestions people ask
Is Iteradian cheaper than QuickNode?
It depends on your method mix, because the two meter differently. QuickNode bills in API credits, 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 QuickNode have a free tier?
A one-month free trial rather than a permanent free tier — 10,000,000 API credits at 15 requests per second, no card required.
Does QuickNode support Bittensor?
On the pages we read: Not listed on its chains page. Iteradian serves Bittensor’s native Subtensor JSON-RPC on every plan, alongside the other networks in its 12-network catalogue.
When should I choose QuickNode over Iteradian?
You need streams or IPFS, a published support response time on a low-cost plan, dedicated clusters with an uptime SLA, or 79 chains under one account.