Gelato

• Name: Gelato
• URL: https://gelato.cloud/
• Category: wallet-and-chain middleware product family / relayer-paymaster-bundler stack / rollup-and-RPC platform
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: Gelato is best kept as the umbrella product-family note for the public Gelato stack: Turbo Relayer, Paymaster & Bundler, Rollup-as-a-Service, Private RPCs, VRF, and Web3 Functions. The separate operator boundary now lives in gelato, which is the cleaner place to reason about API-key issuance, dashboard and billing control, hosted relayer / bundler / paymaster / RPC operation, and the company-run rollup-management shell. Keep this note on the feature bundle developers integrate.
• What it does:
  • Provides Turbo Relayer / gasless transaction tooling for sponsored, token-paid, native-paid, sync, async, and multichain execution flows
  • Offers Paymaster & Bundler infrastructure for ERC-4337 and EIP-7702 smart-account traffic, including GasTank-based sponsorship and account-abstraction routing
  • Sells Rollup-as-a-Service for OP Stack, Arbitrum Orbit, and ABC Stack deployments with managed hosting and native integrations into Gelato middleware
  • Exposes authenticated Private RPCs plus adjacent VRF and Web3 Functions products under the same developer platform umbrella
  • Maintains public docs, SDKs, examples, and GitHub materials that make the stack legible as more than one narrow relayer product
• Key claims:
  • The homepage positions Gelato as Smart wallet and rollup infra in one place, which is a strong first-party signal that the product surface is intentionally broader than automation or bundling alone
  • The same homepage says developers can manage their onchain experience through one integration, one bill, one dashboard, one API, which is useful product framing even before shifting to the company note because it shows the stack is meant to be adopted as one integrated bundle
  • Gelato’s docs llms.txt lays out a multi-product platform spanning Turbo Relayer, Paymaster & Bundler, RaaS, Private RPCs, VRF, and Web3 Functions, which is the cleanest product-map summary in one place
  • The docs make the transaction layer unusually concrete: relayer methods cover fee quotes, async and sync submission, status tracking, and multichain batching rather than only a vague gasless UX claim
  • The RaaS docs show that Gelato is not just wallet middleware: it also packages rollup deployment, hosting, and management with native integrations into its other middleware surfaces and 23+ third-party infra providers
  • Public GitHub materials reinforce that the stack is shipped software plus hosted workflow, not merely a marketing wrapper over one API
• Whitepaper: No single canonical whitepaper or litepaper is the important artifact here. The strongest primary materials were Gelato’s homepage, docs index, relayer docs, paymaster docs, RaaS docs, Private RPC docs, and the earlier source capture in ../whitepapers/gelato-primary-sources-2026-04-25.md.
• Sources:
  • https://gelato.cloud/
  • https://docs.gelato.cloud/llms.txt
  • https://docs.gelato.cloud/gasless-with-relay/gelato-turbo-relayer/overview
  • https://docs.gelato.cloud/paymaster-&-bundler/gelato-bundler-paymaster/overview
  • https://docs.gelato.cloud/rollup-as-a-service/introduction
  • https://docs.gelato.cloud/private-rpcs/introduction
  • https://github.com/gelatodigital

Internal linkages

• Separate the product-family lens from the operator lens: use gelato when the question is who issues API keys, runs the dashboard and billing shell, hosts relayers / bundlers / private RPCs, or packages rollup operations under one vendor boundary.
• Strongest adjacent comparison points: pimlico, openfort, and caldera.
• Useful cut: Gelato is the integrated product family in this cluster, not a neutral protocol primitive.

Product / company boundary

• Keep this project note on the public feature bundle developers compare: gasless transactions, account-abstraction routing, rollup deployment, authenticated RPC, randomness, and automation helpers.
• Use gelato when the sharper question is who controls credentials, hosted execution paths, sponsorship workflow, status publication, billing, managed infrastructure, and third-party-provider composition around that bundle.
• That split matters because the features are real, but the easiest production path still runs through one company-shaped operating shell.

Control surface

• Product-level leverage sits in which execution paths Gelato makes easy by default: sponsorship, ERC-20 gas payments, smart-account routing, transaction batching, authenticated RPC access, and rollup stack composition.

• Some of that leverage is inseparable from the operator layer because the company runs the endpoints, dashboard, billing shell, and much of the hosted path. That is why gelato belongs beside this note.

• Read Gelato first as a bundled middleware stack spanning wallet-side execution and chain-side operations. The key analytical question is which pieces remain product-comparison surfaces and which harden into company-shaped workflow dependencies.

• Last reviewed: 2026-08-09 UTC