Rollups-as-a-Service Explained: Launching a Chain in Minutes

Not long ago, running a rollup meant operating a sequencer, batch poster, proposer, full nodes, archive nodes, RPC endpoints, an indexer and a block explorer, all with high uptime and careful key management. That is a lot of moving parts for a team that really just wants to build a great app.

Rollups-as-a-Service (RaaS) emerged to solve exactly that. RaaS providers take open-source rollup frameworks and run them for you as a managed service. You choose settings in a dashboard or work with their team, and they handle deployment, operations, upgrades and monitoring. For many projects, it is the fastest and most practical way to get a chain into the water.

What a RaaS provider actually does

Offerings vary, but a typical RaaS package includes:

• Chain deployment: spinning up your rollup on a supported framework, such as the OP Stack, Arbitrum Orbit, ZK Stack or Polygon CDK, and deploying the bridge and settlement contracts.
• Sequencer operations: running the component that orders transactions and produces blocks, with redundancy and failover.
• Node and RPC infrastructure: public and private RPC endpoints so wallets, apps and users can talk to your chain.
• Data availability integration: posting data to Ethereum or to alternative DA layers such as Celestia, EigenDA or Avail.
• Ecosystem tooling: block explorers, bridges, faucets, and often integrations with oracles, indexers, account abstraction and wallets.
• Upgrades and maintenance: keeping your chain current as the underlying framework releases new versions and security fixes.
• Monitoring and support: alerting, status pages and an engineering team you can reach when something goes wrong.

Meet the major providers

The RaaS market moves quickly, and offerings change, so treat these as general descriptions and check each provider’s current materials.

Conduit

Conduit is known for running production rollups for a number of well-known chains, with a strong focus on the OP Stack and Arbitrum Orbit. It emphasizes reliability and a self-serve deployment experience alongside enterprise support.

Caldera

Caldera offers managed rollups across several frameworks and has focused on connecting its chains together so that apps and liquidity can move between them more easily. It has been a popular choice for gaming and consumer projects.

AltLayer

AltLayer offers RaaS across multiple stacks and has leaned into restaking-based services that add extra verification, faster finality and decentralized sequencing options on top of standard rollups.

Gelato

Gelato started as a provider of Web3 automation and developer services and expanded into RaaS. Its pitch combines chain deployment with a bundled set of developer tools such as account abstraction, oracles and automation.

Zeeve

Zeeve provides infrastructure for a wide range of blockchains and supports several rollup frameworks as well as appchain and node services, often with an enterprise orientation.

What does RaaS cost?

Pricing changes often and depends heavily on configuration, so we will stick to broad, approximate ranges. Many providers let you start a testnet for something in the range of tens of dollars per month, and some offer free tiers for experimentation. Production mainnets typically run into the thousands of dollars per month for the managed service, and more for high-availability setups, dedicated support or custom features.

That monthly fee is only part of the picture. You also pay variable costs, mainly for data availability and settlement transactions on the parent chain, which scale with activity. Some providers pass these through at cost; others bundle them. Always ask for a clear breakdown of fixed versus variable costs, and model what happens when your traffic grows ten times.

RaaS vs doing it yourself

Reasons to use RaaS

• Speed: testnets in minutes or hours and mainnets in weeks rather than months.
• Expertise: operations teams who have already handled incidents, upgrades and edge cases.
• Bundled ecosystem: explorers, bridges and integrations that would take months to arrange yourself.
• Focus: your engineers can work on your product instead of infrastructure.

Reasons to self-host

• Control: you hold every key and make every operational decision.
• Customization: deep changes to the framework can be easier when you run it yourself.
• Cost at scale: very large chains with strong in-house teams may find self-hosting cheaper over time.
• Regulatory or enterprise requirements: some organizations must run infrastructure in their own environments.

Many teams start with RaaS, learn how their chain behaves in production, and only later consider bringing parts of the stack in-house.

Questions to ask before you sign

1. Which frameworks and DA layers do you support in production today?
2. Who holds the admin, upgrade and sequencer keys, and how are they protected?
3. What are your uptime commitments, and what happens if you miss them?
4. How are framework upgrades and security patches scheduled and communicated?
5. What is included in the base fee, and what is billed separately?
6. Can we migrate to another provider or self-host later, and how?
7. Which bridges, explorers, oracles and wallets are integrated out of the box?
8. How do you handle incidents, and can we see an example post-mortem?

Avoiding lock-in

Because most RaaS providers run open-source frameworks, your chain is generally portable in principle. In practice, migration can be painful if keys, contracts or custom integrations are tightly bound to one provider. Clarify key ownership upfront, keep good documentation of your configuration, and make sure contracts and multisigs are controlled by your organization, not solely by the vendor.

RaaS makes launching easy. It does not make running a successful chain automatic. Ecosystem growth, security discipline and a real use case are still your job.

Is RaaS right for you?

If you are a startup, brand, game studio or community that wants its own chain without building a protocol team, RaaS is very likely the right starting point. If you have strong infrastructure engineers and very specific needs, self-hosting may be worth it. Either way, the existence of mature RaaS options is one of the biggest reasons launching a chain in 2026 is realistic for far more teams than ever before.

Compare providers and stacks in Where to Build, explore Tools, or let WaveChains help you launch and coordinate providers on your behalf.