Provider at a glance
- Category
- RPC & Node Services
- Entity
- All 4 Tenderly products
- Official website
- tenderly.co
Independent rankingchecked How it works
Details
Scored 45 out of 100 under methodology 2026.10.18, from the evidence read in October 2026.
Tenderly Node
RPC with debugging tools
RPC & Node Services
#9 Overall
Ranked #9 of 9 RPC & node services in the published ranking
45
ChainChoice Score
The ChainChoice Score, shown against 100: published scores run from 41 to 99.- High evidence confidence
Is Tenderly Node right for you?
Look elsewhere if these come first
- Real cost per 1M identical calls1/10 here; Infura (Consensys) scores 6
- Documented incident record and chain coverage5/10 here; QuickNode scores 7
- Archive debug and trace access1/10 here; Ankr scores 7
- Published throughput and self-serve ceiling1/10 here; Ankr scores 7
Not yet tested for your country. Markets it lists: Global.
to test where you can use it.
The rank above is the published one, the same for every reader. Find my best RPC provider shows where it lands for you.
What will Tenderly Node cost you?
Not priced on this basis
- Usage per month
- 10
How safe is Tenderly Node?
- Evidence: verified4 of 4 criteria rest on quoted, sourced receipts. Read October 2026.
- LicenceMiCA (EU): no register record on file here.
Alternatives to Tenderly Node
Compare all 4- 6QuickNode20 points above · stronger on real cost per million calls (4 against 1)65$662
- 7Ankr14 points above · stronger on archive and trace access (7 against 1)59$12
- 8Infura (Consensys)14 points above · stronger on real cost per million calls (6 against 1)59$0.00
For your setup
Find out if Tenderly Node fits you
The rank above is the published one — the same for every visitor. Answer the category's questions and this section shows where Tenderly Node lands for you, which criteria your answers weight up, and which stated needs the record does or does not meet. The published rank stays beside it.
- A few questions
- No account required
- Ranking-blind: no commercial input
- Personalised in under 60 seconds
Find my best RPC providerNothing is inferred from clicks, popularity or commercial value.
Why this rank
Why Tenderly Node ranks #9
Each strength is read from evidence on a 0–10 ladder and weighted as the published methodology states. The 32 objective points these produce (6.4 here) sit inside the score; availability, friction, trust record and measured data add the rest.
4 published criteria · Σ weight 100
CriterionWeightStrength · 0–10ScoreContrib.MedianBestRankEvidence
351+1.126.010#9/9Loading evidence…
201+0.645.07#9/9Loading evidence…
201+0.646.09#9/9Loading evidence…
255+4.005.07#5/9Loading evidence…
Hairline = best in this ranking · tick = its median · a missing bar is "not scored", never zero
Margin−14behind Infura (Consensys), #8
RobustnessHoldsacross a one-point change to each of its 4 criterion scores, the re-run scores 43–47 and stays #9
Evidence4 of 4 scored4 quoted, 4 with a source link
What would move the rank
Each line is the ranking run again with one of Tenderly Node’s criterion scores changed and every other value held: the smallest whole-point change on that criterion that moves its rank, and where the re-run puts it. Up to 4 climbs and 3 falls are listed, smallest change first. Nothing here is a forecast.
Real cost per 1M identical calls 1 → 8 on its ladder · passes Infura (Consensys)+760#9 → #7
Smallest climb: real cost per 1M identical calls 1 → 8 passes Infura (Consensys), #8.
Strengths
0 from the score dataWhere it leads
No scored criterion is at or within one point of the category best, so no strength can be stated from the data.
Tradeoffs
4 from the score dataWhere it trails
Not for readers who put first
- Real cost per 1M identical calls — 1/10 against a category best of 10/10
- Documented incident record and chain coverage — 5/10 against a category best of 7/10
- Archive debug and trace access — 1/10 against a category best of 7/10
- Published throughput and self-serve ceiling — 1/10 against a category best of 9/10
Record watch-outs
- You cannot budget this without a sales call. The pricing page has no dollar figure for new customers ('One contract. One invoice. No tiers.'), while its FAQ still lists legacy Starter and Pro entitlements (35M TUs at 20 TU/s and 350M TUs at 300 TU/s, auto-scaling at $10 per 1M TU) that only existing subscribers keep. Node RPC is also excluded from the Free plan entirely, so unlike every other provider here you cannot test the RPC before signing. Buy Tenderly for the simulator and debugger; treat the RPC as an add-on to that relationship, not as a price-competitive endpoint.
Competitive position
Where Tenderly Node leads and where it trails
Rank on every objective dimension among the rows scored on it. A criterion in the top third of its pool is listed as a lead, the bottom third as a trail; the middle is neither. Popularity, size and commercial terms are not dimensions.
Availability#1 / 914.0 of 20 · constant here
Published criteria#9 / 94.8 of 30 · best 18.6
Friction#1 / 92.7 of 10 · constant here
Trust record#1 / 93.2 of 8 · constant here
Measured data#1 / 98.3 of 18 · constant here
Where Tenderly Node leadsNo criterion in the top third of its pool.
Where it trails
- Real cost per 1M identical calls#9 / 9
- Archive debug and trace access#9 / 9
- Published throughput and self-serve ceiling#9 / 9
Closest alternatives
The 3 nearest rows by score
Nearest by published score in either direction. Each card states the criteria on which the two rows differ and the cost difference under the same scenario inputs; the compare arithmetic below shows why the higher one ranks higher.
Infura (Consensys)#8 of 9 · score 59 · 14.0 points ahead
Tenderly Node leads on
- Documented incident record and chain coverage5 vs 3
Infura (Consensys) leads on
- Real cost per 1M identical calls6 vs 1
- Archive debug and trace access4 vs 1
- Published throughput and self-serve ceiling3 vs 1
Largest single reason Infura (Consensys) is ahead: published criteria (+14.0 display points).Scenario cost: Tenderly Node has no verified pricing for this scenario.
Ankr#7 of 9 · score 59 · 14.0 points ahead
Tenderly Node leads on
- Documented incident record and chain coverage5 vs 3
Ankr leads on
- Real cost per 1M identical calls2 vs 1
- Archive debug and trace access7 vs 1
- Published throughput and self-serve ceiling7 vs 1
Largest single reason Ankr is ahead: published criteria (+14.0 display points).Scenario cost: Tenderly Node has no verified pricing for this scenario.
QuickNode#6 of 9 · score 65 · 20.0 points ahead
Tenderly Node leads onNo scored criterion
QuickNode leads on
- Real cost per 1M identical calls4 vs 1
- Archive debug and trace access6 vs 1
- Published throughput and self-serve ceiling4 vs 1
Largest single reason QuickNode is ahead: published criteria (+19.8 display points).Scenario cost: Tenderly Node has no verified pricing for this scenario.
Against the leader
81 vs 45 · gap 36.0Why BlockPI ranks above Tenderly Node
The compare workspace's arithmetic applied to these two rows. Each dimension's share of the gap is its weight × the difference, on the displayed scale — it reproduces the displayed gap of 36.0 to within rounding.
DimensionThisBlockPIGap share
Availability · 23% weight · constant here14.014.0same
Published criteria · 35% weight4.818.6−35.9, worse
Friction · 12% weight · constant here2.72.7same
Trust record · 9% weight · constant here3.23.2same
Measured data · 21% weight · constant here8.38.3same
Published criterionThisBlockPIPoints
Real cost per 1M identical calls · w35110−10.08, worse
Archive debug and trace access · w2016−3.20, worse
Published throughput and self-serve ceiling · w2019−5.12, worse
Net4581−36.0
Your scenario
Tenderly Node is not priced for this scenario
Metered usage beyond whatever the plan includes, for a year. Excludes egress, support tiers and enterprise minimums. Change an input and every figure recomputes from the published rate; the published rank does not move.
your cost/yr · default scenario — set your own
Usage per month · your input10
Rate read from the provider’s published pricing ↗ on 22 October 2026.
your cost/yrCost is stated as your cost/yr in USD; it is never a yield, never annualised, and it does not enter the score.
Not priced on this basis
Under the default inputs · USDCategory median$3328 of 9 rows priced
Cheapest priced$0.00 · Infura (Consensys)Difference not stated · availability not applied — set your country to filterCompare with Infura (Consensys)
1 of 9 rows in this ranking have no verified rate for this scenario and are absent from the median, not counted as free.
Evidence
Evidence read 22 October 2026
One row per published criterion: the page each strength was read from, its source type by domain, the reading date and whether the file and the published table agree. Open a row for the quote and the receipt.
4 of 4 cells scored
Score evidenceVerified4 of 4 criteria reconstruct from receipts
4 of 4 criteria reconstruct from a quoted, sourced receipt equal to the published strength.Public receiptsReading…4 quoted with a source URL
The receipt file has not been read yet.Evidence confidenceHighcoverage and corroboration, never freshness
4/4 criteria scored, with 4 dated sources quoted.RobustnessHoldsrank #9 across every one-point re-run
Whether the position holds when one criterion score is changed by one point and the ranking is run again. It is always a re-run of the ranking, never an estimate.The newest evidence read on the platform is 3 November 2026; this category's reading is older. The scores stand as read on 22 October 2026.
Reading the evidence ledger…
CriterionSourceTypeReadFreshnessStatusReceipt
Real cost per 1M identical callsstrength 1 · weight 35Report an error—22 October 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.Archive debug and trace accessstrength 1 · weight 20Report an error—22 October 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.Published throughput and self-serve ceilingstrength 1 · weight 20Report an error—22 October 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.Documented incident record and chain coveragestrength 5 · weight 25Report an error—22 October 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.How you can lose money here, and what the ranking scores
- Liveness failure (Tenderly Node 5/10): the operator stops, censors you or loses data.Scored by Documented incident record and chain coverage · 25%
Not assessed by this ranking: Exit failure, Information failure. A high place says nothing about these; the Methodology tab says what each means. Also scored, as cost, quality or a summary of several families: Real cost per 1M identical calls (35%), Archive debug and trace access (20%), Published throughput and self-serve ceiling (20%).
Facts
facts, not scoresWhat the record publishes
- Pricing
- Tenderly pricing page (tenderly.co/pricing, rendered in a browser because curl gets a 429 Vercel checkpoint), read 22 October 2026 for the 21 October 2026 re-read; unchanged since 14 September 2026. No dollar price is published for Node RPC for new customers. "Tenderly Free": "No credit card. No trial. Free, indefinitely."; "Use Tenderly in the browser. No API access on Free." "Tenderly Console": "One contract. One invoice. No tiers."; "Capacity, support, and chain count are sized in conversation." via Contact Sales; Node RPC "Historical archive access" "6 months / 2 years / full". Docs (docs.tenderly.co/node/pricing.md): "Node RPC is available on paid plans only. The Free plan does not include Node RPC access." TU per request: Read 1, Compute 4 (eth_call), Write 20, Debug and Trace 40, Advanced Compute 1 40, Advanced Compute 2 400. Legacy-only entitlements (pricing FAQ): Starter "35M TUs, 20 TU/s, auto-scaling ($10/1M TU), EU West"; Pro "350M TUs, 300 TU/s, auto-scaling ($10/1M TU), multi-region support".Tenderly Node — official pricing page ↗ · 22 October 2026
- Prices published in
- USDTenderly Node — official pricing page ↗ · 22 October 2026
- Licences held
- Not published
- Compliance level
- partial
- Regulatory note
- Not published
- Supported chains
- Multi-chain
- Markets served
- global
- Primary markets
- Not published
- Restricted markets
- Not published
- Operating limits
- Not published
- Availability note
- Tenderly's Terms of Service (tenderly.co/terms-of-service, "Effective Date: June 8, 2026", read 22 October 2026), section 9.7, bar export "to any destinations prohibited by the government of the U.S.A. or to any Specially Designated Nationals or other denied or blocked parties"; the terms name no country. Global, sales-led.
Legal entity on file: Tenderly, placed in 4 products. Only confirmed entities are shown; nothing is inferred from the brand name.
If something goes wrong with Tenderly Node: where to complain, and where to report a scam
Loading the routes for your country.
How this page is reviewed
Reviewed means this product in this category was read against its sources on or after that date; every ranked category is re-read at least every 45 days. Models research, extract and parse. A deterministic engine ranks. Every quote passes an adversarial refute pass.
Accountable for this review: Mathias Siemonsmeier, Founder.
How we review · Review calendar · Corrections log · How we make money
History
What the record carries
Changes to published ranks are recorded in a ledger; every step and its cause is listed on the rank-history page. The entries below begin with the current verified snapshot, then the methodology versions whose changes applied to this category, newest first.
9 methodology entries
- 22 October 2026Current verified snapshot · methodology 2026.10.18Score 45, #9 of 9. 4 of 4 criteria scored. History starts here; earlier values are not interpolated.
- 10 October 2026
2026.10.8When nothing serves your country, the list shown for reference is the published ranking · platform-wide- fixed The reference list shown when nothing serves your country is the published order with the published scores, and a build check now fails any such list out of that order or with a score the ranking does not publish.
- fixed The explorer prints an overall rank only for a row the published ranking holds; a country entrant such as Coinbase Commerce for US merchants shows no overall rank.
- changed Published orders do not move. Country results change only where nothing serves the country: in India bill pay keeps Bitcoin Well first and now shows Strike second, as published; 35 such runs across all categories and countries now match the published list exactly.
- 10 October 2026
2026.10.6A criterion you require re-scores the rows that meet it · platform-wide- changed The explorer sends each criterion you require, at any band, as fit_required with your other answers; region, licence, chain and fact filters stay filters. On /best, a required criterion joins For you as a marked preference does, which needs your country; Overall stays the published ranking, filtered.
- added Every published criterion has a golden case as the explorer sends it (require:<criterion>), so the order a requirement gives is replayed and gated as the published order is, and a change to it needs an entry here.
- 16 September 2026
2026.09.15Dimension scores carry tenths, and eleven more categories are re-read from primary sources · platform-wide- changed Dimension scores resolve to tenths of a point (O-04b), and weightedTotal is rounded to six decimal places before the order is read. 518 published scores move across 107 categories that were not re-read; none of them moves by more than 4 points, and most move by 1.
- fixed 66 published scores change in the eleven re-read categories, against a verbatim source each. The largest moves are Reflexer RAI (−16), Beefy and Unrekt (−11), Aztec (−10) and Golem (+9) — all of them rows whose sources had moved since their last read.
- changed Published order moves in 38 of 119 categories and three #1s change: smart_contract_audits (Zellic → Certora) and travel_rule_compliance (Sumsub Travel Rule → CodeVASP) on the finer resolution, kyc_compliance (Veriff → Sumsub) on the re-read.
- added availabilitySource (O-04g): for a reader who states a country, a row whose availability in that country rests on a region tag its record gives no source for sorts below every sourced row. It is inert in every order published here, which states no country.
Methodology 2026.10.18, the same published run every visitor sees · receipt rpc_nodes:tenderly_node:2026.10.18:a6f69a8367c9
Are you Tenderly Node? Reply to this verdict, or send evidence, ask for a correction or claim the listing. Every message gets a public ticket number; none of it changes a rank unless a public page or a signed statement supports it.