Conduit primary-source snapshot
Fetched: 2026-04-23 UTC
1) Official site overview
Source: https://www.conduit.xyz/
Selected excerpts from the official site:
Powerful Chain Infrastructure
60+ Mainnets deployed on Conduit
3B Transactions processed
Additional signals from the homepage:
- Conduit presents itself as a managed infrastructure provider for dedicated chains rather than as a token-centric protocol
- The homepage frames the offering across chains, RPC nodes, and indexing, suggesting an operational platform rather than a single-product rollup launcher
- Customer examples and case studies are a major part of the primary-source story, which is useful for understanding target users even though the numbers remain vendor claims
2) Docs overview
Source: https://docs.conduit.xyz/overview.mdx
Selected excerpts from the docs overview:
Learn how to deploy your own rollup in minutes using Conduit’s self-serve platform. No coding required - get enterprise-grade rollup infrastructure
Conduit is the complete chain infrastructure platform where the best teams in crypto scale their apps and ecosystems.
Get all the tooling you need with built-in RPCs, Account Abstraction, Indexing, and 70+ more apps in the Marketplace.
Additional signals from this page:
- The docs explicitly position Conduit as an integrated platform, not only a rollup host
- Built-in RPC, indexing, marketplace integrations, and account-abstraction support are core parts of the product surface
- The docs themselves are detailed enough to serve as a primary source even without a whitepaper
3) Chains product overview
Source: https://docs.conduit.xyz/chains/overview.mdx
Selected excerpts from the chains docs:
Customers like Polygon, Ethena, Plume, Blackbird, and more have already deployed with Conduit.
We work closely with Optimism on the Superchain, Arbitrum on Orbit, and Polygon on AggLayer.
Build on production-ready stacks from Optimism, Arbitrum, and Polygon
Additional signals from this page:
- Conduit should be categorized partly by the ecosystems and rollup stacks it supports, not only by a generic “RaaS” label
- The docs emphasize customization and modular choices around chain architecture
- Production customers and ecosystem relationships are central to the company’s positioning
4) Docs index / llms.txt
Source: https://docs.conduit.xyz/llms.txt
Selected excerpts from the docs index:
OP Stack
Arbitrum Orbit
Agglayer CDK
Bundler
Pricing & Costs
Additional signals from this page:
- Conduit exposes a broad, machine-readable docs surface via
llms.txt, which makes it easy to assess product breadth quickly - The docs span launch flows, integrations, RPC operations, indexing, and account abstraction, reinforcing the platform characterization
- This is a good example of a docs-first crypto infra vendor whose real source of truth is its operating documentation
5) GitHub organization
Source: https://github.com/conduitxyz
Selected excerpts from the GitHub org:
Fully-managed, production-grade rollups on Ethereum
Conduit Optimism External Nodes provides everything you need to run and operate an OP Stack external node for a Conduit managed rollup.
Agent Skills for integrating Conduit RPC infrastructure into AI-powered applications.
Additional signals from this page:
- Conduit publishes supporting tooling around CLI flows, external nodes, and custom clients, which helps distinguish it from vendors that keep everything behind a UI
- Public repos suggest the platform exposes real operational interfaces for developers and chain operators
- The GitHub org complements the docs rather than replacing them as the main source of truth
Notes
- This pass did not locate a classic whitepaper or litepaper from official Conduit sources.
- The strongest primary materials were the official marketing site, detailed product docs, and GitHub organization.
- Conduit is worth cataloging because it occupies an important infrastructure layer between protocol frameworks and app teams that want dedicated chain operations without building every component themselves.
- TVL, chain-share, customer, and transaction metrics should still be treated as vendor claims unless independently verified.