Conduit

• Name: Conduit
• URL: https://www.conduit.xyz/
• Category: Rollup / chain infrastructure / RPC / indexing platform
• Tags: ethereum-ecosystem
• Summary: Conduit is a managed chain-operations vendor for teams launching and running their own chains. The useful cut is not rollup in minutes; it is that Conduit sells the surrounding operator stack — deployment templates, RPC, indexing, explorer setup, and adjacent tooling — that can make a chain feel turnkey while keeping the real control points offchain.
• What it does:
  • Lets teams deploy testnets and production chains through a self-serve or sales-assisted platform
  • Supports multiple chain stacks, including OP Stack, Arbitrum Orbit, and Agglayer CDK
  • Provides managed RPC infrastructure with API keys, throughput guidance, WebSocket support, and access controls
  • Offers indexing and chain-data products for querying rollups and other supported chains
  • Documents integrations such as Blockscout, bridge UI setup, bridged USDC, bundlers, gas sponsorship, and external-node operation
  • Maintains a GitHub footprint for CLI tooling, external-node setups, custom execution clients, and account-abstraction-related code
• Key claims:
  • The homepage markets Conduit as “powerful chain infrastructure” and claims to be powering a large share of Ethereum chains, with 60+ mainnets, billions of processed transactions, and billions in TVL; these should be treated as vendor claims unless independently verified
  • Official docs describe Conduit as a platform where teams can deploy their own rollup in minutes with enterprise-grade infrastructure
  • The chains docs emphasize production-ready support for Optimism, Arbitrum, and Polygon-associated rollup stacks, with modular choices around settlement and data availability
  • Product docs show Conduit is more than rollup hosting: it also sells RPC, indexing, and account-abstraction-adjacent infrastructure for developers building on Conduit-managed chains
  • GitHub materials suggest Conduit also exposes implementation details and tooling for external nodes, CLI flows, and customized OP Stack infrastructure rather than only offering a closed managed service
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were Conduit’s official site, docs portal, and GitHub organization; see ../whitepapers/conduit-primary-sources-2026-04-23.md.
• Sources:
  • https://www.conduit.xyz/
  • https://docs.conduit.xyz/overview.mdx
  • https://docs.conduit.xyz/chains/overview.mdx
  • https://docs.conduit.xyz/llms.txt
  • https://github.com/conduitxyz

Internal linkages

• Stronger managed-chain-ops comparison: caldera.
• Main chain-stack family behind much of Conduit’s rollup surface: optimism.

Control surface

• Customer chains hold the contracts, balances, bridges, and transactions. Conduit’s leverage sits in the operational wrapper around them: deployment flows, RPC policy, indexing, explorer defaults, bridge setup, and node tooling.

Comparable to / differs from

• Comparable to: Caldera as the stronger managed chain-operations note in the corpus.
• Differs from: architecture layers such as Agglayer and from execution venues themselves.

Governance / control risk

• Practical authority can collect around production access, deployment templates, RPC quotas, explorer defaults, bridge integrations, and which node or account-abstraction paths are easy versus unsupported.
• Conduit is infrastructure, but not neutral plumbing once teams depend on its packaged defaults.

Rent / leverage sink

• Conduit’s leverage sits in the recurring operational dependency layer: once a chain relies on its RPC, indexing, explorer, and launch tooling, moving away can be harder than switching execution clients alone.

• The strongest rent sink is the convenience and policy wrapper around chain operations, not merely the one-time deployment flow.

• Last reviewed: 2026-06-04 UTC