CDK Enterprise

Your Compliance Department’s Favorite Stack

Enterprise-grade blockspace means predictable costs, privacy as-needed, performance under real world loads, and uptime guarantees. This is scaling infra that actually scales

Learn more
Get in touch
What is CDK Enterprise?

Privacy-first with interop when you need it

Private EVMs keep you siloed. Public chains offer composability but require transparency. CDK Enterprise is the third option: a public-permissioned L2 that’s interoperable and auditable, with enterprise controls when you need them. All of the network-level controls of siloed, closed systems, with the user and liquidity upsides of public chains
Why CDK Enterprise?

What you get

Granular network control

You can deploy CDK Enterprise as a fully private chain or with gated access and offchain data. API keys + access control lists provide the filtering to control who can read, who can write, and even who calls specific contracts or RPC methods

High-performance & predictable overhead

Proven performance under real world load, with peaks of 5,000+ TPS and 200 Mgas/s. Alongside a managed uptime SLA, you’ll replace an expensive Hyperledger Besu setup with less maintenance complexity and lower operating overhead

Unified liquidity via Agglayer, as-needed

Launch with native EVM-equivalence and flip on cross-chain interop whenever—no replatforming required. Start out public-permissioned and connect to broader liquidity and even non-EVM ecosystems on your timeline

Seamless, lossless migration

For chains running Besu, proven migration paths enable you to upgrade from a siloed stack to a feature-complete rollup without disrupting normal business. Zero-downtime and full-history options for data that must always be retrievable

Get in touch with the team about CDK Enterprise

Talk to us about CDK

Get in touch
IMPLEMENTATION Providers

Launch Faster with Implementation Providers

Connect with trusted providers to securely and rapidly deploy your layer 2, Agglayer-connected.
Explore and Connect with IPs

FAQ

What is the Agglayer Chain Development Kit (CDK)?

A multistack toolkit by Polygon Labs for building custom Ethereum Layer 2 chains with native Agglayer integration. It offers developers flexibility to choose stacks like CDK OP Stack or CDK Erigon, enabling unified liquidity, seamless cross-chain UX, and tailored performance, with more stacks to be added in the future.

What does it mean for CDK to go multistack?

CDK’s multistack approach allows developers to build chains using various stacks, such as CDK OP Stack and CDK Erigon, with more to be added in the future. This gives builders freedom to select the best stack for their needs, all natively connected to Agglayer for unified liquidity and interoperability.

What is CDK OP Stack, and what does it offer?

CDK OP Stack is a CDK stack using Ethereum’s Geth client (50%+ market share) and OP Stack, offering low-cost, high-performance chains with native Agglayer connectivity. Sovereign mode uses pessimistic proofs for security; rollup mode (with Plonky3-generated proofs) provides the greatest security and validium mode the most performance.

How does CDK Erigon differ from CDK OP Stack?

CDK Erigon focuses on performance and extensive customization, 3 core modes, and high throughput, for bespoke L2s. CDK OP Stack is based on the OP stack, with geth at its core for familiarity and performance, prioritizing mass adoption with ZK enhancements.

What is a sovereign chain in CDK?

A sovereign chain, available in CDK OP Stack and CDK Erigon, operates without ZK provers and uses pessimistic proofs via Agglayer for security. This ensures no chain can withdraw more than deposited on the unified bridge, offering low-cost, high-performance connectivity.

Why is Agglayer integration important for CDK chains?

Agglayer integration, native to all CDK chains, enables unified liquidity, shared state, and seamless cross-chain transactions. It creates a single environment that feels like the internet, enhancing UX and interoperability across diverse chain architectures.

Do I need to use Agglayer with CDK chains?

For the most part, yes. However, CDK chains are natively connected to Agglayer by default for optimal interoperability and UX; developers can technically choose to disable it and run chains independently, depending on their project needs.

How can I start building a CDK chain?

Use the CDK developer docs to spin up a testnet or learn more. For production-ready chains, contact implementation providers like Conduit (supports CDK OP Stack with G2 sequencer) or Gateway.fm (supports CDK Erigon) to ensure a fast, reliable launch.