Conduit

• Name: Conduit
• URL: https://www.conduit.xyz/
• Category: chain-operations company / rollup-and-L1 deployment operator / RPC and indexing platform company
• Tags: ethereum-ecosystem
• Summary: Conduit belongs as an entity note, not a protocol note. The useful question is who runs the managed stack that launches, configures, and keeps customer chains alive: deployment workflow, chain-template choices, RPC credentials, indexing defaults, bridge and wallet integrations, marketplace add-ons, and the professional-services layer that helps teams keep operating once the chain is live. The practical leverage is not the phrase rollup in minutes; it is that a named company can become the day-2 operating shell around a chain.
• What it does:
  • Sells managed chain deployment and operations for rollups and adjacent custom-chain builds, including self-serve and sales-assisted launch paths
  • Supports multiple underlying stack families such as OP Stack, Arbitrum Orbit, and Polygon / AggLayer-associated CDK paths rather than shipping one proprietary protocol
  • Provides built-in RPC, indexing, account-abstraction-adjacent tooling, and marketplace integrations that make Conduit part of the default developer and operator workflow after launch
  • Packages professional services around architecture design, wallet / bridge / data-system integrations, migration planning, training, and ongoing operational support
  • Publishes external-node and CLI-oriented tooling that lets customers and ecosystem participants interact with Conduit-managed chains without everything staying behind a thin dashboard
• Key claims:
  • The homepage now leads with You build the product, we run the chain, which is unusually explicit primary-source language for why this belongs in companies/ rather than projects/
  • The site markets Conduit as powering 55% of chains on Ethereum, with 60+ mainnets, billions of transactions, and billions in TVL; those should still be treated as vendor claims, but they show Conduit wants to be read as a real operating layer rather than a boutique launch tool
  • The docs overview calls Conduit the complete chain infrastructure platform and says teams get built-in RPCs, account abstraction, indexing, and 70+ marketplace apps, which confirms the product is broader than chain creation alone
  • The chains docs say customers like Polygon, Ethena, Plume, and Blackbird have deployed with Conduit and that the company works closely with Optimism, Arbitrum, and Polygon on their respective stack families, which is a useful map of where ecosystem and company boundaries meet
  • The homepage’s professional-services language matters analytically because it extends the control surface beyond software into migration planning, operator enablement, and long-lived dependency on Conduit’s staff and workflows
• Whitepaper: No classic company whitepaper is the point here. The strongest primary materials remain the official site, overview docs, chains docs, and the earlier primary-source snapshot in ../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

• Project-layer alias: conduit.
• Strongest adjacent managed-chain-ops comparison: caldera.
• Useful company-layer contrast: quicknode for another case where infrastructure packaging, credentials, and workflow defaults matter more than any standalone protocol claim.

Protocol / company boundary

• There is not a particularly useful standalone Conduit protocol boundary doing the analytical work.
• The underlying protocol families are OP Stack, Orbit, AggLayer / CDK, and the other chains or bridges a customer chooses; Conduit is the company that packages those options into a managed launch and operations surface.
• That is why this note belongs in companies/: the important questions are who controls the easiest deployment path, who holds the operating playbooks, which integrations become default, and how much of the chain’s day-2 reality lives inside a named vendor relationship.

Control surface

• Practical authority sits in launch approval and support workflow, chain-template exposure, config and integration defaults, RPC and indexing credentials, marketplace and bundler-adjacent packaging, migration help, and the operational knowledge customers leave inside Conduit’s stack.

• Customer chains still hold the contracts, balances, sequencers, and governance objects that matter onchain, but Conduit can strongly shape how easily teams deploy, observe, recover, and extend those systems in practice.

• Read Conduit as a company-run chain-operations control plane, not as a neutral protocol primitive.

• Last reviewed: 2026-08-05 UTC