Skip to main content

Rollup as a Service

Your own L2 or L3, with the sequencer run for you

Deploy optimistic or ZK rollups on Ethereum. Our engineers run the sequencer, batcher, prover, and bridge, and apply framework upgrades, so your team ships the application.

Frameworks
4
OP, Orbit, CDK, ZK Stack
DA options
5
Blobs, Celestia, EigenDA, Avail, DAC
Sequencer keys
Yours
Chain ownership stays with you
Type II certified
SOC 2
Audited annually

Rollup frameworks we deploy and operate

OP Stack, Arbitrum Orbit, Polygon CDK and ZK Stack. Pick the stack that fits your finality, cost, and decentralisation profile; we run the sequencer, the prover, and the bridge whichever you choose.

OP Stack

Optimistic rollup

Optimism's open-source rollup framework. Opt into the Superchain and inherit shared bridging, governance, and ecosystem liquidity from day one.

Finality
7-day challenge window
Interop
Superchain
  • op-node + op-batcher
  • Permissionless fault proofs
  • Superchain bridging + governance

Powers in production

Base · Optimism · Mode · Zora · World Chain

OP questions answered

Arbitrum Orbit

Optimistic · AnyTrust

Orbit chains settle to Arbitrum One as an L3, or to Ethereum as an L2. AnyTrust mode trades a Data Availability Committee assumption for much lower data costs.

Finality
7-day challenge window
Interop
Orbit native bridge
  • Custom gas tokens
  • Permissioned validators
  • Stylus + EVM

Powers in production

XAI · DEGEN · RARI · Sanko · Cheese Chain

Orbit questions answered

Polygon CDK

ZK rollup · Validium

Polygon's Chain Development Kit for zkEVM rollups. Atomic cross-chain bridging via the AggLayer puts your chain on a shared liquidity network on day one.

Finality
Hours (ZK proof)
Interop
AggLayer
  • GPU-accelerated proving
  • AggLayer interop
  • zkEVM Type 2

Powers in production

Katana · Wirex Pay · Manta Pacific

CDK questions answered

ZK Stack

ZK rollup · Validium

Matter Labs' framework with Boojum proofs and EraVM execution. Every account is a smart account: sponsored gas, paymasters, and session keys come standard.

Finality
Hours (Boojum proof)
Interop
Elastic Chain
  • Native AA on every account
  • Boojum recursive proofs
  • Elastic Chain interop

Powers in production

Abstract · Cronos zkEVM · GRVT · Lens Chain

ZK Stack questions answered

Side by side

The tradeoffs that decide it: how long until funds are final, what your contracts compile to, and where data lives.

  • OP Stack

    Type
    Optimistic rollup
    Finality
    7-day challenge window
    VM
    EVM-equivalent (op-geth)
    Data availability
    Ethereum blobs · Celestia · Alt-DA
  • Arbitrum Orbit

    Type
    Optimistic · AnyTrust
    Finality
    7-day challenge window
    VM
    Stylus + EVM (Nitro)
    Data availability
    Arbitrum One · AnyTrust DAC
  • Polygon CDK

    Type
    ZK rollup · Validium
    Finality
    Hours (ZK proof)
    VM
    zkEVM (Type 2)
    Data availability
    Ethereum · DAC
  • ZK Stack

    Type
    ZK rollup · Validium
    Finality
    Hours (Boojum proof)
    VM
    EraVM · native AA
    Data availability
    Ethereum · Validium

Choose every layer of the modular rollup stack

Execution, settlement, data availability, proving and sequencing are separate choices. We model the cost and security tradeoff of each before you sign, and keep operating whichever DA layer, prover, or sequencer you pick.

  • Execution

    Where transactions run

    The VM that turns transactions into state changes. Pick by tool-chain familiarity, account-abstraction needs, and existing contract portability.

    • EVM-equivalent (op-geth)

      OP Stack

    • Stylus + EVM (Nitro)

      Arbitrum Orbit

    • zkEVM (Type 2)

      Polygon CDK

    • EraVM · native AA

      ZK Stack

  • Settlement

    Where finality lives

    The chain your rollup posts state roots and proofs to. It sets your security guarantees and what the bridge trusts.

    • Ethereum L1

      Maximum security

    • Arbitrum One

      Orbit L3s

    • Base / Optimism

      OP L3s

    • Sovereign

      App-specific

  • Data availability

    Where transaction data is published

    The cheaper the DA, the higher the trust assumption. Ethereum blobs carry the fewest assumptions; alt-DA layers trade lower cost for trust in their own validators or a committee.

    • Ethereum blobs

      Trust-minimised

    • Celestia

      Modular DA

    • EigenDA

      Restaked DA

    • Avail

      Modular DA

    • AnyTrust DAC

      Committee-trust

  • Proving

    How state validity is proven

    Optimistic rollups assume validity and let challenges run; ZK rollups prove it cryptographically every batch. Proving infrastructure scales with your throughput.

    • Fraud proofs

      Optimistic

    • Boojum (STARKs)

      ZK Stack

    • Plonky3

      Polygon CDK

    • SP1 / Risc Zero

      Custom ZK

  • Sequencing

    Who orders transactions

    Centralised sequencers are simple but censorable. Shared sequencing aligns your chain with others; decentralised sequencing is the long-term endgame.

    • Centralised (default)

      Lowest latency

    • Shared (Espresso)

      Cross-chain ordering

    • Astria

      Shared, modular

    • Decentralised

      Permissionless

Managed on top of the rollup stack

One-click deployment

Sequencer, batcher, prover, and RPC nodes deployed together and managed from one dashboard. Your team does not need rollup operations experience.

Custom block explorer

White-labeled explorer with your branding. Full transaction history and network metrics included.

L1 to L2/L3 migration

Our engineers plan the migration with you, run the cutover, and hand off operations when you're ready.

Testnet in <24 hours, mainnet in 4 – 8 weeks

A typical managed rollup launch. Tokenomics, audits, and bridge setup take longest; the infrastructure is the fast part.

  1. Before signing

    Scoping call

    Framework recommendation + cost model

    • Throughput envelope
    • Cost model (DA + L1)
    • Framework pick
  2. <24 hours

    Testnet live

    Public testnet with explorer + faucet

    • RPC + WS endpoints
    • Block explorer
    • Bridge UI
  3. After testnet

    Integration + load test

    Your dApp on the testnet, traffic profiled

    • Load-test report
    • Tokenomics review
    • Audit kickoff
  4. 4 – 8 weeks

    Mainnet launch

    Mainnet sequencer + bridge live

    • Sequencer keys
    • Audit completion
    • Bridge announcement
  5. After mainnet

    Operate under SLA

    24/7 monitoring, upgrade management, reviews

    • Performance reviews
    • Framework upgrade plan
    • Capacity scaling

Owning and running your rollup

Need something specific? Talk to an engineer.

  • Rollup-as-a-Service (RaaS) is a managed offering that deploys, operates, and upgrades your Layer-2 or Layer-3 rollup chain. You define the chain parameters. We run the sequencer, batcher, prover (for ZK rollups), block explorer, and bridge under a contractual uptime SLA, with 24/7 monitoring.

  • Yes. Chain ownership, sequencer keys, and admin contracts stay with you. We operate the infrastructure under contract; you can take operations in-house or move to another RaaS at any time.

  • Two parts: a managed infrastructure fee, and pass-through settlement costs on the chain you settle to. Settlement is usually the larger and more variable half — it moves with your transaction volume and, above all, with your DA choice. Ethereum blobs are the trust-minimised, higher-cost option; Celestia, EigenDA, Avail, and AnyTrust committees cut that cost substantially in exchange for a weaker data-availability guarantee. We model both halves against your expected throughput before you sign anything.

  • Yes, on every framework. You can set a custom ERC-20 as the gas token (with appropriate bridging), use the chain native fee token, or run a gasless/paymaster setup where the application sponsors user fees.

  • Rollup mode posts all transaction data to the settlement layer, giving full data availability and trustless reconstruction, and inherits Arbitrum security end to end. AnyTrust posts data to a Data Availability Committee instead, cutting data costs substantially in exchange for a trust assumption on that committee. The fraud-proof challenge window is identical in both modes — AnyTrust changes where data lives, not how fast you can withdraw. Production gaming and consumer chains usually pick AnyTrust; security-critical chains pick rollup.

  • Rollup posts call data to Ethereum, giving full data availability at higher cost. Validium posts to a committee instead — cheaper, same fast ZK finality, but with a data-availability trust assumption. For high-volume consumer apps, validium is usually the right call.

  • We manage prover capacity for you and add instances as your chain grows, so you pay for the throughput you actually use. Proof generation is a separate line item in the cost model, because it scales with transaction volume rather than with the flat infrastructure fee.

  • Every account on a ZK Stack chain is a smart account by default. You get sponsored transactions, paymasters, session keys, and arbitrary signature schemes without deploying any account-abstraction contracts of your own.

  • Yes, and which one follows from your framework. OP Stack chains can opt into the Optimism Superchain for shared bridging and governance. Orbit chains settle to Arbitrum One and inherit its tooling. Polygon CDK chains join the AggLayer, which gives unified bridging and shared liquidity with other Polygon-ecosystem chains. ZK Stack chains interoperate through the Elastic Chain layer (previously branded Hyperchains). We handle the technical integration and the paperwork either way.

  • We apply framework upgrades (OP, Orbit, CDK, ZK Stack releases) on a coordinated schedule with you. Upgrades are tested on your testnet first, then deployed to mainnet during low-traffic windows, and our engineers run the rollout.

  • 24/7 incident response with a contractual SLA, a dedicated Slack channel with our infrastructure engineers, framework upgrade management, and scheduled performance and architecture reviews. Review cadence and any onsite engineering are set in your contract.

We launch your rollup and keep operating it after mainnet.

Scope throughput, finality, and cost with a rollup engineer. You leave with a written framework recommendation and a cost model that covers DA and L1 settlement.