Caldera is a Rollup-as-a-Service (RaaS) platform that lets development teams deploy production-grade Layer 2 and Layer 3 rollup chains without building or operating the underlying node infrastructure. Teams choose a rollup framework, configure chain parameters, and Caldera handles sequencing, data availability routing, bridge UI, and monitoring. Chains like ApeChain, Plume Network, and Xai Games launched through Caldera.
​

Caldera is a managed infrastructure platform for deploying custom Ethereum rollup chains. It abstracts the engineering complexity of running a rollup sequencer, configuring a data availability layer, and maintaining bridge contracts, so product teams can launch an app-chain in days rather than months. Caldera supports OP Stack, Arbitrum Orbit, and Polygon CDK frameworks.
​

Building a rollup from scratch requires deep expertise in Ethereum client engineering: sequencer design, fraud proof or validity proof systems, DA client integration, and bridge security. Most product teams, whether launching a gaming chain, a DeFi protocol, or an enterprise settlement layer, want a dedicated chain without the DevOps burden. Caldera fills that gap by operating the critical infrastructure and exposing configuration knobs through a deployment interface.
​

The broader Caldera platform covers the full lifecycle: chain deployment, sequencer operation, telemetry dashboards, custom gas token configuration, and cross-chain messaging through its Metalayer. Teams retain ownership of their chain's smart contracts and governance; Caldera handles the operational layer beneath them.
​

The RaaS category emerged after the OP Stack and Arbitrum Orbit frameworks made rollup codebases open source and modular. Optimism released the OP Stack in late 2022; Arbitrum opened Orbit to third-party deployers in mid-2023. Once the hard part shifted from "write the rollup code" to "operate it reliably at scale," infrastructure providers stepped in. Caldera is one of the first RaaS platforms to achieve meaningful ecosystem depth, with dozens of production chains deployed across gaming, DeFi, and enterprise segments as of 2025.
​

Caldera provisions a complete rollup stack on demand. A team selects a rollup framework, chooses a data availability layer, configures chain parameters such as block time and gas token, and Caldera deploys and operates the sequencer, full nodes, bridge contracts, and monitoring stack. The chain settles to Ethereum or an L2 parent depending on the framework choice.
​

The deployment flow works roughly as follows. A team specifies the rollup framework (OP Stack, Arbitrum Orbit, or Polygon CDK), the DA layer (Ethereum calldata, EIP-4844 blobs, Celestia, or EigenDA depending on framework support), and network parameters. Caldera provisions a dedicated sequencer node and a set of full nodes, deploys the bridge and rollup manager contracts to the parent chain, and hands the team RPC endpoints and a block explorer.
​

Once live, Caldera operates the sequencer and monitoring layer. The sequencer batches transactions, posts them to the DA layer, and submits state roots to the parent chain. Caldera's telemetry dashboard exposes block production metrics, sequencer latency, L1 submission costs, and bridge activity. Teams do not need to operate their own nodes to keep the chain running.
​

Custom gas tokens are a frequently used feature. A team can designate any ERC-20 token as the gas token for their chain, so users pay transaction fees in the project's native token rather than ETH. Custom precompiles let teams add chain-specific opcodes or system contracts that accelerate protocol-level operations, such as onchain game logic or privacy computations.
​

Caldera also handles upgrades. When OP Stack or Arbitrum Orbit ships a new release, Caldera coordinates the migration for managed chains, reducing the operational surface teams must track. This is a material advantage for small teams; tracking upstream rollup framework changes is non-trivial engineering work.
​

Caldera supports three rollup frameworks: OP Stack, Arbitrum Orbit, and Polygon CDK. Each framework carries different tradeoffs around EVM compatibility, proof system, data availability options, and ecosystem alignment. The table below summarizes the key dimensions so teams can match a framework to their requirements.
​

The choice of framework affects which bridging infrastructure the chain inherits, which proof system (optimistic or ZK) settles disputes, and which ecosystem tooling works out of the box. Teams targeting the Superchain ecosystem typically choose OP Stack. Teams with existing Arbitrum liquidity relationships often choose Arbitrum Orbit. Teams building ZK-native applications or targeting the Polygon AggLayer may choose Polygon CDK.
​

For a deeper comparison of how optimistic and ZK rollup proof systems differ, see What Is a Rollup: Optimistic vs ZK Rollups. For the specifics of the OP Stack architecture, see What Is the OP Stack.
​

EVM compatibility is high across all three frameworks. OP Stack and Arbitrum Orbit chains are bytecode-compatible with Ethereum mainnet, meaning Solidity contracts deploy without changes. Polygon CDK uses the zkEVM, which is also EVM-equivalent but may have minor opcode differences on edge cases. Development teams with existing Solidity contracts can migrate to any of the three with minimal code changes.
​

The DA layer choice matters for cost and decentralization. Ethereum blob space (EIP-4844) provides the strongest security guarantees but costs more than off-chain DA solutions like Celestia or EigenDA. AnyTrust, used within Arbitrum Orbit, uses a data availability committee model that cuts costs further at the expense of introducing a trusted committee. Teams with high transaction throughput requirements often choose off-chain DA to keep per-transaction fees competitive.
​

Several production chains deployed through Caldera have achieved meaningful user bases and transaction volumes. ApeChain (the official chain for the APE ecosystem), Plume Network (a real-world asset chain), and Xai Games (a gaming-focused L3) are among the most cited examples. Each chose Caldera to reduce time-to-launch and avoid operating bespoke rollup infrastructure.
​

ApeChain is the official Layer 3 for the APE ecosystem, built on Arbitrum Orbit with ApeChain's APE token as the native gas token. The chain targets NFT activity, gaming, and DeFi applications tied to the Bored Ape Yacht Club and adjacent communities. Using Caldera meant the ApeCoin DAO could launch a dedicated settlement environment for its ecosystem without standing up an independent sequencer team. Caldera's deployment tooling handled sequencer provisioning, bridge contracts, and the block explorer.
​

Plume Network is an Ethereum L2 focused on tokenized real-world assets. The chain targets institutional issuers and retail investors who want to hold or trade RWA tokens onchain. Plume chose Caldera to launch its testnet and mainnet faster than a from-scratch build would permit, with the sequencer and monitoring stack handled by Caldera. The real-world asset sector has grown substantially, with RWA.xyz tracking over $10B in tokenized assets across chains as of early 2026, and Plume positions itself as a dedicated settlement layer for that market.
​

Xai Games is an Arbitrum Orbit L3 designed for onchain gaming. It settles to Arbitrum One as its parent chain and uses the AnyTrust DA model to minimize per-transaction costs for game move submissions. The AnyTrust approach is well-suited to gaming workloads because game state transitions are high-frequency and low-value; a trusted DA committee reduces costs without meaningfully degrading security for that use case. Caldera operated the Xai sequencer infrastructure, letting the Xai team focus on game developer integrations rather than node operations. For more on Arbitrum's architecture, see What Is Arbitrum.
​

Manta Pacific, a privacy-focused L2, initially launched through Caldera before migrating its infrastructure to an independent operator setup. The Manta case illustrates a common RaaS lifecycle: teams use a managed provider to launch quickly and validate the chain concept, then optionally take over operations as the team grows and the operational cost-benefit calculates differently. Caldera's architecture is designed to support this transition.
​

The Caldera Metalayer is a cross-chain messaging and liquidity layer that connects chains deployed through Caldera. It enables native asset transfers and contract calls between Caldera-deployed chains without requiring a third-party bridge for every pair. Teams building across multiple Caldera chains can route messages and value through the Metalayer rather than integrating separate bridge protocols.
​

Standard rollup bridges settle through the parent chain: a message from Chain A to Chain B requires submitting a transaction on the parent (e.g., Ethereum or Arbitrum One), waiting for confirmations, and then executing on the destination chain. The latency is proportional to the parent chain's finality window, which for optimistic rollups can be up to seven days for fully trustless exits.
​

The Metalayer reduces this latency for Caldera-to-Caldera transfers by maintaining a shared state view across the connected chains. Rather than routing through the parent on every transfer, the Metalayer can verify cross-chain proofs more directly between chains that share the same infrastructure operator. This is conceptually similar to how Superchain Interop works within the Optimism ecosystem, but scoped to Caldera's multi-framework deployment set.
​

The Metalayer also addresses liquidity fragmentation. When an ecosystem deploys multiple chains, each chain accumulates its own liquidity pools. Moving assets between those pools through canonical bridges is slow. The Metalayer provides a unified liquidity layer so that a token held on one Caldera chain can be used or traded on another Caldera chain without manual bridging steps from the user's perspective. For a broader treatment of cross-chain communication patterns, see What Is Blockchain Interoperability.
​

Caldera competes with Conduit, AltLayer, and Gelato in the RaaS market. All four provision rollup infrastructure as a managed service, but they differ in supported frameworks, data availability integrations, interoperability offerings, and how they price deployments. The table below captures the key differentiators across the four providers.
​

The RaaS category is young and competitive. Conduit launched around the same time as Caldera and has taken a similar approach, with strong OP Stack support and early Arbitrum Orbit additions. AltLayer emphasizes restaked rollups and has an integration with EigenLayer for AVS-based sequencing. Gelato is a broader Web3 infrastructure provider that added RaaS to its existing relay and automation services.
​

Caldera's most differentiated feature is the Metalayer. None of its primary competitors ship a native cross-chain messaging layer for chains deployed on their platform. Teams building multi-chain ecosystems (e.g., a gaming studio that wants a game chain, a marketplace chain, and a token staking chain) get a routing layer included rather than needing to integrate LayerZero, Hyperlane, or a similar protocol separately.
​

Gelato has the broadest framework coverage, including ZKsync's Elastic Chain (also known as ZK Stack) which none of the other three support as of early 2026. For teams building in the ZKsync ecosystem, Gelato is the primary managed option.
​

Conduit maintains a reputation for OP Stack depth and tight Superchain alignment. Teams prioritizing Superchain interoperability and the Optimism governance ecosystem often view Conduit and Caldera as roughly equivalent on OP Stack, with the differentiator coming down to enterprise support, pricing, and Metalayer value.
​

Pricing across all four providers is typically not public. Deployments are generally quoted per chain per month, with variables including sequencer redundancy, DA layer choice, and support tier. Teams should request quotes from multiple providers, as costs can vary significantly depending on expected throughput.
​

Caldera is suited for teams that need a dedicated settlement environment but do not want to build and operate rollup infrastructure in-house. The clearest fits are gaming studios with high-frequency onchain activity, DeFi protocols that need custom gas tokens or precompiles, and enterprise applications requiring chain-level isolation from public L2 traffic. RaaS makes less sense for teams whose throughput fits comfortably on a shared L2.
​

Onchain games generate high transaction counts at low per-transaction values. Putting game logic on a public L2 like Arbitrum One or Base means competing for blockspace and paying fees priced for DeFi activity. A dedicated chain with a custom gas token eliminates gas-price volatility from the user experience and lets the game operator control the fee model. Xai Games is the direct example: the Xai team uses the AnyTrust DA model to reduce costs to fractions of a cent per transaction.
​

DeFi protocols that reach sufficient scale sometimes find that a shared L2 limits their design space. Custom precompiles can accelerate onchain matching engines. Custom gas tokens let protocols capture fee revenue in their native token. Chain-level isolation means a bug in an unrelated protocol cannot congest the chain or spike fees during critical liquidation windows. For more context on how DeFi protocols use dedicated infrastructure, see What Is DeFi.
​

Enterprises deploying tokenized assets or settlement applications often want a chain that they can configure with specific gas rules, whitelisted validators, or permissioned access at the smart contract layer. Plume Network illustrates the RWA use case: a chain dedicated to RWA tokens with infrastructure that the team controls, rather than inheriting the governance and congestion of a general-purpose L2.
​

If a protocol's transaction volume fits on a shared L2 at acceptable cost, deploying a dedicated chain adds operational overhead without enough benefit. Running a chain means managing sequencer upgrades, monitoring bridge health, and educating users about a new network. Small or early-stage teams are usually better served by deploying on an established L2 until they have evidence that a dedicated chain is necessary. RaaS is a scaling solution, not a launch strategy.
​

Caldera is a blockchain infrastructure provider, not a blockchain itself. It deploys and operates rollup chains on behalf of other teams. The chains deployed through Caldera, such as ApeChain or Xai Games, are distinct networks with their own block explorers, RPCs, and bridge contracts. Caldera operates the sequencer and node infrastructure for those chains.
​

Yes, through Polygon CDK. Caldera supports ZK-based rollups using the Polygon zkEVM proving system, which is EVM-equivalent. OP Stack and Arbitrum Orbit chains on Caldera use optimistic proof systems, not ZK proofs. Teams that specifically need validity proofs for fast finality should select Polygon CDK when deploying on Caldera. See What Is a Rollup for a comparison.
​

Arbitrum One and Base are shared public L2s where every protocol competes for blockspace. A Caldera chain is a dedicated rollup where the deploying team controls block production, gas token, and chain parameters. Dedicated chains offer predictable fees and customizability but require users to bridge assets to a new network, which increases onboarding friction compared to deploying on an established L2.
​

Caldera supports Ethereum calldata and EIP-4844 blob space, Celestia, EigenDA, and Arbitrum's AnyTrust DA committee model. The available options depend on the chosen rollup framework. Celestia and EigenDA reduce per-transaction costs compared to Ethereum native DA, while AnyTrust offers the lowest costs with a trust assumption on a designated data availability committee.
​

Standard bridges route messages through the parent chain, incurring the parent chain's finality latency. The Caldera Metalayer connects Caldera-deployed chains directly, enabling faster cross-chain transfers and a unified liquidity layer across the Caldera ecosystem. It does not replace canonical bridges to Ethereum but reduces friction for transfers that stay within the set of Caldera-operated chains. See What Is Blockchain Interoperability.
​

Sources and methodology. Framework capability information sourced from Caldera documentation and public announcements. Competitor feature comparisons sourced from each provider's public documentation as of Q1 2026. RWA market size sourced from rwa.xyz. Figures are subject to change as providers update their offerings.
​