Overview
Moving from a local devnet to a production CDK chain on testnet or mainnet requires infrastructure planning, bridge configuration, and Agglayer registration. Polygon’s implementation providers handle this process end-to-end.Implementation providers
Two providers currently support production CDK deployments:
Both providers support all three deployment modes: sovereign, validium, and zkrollup.
To deploy a CDK Besu chain, follow the public
cdk-besu runbook, which covers devnets, testnets, and production networks that settle on Sepolia or Ethereum mainnet.
Testnet deployment
Testnet deployments let you validate your chain configuration, bridge behavior, and application integrations before going to mainnet. Contact an implementation provider to set up a testnet environment. They will provision:- L1 and L2 node infrastructure
- Bridge service and AggKit components
- Agglayer connectivity (testnet)
- Monitoring and alerting
Mainnet deployment
Mainnet deployment follows the same process as testnet with additional requirements:- Agglayer registration: Your chain must be registered with Agglayer through the Polygon Support Portal.
- Bridge contract deployment: L1 bridge contracts are deployed and verified on Ethereum mainnet.
- Safe Proposer setup: Rollup registration uses a Safe multisig proposer for governance.
Self-operated chains
If you prefer to operate your own infrastructure, start with the Quickstart and Devnet Deployment Guide to understand the component architecture. For a Besu chain, thecdk-besu runbook covers deployment, verification, and day-to-day operations. For production self-operation, contact the Polygon team through the Support Portal to discuss requirements.