Gelato

• Name: Gelato
• URL: https://gelato.cloud/
• Category: Smart wallet / gasless UX / rollup-as-a-service / web3 infrastructure platform
• Tags: ethereum-ecosystem
• Summary: Gelato is a vendor stack that bundles sponsored wallet execution and managed rollup operations under one roof. The point is not that it has many products. The point is that paymaster policy, relay defaults, private RPC posture, and chain-operations configuration can all accumulate under the same operator.
• What it does:
  • Provides Paymaster & Bundler infrastructure for ERC-4337 and EIP-7702 account-abstraction flows, including gas sponsorship and token-based gas payments
  • Offers gasless transaction infrastructure via relay products and related SDK/API flows across EVM and other supported environments documented in its docs index
  • Runs Rollup-as-a-Service infrastructure for deploying, hosting, and managing OP Stack, Arbitrum Orbit, and ABC Stack rollups with multiple data-availability options
  • Maintains adjacent infrastructure products such as private RPCs, VRF, automation/web3 functions, and open-source SDK/example repositories
• Key claims:
  • Homepage markets Gelato as “Smart wallet and rollup infra in one place” and says developers can launch gasless onboarding, smart wallets, and custom rollups from one SDK
  • Official docs index describes Gelato as a “comprehensive Web3 infrastructure platform” spanning gasless transactions, account abstraction, rollup deployment, and blockchain infrastructure services
  • Paymaster & Bundler docs say Gelato supports both ERC-4337 and EIP-7702, with sponsorship, ERC-20 gas payments, and compatibility with multiple smart-account and embedded-wallet providers
  • Rollup docs say Gelato RaaS supports deployment, hosting, and management of optimistic and zero-knowledge rollup stacks, integrates with Gelato middleware, and exposes a marketplace of third-party infra integrations
  • Public GitHub repositories show active SDKs, gasless tooling, automation contracts, and rollup how-to repos, reinforcing that Gelato operates as a broad developer control plane rather than a single-purpose relayer product
• Whitepaper: No single canonical whitepaper or litepaper was found in this pass. The strongest primary materials were Gelato’s homepage, docs index (llms.txt), Paymaster & Bundler docs, Rollup-as-a-Service docs, and public GitHub repositories; see ../whitepapers/gelato-primary-sources-2026-04-25.md.
• Sources:
  • https://gelato.cloud/
  • https://docs.gelato.cloud/
  • https://docs.gelato.cloud/llms.txt
  • https://docs.gelato.cloud/paymaster-&-bundler/gelato-bundler-paymaster/overview
  • https://docs.gelato.cloud/rollup-as-a-service/introduction
  • https://github.com/gelatodigital

Internal linkages

• Best adjacent reads: pimlico, alchemy, and caldera.
• Reusable lens: Gelato matters when one vendor tries to own both sponsored execution for users and managed operations for chains.

Control surface

• User execution still lands on external chains and contracts. Gelato’s leverage sits in paymaster policy, bundler routing, relay retries, private RPC posture, automation triggers, and rollup deployment / hosting defaults.
• The point is not just that Gelato offers many products. It is that wallet-side sponsored execution and chain-side managed operations can harden into one vendor dependency.

Comparable to / differs from

• Comparable to: Pimlico and Alchemy on the wallet-control side, and Caldera on the managed-rollup side.
• Differs from: narrower bundler-only components or execution venues themselves. Gelato matters because it packages both the wallet-side operator layer and the chain-ops layer.

Governance / control risk

• Practical authority can sit in paymaster admission, sponsored-call policy, relay and retry logic, chain-support defaults, private RPC behavior, and the managed configuration choices embedded into rollup deployments.
• So the real dependency is not a single SDK feature. It is the bundled operator stack behind user execution and chain operations.

Rent / leverage sink

• Gelato can collect leverage at two levels at once: the user-execution layer where sponsorship and relaying decide how easily actions get onto a chain, and the chain-operations layer where hosting and configuration defaults define how that chain runs.

• The interesting rent sink is therefore the combined wallet-plus-rollup middleware dependency, not just any one SDK or relayer endpoint.

• Last reviewed: 2026-06-02 UTC