Provider at a glance
- Category
- Relayers
- Entity
- All 2 Gelato products
- Official website
- docs.gelato.cloud
Independent rankingchecked How it works
Details
Scored 59 out of 100 under methodology 2026.10.18, from the evidence read in August 2026.
Gelato Relay
Hosted meta-transaction relay
Relayers
#7 Overall
Ranked #7 of 7 relayers in the published ranking
59
ChainChoice Score
The ChainChoice Score, shown against 100: published scores run from 41 to 99.- High evidence confidence
Is Gelato Relay right for you?
Look elsewhere if these come first
- What the relayer is authorised to do, and whether you can keep the address7/10 here; Sequence Transactions API (Relayer) scores 9
- Exactly-once execution and stuck-queue recovery4/10 here; Circle Gas Station scores 7
- What a stolen API credential can do before anyone notices6/10 here; the category best is 10
- Where the gas float sits and how you get it back2/10 here; Circle Gas Station scores 8
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 relayer service shows where it lands for you.
What will Gelato Relay cost you?
Not priced on this basis
- Usage per month
- 10
How safe is Gelato Relay?
- Evidence: verified4 of 4 criteria rest on quoted, sourced receipts. Read August 2026.
- LicenceMiCA (EU): no register record on file here.
Alternatives to Gelato Relay
Compare all 4- 4Sequence Transactions API (Relayer)14 points above · stronger on gas float custody (7 against 2)73
- 5Circle Gas Station11 points above · stronger on gas float custody (8 against 2)70
- 6Openfort backend wallets10 points above · stronger on gas float custody (7 against 2)69
For your setup
Find out if Gelato Relay fits you
The rank above is the published one — the same for every visitor. Answer the category's questions and this section shows where Gelato Relay 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 relayer serviceNothing is inferred from clicks, popularity or commercial value.
Why this rank
Why Gelato Relay ranks #7
Each strength is read from evidence on a 0–10 ladder and weighted as the published methodology states. The 32 objective points these produce (16.0 here) sit inside the score; availability, friction, trust record and measured data add the rest.
4 published criteria · Σ weight 100
CriterionWeightStrength · 0–10ScoreContrib.MedianBestRankEvidence
327+7.179.010#6/7Loading evidence…
264+3.336.07#6/7Loading evidence…
226+4.226.010#3/7Loading evidence…
202+1.287.09#7/7Loading evidence…
Hairline = best in this ranking · tick = its median · a missing bar is "not scored", never zero
Margin−10behind Openfort backend wallets, #6
RobustnessHoldsacross a one-point change to each of its 4 criterion scores, the re-run scores 57–61 and stays #7
Evidence4 of 4 scored4 quoted, 4 with a source link
What would move the rank
The ranking was run again with each of Gelato Relay’s criterion scores changed on its own, as far as each ladder goes in both directions. None of those changes moves its rank.
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
- What the relayer is authorised to do, and whether you can keep the address — 7/10 against a category best of 10/10
- Exactly-once execution and stuck-queue recovery — 4/10 against a category best of 7/10
- What a stolen API credential can do before anyone notices — 6/10 against a category best of 10/10
- Where the gas float sits and how you get it back — 2/10 against a category best of 9/10
Record watch-outs
- Money goes into the Gas Tank and does not come out: "It's important to remember that the current Gas Tank system does not support withdrawals after depositing funds." On 2026-08-11 that sentence was published on a Gelato VRF integration guide, not on any relay page and not on the Gas Tank page the relay setup guide linked to — which documented depositing in five steps and never mentioned withdrawal. Gelato was simultaneously closing every alternative: three separate migration notices deprecated the trusted forwarder, the SyncFee pattern and the Relay SDK, and the last of these stated that the replacement SDK "only supports sponsored transactions." A relay buyer was therefore being funnelled onto a vendor-held, Polygon-only USDC float with no published way to retrieve the unused remainder and no statement of what happens to it on termination. On 2026-09-28 none of this could be re-read: every docs.gelato.cloud path returned HTTP 404, the relay API refused TLS connections, and gelato.cloud/relay redirected to Paymaster & Bundler, whose page states no withdrawal or residue terms.
Competitive position
Where Gelato Relay 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 / 714.0 of 20 · constant here
Published criteria#7 / 712.0 of 30 · best 20.4
Friction#1 / 72.7 of 10 · constant here
Trust record#1 / 73.2 of 8 · constant here
Measured data#1 / 78.3 of 18 · constant here
Where Gelato Relay leads
- What a stolen API credential can do before anyone notices#3 / 7
Where it trails
- What the relayer is authorised to do, and whether you can keep the address#6 / 7
- Exactly-once execution and stuck-queue recovery#6 / 7
- Where the gas float sits and how you get it back#7 / 7
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.
Openfort backend wallets#6 of 7 · score 69 · 10.0 points ahead
Gelato Relay leads onNo scored criterion
Openfort backend wallets leads on
- What the relayer is authorised to do, and whether you can keep the address9 vs 7
- Where the gas float sits and how you get it back7 vs 2
Largest single reason Openfort backend wallets is ahead: published criteria (+10.1 display points).Scenario cost: Openfort backend wallets has no verified pricing for this scenario.
Circle Gas Station#5 of 7 · score 70 · 11.0 points ahead
Gelato Relay leads on
- What the relayer is authorised to do, and whether you can keep the address7 vs 6
Circle Gas Station leads on
- Exactly-once execution and stuck-queue recovery7 vs 4
- Where the gas float sits and how you get it back8 vs 2
Largest single reason Circle Gas Station is ahead: published criteria (+10.4 display points).Scenario cost: Circle Gas Station has no verified pricing for this scenario.
Sequence Transactions API (Relayer)#4 of 7 · score 73 · 14.0 points ahead
Gelato Relay leads onNo scored criterion
Sequence Transactions API (Relayer) leads on
- What the relayer is authorised to do, and whether you can keep the address9 vs 7
- Exactly-once execution and stuck-queue recovery6 vs 4
- Where the gas float sits and how you get it back7 vs 2
Largest single reason Sequence Transactions API (Relayer) is ahead: published criteria (+13.5 display points).Scenario cost: Sequence Transactions API (Relayer) has no verified pricing for this scenario.
Against the leader
81 vs 59 · gap 22.0Why Coinbase CDP Server Wallets (API-key wallets) ranks above Gelato Relay
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 22.0 to within rounding.
DimensionThisCoinbase CDP Server Wallets (API-key wallets)Gap share
Availability · 23% weight · constant here14.014.0same
Published criteria · 35% weight12.020.4−21.8, 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 criterionThisCoinbase CDP Server Wallets (API-key wallets)Points
What the relayer is authorised to do, and whether you can keep the address · w3279−2.05, worse
Exactly-once execution and stuck-queue recovery · w2647−2.50, worse
What a stolen API credential can do before anyone notices · w22610−2.82, worse
Where the gas float sits and how you get it back · w2028−3.84, worse
Net5981−22.0
Your scenario
Gelato Relay 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 11 August 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 medianNot priced0 of 7 rows priced
Cheapest pricedNone pricedDifference not stated · availability not applied — set your country to filter
7 of 7 rows in this ranking have no verified rate for this scenario and are absent from the median, not counted as free.
Evidence
Evidence read 11 August 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 #7 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 11 August 2026.
Reading the evidence ledger…
CriterionSourceTypeReadFreshnessStatusReceipt
What the relayer is authorised to do, and whether you can keep the addressstrength 7 · weight 32Report an error—11 August 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.Exactly-once execution and stuck-queue recoverystrength 4 · weight 26Report an error—11 August 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.What a stolen API credential can do before anyone noticesstrength 6 · weight 22Report an error—11 August 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.Where the gas float sits and how you get it backstrength 2 · weight 20Report an error—11 August 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 (Gelato Relay 4/10): the operator stops, censors you or loses data.Scored by Exactly-once execution and stuck-queue recovery · 26%
- Custody failure: whoever holds the assets loses or withholds them.Scored by What the relayer is authorised to do, and whether you can keep the address · 32% (Gelato Relay 7/10)Scored by What a stolen API credential can do before anyone notices · 22% (Gelato Relay 6/10)Scored by Where the gas float sits and how you get it back · 20% (Gelato Relay 2/10)
Not assessed by this ranking: Exit failure. A high place says nothing about these; the Methodology tab says what each means.
Facts
facts, not scoresWhat the record publishes
- Pricing
- Not readable on 2026-10-28: Not readable on 2026-10-28: docs.gelato.cloud (where docs.gelato.network now redirects) fails the TLS handshake with "certificate has expired", so the relay docs, the Gas Tank pages and the API-key pages cannot be read. gelato.cloud (HTTP 200) still sells the relay ("Turbo Relayer ... Accessible through the existing Gelato Relay API.. Last readable on 2026-08-11: No relay-specific price is published, and this page deliberately publishes no cost ranking because Gelato's cost is already published on two sibling pages. The relay documentation's own pricing words defer entirely: "For the most up-to-date information on Relay subscription limits and pricing plans, please visit our dedicated [Pricing Plans page](/pricing/pricing-plans). Here you can find detailed breakdowns of request monthly limits, throughput limits, autoscale options, and dynamic gas premium fees for each of our supported networks." (https://
docs .gelato .cloud /gasless-with-relay /additional-resources /supported-networks — re-fetched as raw markdown and confirmed character-exact 2026-08-11). That linked table is a cross-product compute-unit table, not a relay price, and it is ALREADY QUOTED VERBATIM in the gelato_raas entry on rollup_as_a_service; it is not reprinted here. Unit price and gas markup belong to account_abstraction_infra (publishedUnitPrice 30%, sponsoredGasMarkup 20%) and cost-per-1M-calls belongs to rpc_nodes (35%). One non-price mechanic is in scope and is disclosed: billing is post-paid off receipts — "After the transaction is successful, Gelato can use the transaction receipts to charge you exactly the amount that the transaction costs plus a nominal fee" (https:// docs .gelato .cloud /paymaster- &-bundler /gastank /introduction, confirmed character-exact 11 August 2026).Gelato Relay — official pricing page ↗ · 11 August 2026 - Prices published in
- USDGelato Relay — official pricing page ↗ · 11 August 2026
- Licences held
- Not published
- Compliance level
- partial
- Regulatory note
- Not published
- Supported chains
- Ethereum, Polygon, Polygon zkEVM, Arbitrum, Optimism, Base, BNB, Avalanche, Gnosis, Linea, zkSync Era, Mantle, Metis, Mode, Blast, Zora, Unichain, Ink, Sonic, Story, Berachain, Monad, MegaETH, HyperEVM, Katana, Plasma, Botanix, Rootstock, Filecoin, Flow, Abstract, Zircuit, Lisk, Lumia, Camp, Open Campus, Reya, Playnance, Aleph Zero, Arena-Z, Ethernity, Everclear (prev Connext)
- Markets served
- global
- Primary markets
- Not published
- Restricted markets
- Not published
- Operating limits
- Not published
- Availability note
- Not published
Legal entity on file: Gelato, placed in 2 products. Only confirmed entities are shown; nothing is inferred from the brand name.
If something goes wrong with Gelato Relay: 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
- 11 August 2026Current verified snapshot · methodology 2026.10.18Score 59, #7 of 7. 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 relayers:gelato_relay:2026.10.18:fbde30e17776
Are you Gelato Relay? 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.