Gelato

• Name: Gelato
• URL: https://gelato.cloud/
• Category: wallet-and-chain middleware company / hosted relayer-paymaster-bundler operator / rollup-operations vendor
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: Gelato belongs in companies/ because the useful question is not only what product modules does Gelato expose? A named operator issues the API keys, runs the dashboard and billing shell, hosts the relayer / bundler / paymaster / private-RPC surfaces, and packages rollup deployment plus managed infrastructure under one account relationship. The homepage’s one integration, one bill, one dashboard, one API framing is the important taxonomy clue: the practical leverage sits with the company-run control plane, not with a neutral protocol primitive.
• What it does:
  • Operates Turbo Relayer / gasless transaction infrastructure across EVM, Solana, and TRON-facing product paths with sponsored, token-paid, native-paid, sync, async, and multichain transaction flows
  • Hosts 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 hosted management and native integrations into Gelato’s other middleware products
  • Provides authenticated Private RPC endpoints and adjacent infrastructure surfaces such as VRF and Web3 Functions under the same platform umbrella
  • Packages the entire stack through app.gelato.cloud, public docs, and one vendor relationship rather than as separable neutral network components
• Key claims:
  • The homepage explicitly pitches Gelato as Smart wallet and rollup infra in one place and then says developers can Manage your entire onchain experience from one platform with one integration, one bill, one dashboard, one API, which is unusually direct operator-boundary language
  • The same homepage routes users to Get Your API Key at app.gelato.cloud/relay, which is a concrete clue that production use flows through a company-run credential and dashboard shell rather than only through open protocol participation
  • Gelato’s docs llms.txt presents the platform as one documentation surface spanning Turbo Relayer, Paymaster & Bundler, Rollup as a Service, Private RPCs, VRF, and Web3 Functions, reinforcing that the practical dependency is on one integrated vendor stack
  • That same docs index points developers to the dashboard at https://app.gelato.cloud and documents a relayer API at https://api.gelato.digital, which makes the hosted ingress and routing boundary concrete
  • The relayer docs describe async, sync, and multichain transaction flows plus status tracking, fee quoting, and webhook-oriented lifecycle handling, which means transaction origination and state publication can remain vendor-shaped even when the final execution settles elsewhere
  • The RaaS docs say Gelato provides tools for deploying, hosting, and managing Ethereum rollups and integrates with Gelato middleware plus 23+ third-party infrastructure providers, which is important because it shows the company can shape both the wallet-side and chain-side defaults inside one commercial shell
  • The Private RPC docs frame the RPC layer as authenticated endpoints with elastic scaling and no rate limits, which is another sign that ordinary chain access can harden around Gelato-managed accounts, policies, and endpoint provisioning rather than around a neutral public network
• Whitepaper: No classic company whitepaper is the useful artifact here. The strongest primary materials are Gelato’s homepage, docs index, product 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

• Product-family companion: gelato.
• Strongest adjacent company reads: alchemy, openfort, and caldera.
• Reusable lens: when one vendor sells the first user transaction, the account-abstraction path, the private RPC, and part of the managed chain stack under one dashboard, the company boundary usually matters more than the product labels do individually.

Protocol / company boundary

• Keep gelato on the public product family: Turbo Relayer, Paymaster & Bundler, RaaS, Private RPCs, VRF, and Web3 Functions as the things developers evaluate functionally.
• Keep this entity note on the named operator boundary: API-key issuance, dashboard and billing authority, relayer and bundler routing, sponsorship workflow, hosted RPC exposure, rollup hosting, and third-party-provider composition inside Gelato’s managed environment.
• That split matters because Gelato is not most usefully analyzed as a neutral protocol. The practical question is who runs the integrated execution-and-operations shell developers end up depending on in production.

Control surface

• Practical leverage sits in API-key issuance, dashboard administration, sponsorship funding and policy, relayer routing, bundler and paymaster availability, supported-chain and payment-token exposure, webhook and status-truth publication, private-RPC provisioning, and rollup-hosting defaults.

• Additional leverage sits in the bundle itself: teams can let the same vendor shape wallet onboarding, transaction delivery, authenticated RPC access, and chain-operations posture instead of choosing those dependencies independently.

• The result is not Gelato controls the protocol so much as Gelato can become the default operator boundary around several otherwise-separable control surfaces at once.

• Read Gelato as a company-run execution-policy and rollup-operations control plane, not as a neutral middleware primitive.

• Last reviewed: 2026-08-09 UTC