TL;DR:
- Input Output is shifting Cardano core development to specialist ecosystem teams covering the Haskell node, Plutus, Daedalus, Hydra and developer relations.
- Se7en Labs and Teragone are among partners taking component responsibility, with public repositories and Intersect oversight intended to support accountability.
- The transition targets at least three Cardano implementations in Haskell, Rust and Go by 2027, while IO Labs and IO Ventures operate under the new structure.
Input Output has announced an infrastructure governance model for Cardano, shifting responsibility for core development away from a single founding company and toward specialist ecosystem teams. The transition covers the Cardano Haskell node, Plutus, Daedalus, Hydra and developer relations, placing some of the network’s most important engineering surfaces into a more distributed operating structure. The change is not just about governance votes. Cardano is decentralizing how the network is built, extending the Voltaire-era logic from decision-making into day-to-day infrastructure maintenance.
Cardano's protocol and governance are already decentralized. Now its engineering is too.
“The last stage of the Voltaire era is full decentralization of node and reference blueprint development. Since 2024, IOG and its partners have carefully managed a process that will conclude… pic.twitter.com/zCCgu6ahco
— Input Output Group (@IOGroup) July 17, 2026
Independent teams take over Cardano’s core stack
Specialist partners including Se7en Labs and Teragone will assume responsibility for specific components, with named partners, public repositories and Intersect oversight intended to make the process auditable. That structure matters because decentralized governance can still depend on centralized engineering if one organization controls the reference software, delivery cadence and developer coordination. The new model targets that remaining dependency, asking the ecosystem to prove it can maintain critical infrastructure through transparent teams rather than implicit reliance on Input Output.
Charles Hoskinson said the process is expected to conclude in 2027, with independent firms maintaining at least three Cardano implementations written in Haskell, Rust and Go. Those implementations are expected to be supported by formal specifications overseen by organizations including Intersect and Pragma, while development remains subject to community review and voting. The multi-implementation goal raises the stakes, because software diversity can improve resilience, but only if specifications, testing and governance coordination stay disciplined across teams and languages.
Input Output is also reshaping its role. IO Labs is spinning out development of the Haskell node to community control, while Input Output plans to focus more heavily on research and venture creation through IO Labs and IO Ventures. The broader structure is designed to reduce Cardano’s dependence on one organization and strengthen the case for community-funded infrastructure through the Cardano treasury. The transition turns decentralization into an operational budget question, because independent teams must be funded, measured and held accountable.
The decentralization campaign launched July 17 with a dedicated website and short film. Additional milestones for the Haskell node, Plutus, Hydra and developer relations are expected from August through December 2026, with IO Labs and IO Ventures operating under the new structure from January 2027. The real test is execution, not rhetoric, as Cardano moves from shared governance ideals toward shared engineering responsibility.
