tl;dr
Crypto is more modular than ever, providing institutions and builders many different ways to launch custom blockchains. Recent innovation has opened the gateway to sector-specific chains, with major interest from enterprises looking to expand into blockchain and tap Ethereum’s deep, liquid markets.
Among the most popular stacks helping industries get there are OP Stack and Arbitrum Orbit.
But choosing the right stack to build your custom chain requires thinking through performance, interoperability, sovereignty, and access to a unified Web3.
Several major enterprises are taking distinct approaches in choosing blockchain stacks. Robinhood recently announced it is building an Ethereum Layer 2 using Arbitrum Orbit. By leveraging Orbit’s flexible architecture, Robinhood aims to create a scalable platform for tokenized assets like stocks and ETFs.
On the other side, Base Chain, Coinbase’s OP Stack-powered Layer 2, has rapidly become the most prominent member of the Optimism Superchain, securing over $14.5B in total value as of mid-2025. With deep liquidity from Coinbase and simplified onboarding, plus the promise of interoperability through Superchain, Base shows how OP Stack has been adopted for performant, sector-specific chains.
Each of these stacks promise ease in development, fast settlement, low fees, and crucially, interoperability.
But each stack also locks respective builders into self-serving ecosystems.
Joining the Superchain means following the Law of Chains and assenting to a tax (either 2.5% of chain revenue or 15% of onchain profit) in order to access interoperability. Although the details about Robinhood Chain are sparse, Arbitrum also imposes a revenue share and licensing agreement with Orbit chains that aren;t configured as Layer 3s that settle to Arbitrum One. Optimistic chains are also subject to a 7-day withdrawal period for assets moving off of the Layer 2 through a canonical bridge—immensely slowing capital and curbing interoperability, except by introducing third-party bridges, which bring added security challenges, assumptions, and price premiums for end users.
Developers shouldn’t have to choose, and crypto shouldn’t be so fragmented.
Luckily, there’s an alternative. Agglayer CDK by Polygon Labs is a multistack toolkit that offers native interoperability and easy user and developer experience, without the extractive fees. With recently added native support for OP Stack and support for more stacks coming soon, Agglayer CDK builds across isolated ecosystems, bringing ZK security to optimistic chain performance in one bundle.
And with native interoperability for all other chains connected to Agglayer’s bridge, Agglayer CDK brings the upside of high-performant chains without hidden fees or taxes for interop.
So—which stack should you choose?
The OP Stack is the open-source toolkit powering Optimism and the emerging Superchain vision. It provides a standardized set of modules—consensus, execution, settlement—that make it easy to launch Ethereum-compatible rollups.
OP Stack has proven it can scale L2s rapidly while remaining EVM-equivalent and dev-friendly. A number of DeFi-focused and enterprise chains have launched with OP Stack, including Uniswap’s Unichain and Kraken’s Ink,
Orbit is Arbitrum’s framework for launching customizable chains using the Nitro stack. It gives enterprises granular control over nearly every part of the chain—from data availability to execution environments.
Orbit is ideal for projects building complex ecosystems or needing fine-tuned protocol logic while still inheriting Ethereum’s security guarantees.
Both OP Stack and Arbitrum Orbit have business tradeoffs.
OP Stack requires builders to conform to collective standards if they want to join the Superchain and mandates revenue sharing, sacrificing some sovereignty for access to the promise of a still-forthcoming interoperable ecosystem.
Otherwise, developers can fork OP Stack under the permissive open source license and launch custom chains, but without access to the Superchain.
Arbitrum Orbit offers significantly greater governance autonomy and customizability, but it imposes substantial revenue-sharing obligations. Unlike OP Stack, which is open source under an MIT license, there is Business Source licensing for the Orbit stack itself, unless a new chain settles to Arbitrum One or Arbitrum Nova.
Both stacks represent extractive models that require careful consideration of governance, sovereignty, economic autonomy, and long-term business implications.
Instead of picking one side, Agglayer CDK gives enterprises full choice for custom-designing a chain, without ecosystem lock in, extractive fees, or hidden licensing requirements.
Builders have a multistack environment to choose from: Agglayer CDK OP Stack, but powered by ZK; or the original ZK stack, Erigon, for battle-tested reliability, with more stacks in the future—and all with native connectivity to Agglayer.
Crypto is about freedom.
With Agglayer CDK, builders no longer have to pick between OP Stack’s popularity or Arbitrum Orbit’s flexibility.
You can launch chains using whichever stack best fits your needs, and tap into the interoperability, liquidity, and security of Agglayer.
As more stacks become Agglayer-native, Agglayer will remain the aggregation layer for all of Web3.
Both OP Stack and Arbitrum Orbit are powerful tools. But building for Web3’s future shouldn’t mean being locked into one protocol.
Agglayer CDK empowers you to build your chain your way—on your terms, with your stack, and with seamless access to a secure, unified, crosschain world.
Ready to launch? Explore the Agglayer CDK developer docs or reach out to implementation providers like Conduit and Gateway.fm.
Not necessarily. OP Stack offers standardization and Superchain compatibility, while Orbit offers flexibility and customizability. The best choice depends on your use case—or better yet, use Agglayer CDK and don’t choose at all.
Not today, but Agglayer CDK is already multistack, and support for Orbit is being explored.
It’s a multistack toolkit for building custom chains with native Agglayer integration. It currently supports OP Stack and Erigon, with more on the way.