Shipyard Ended Infrastructure Support for IPFS
The firm ceased all maintenance of IPFS software and core operations following the expiration of its funding.
Updated on Sept. 30, 2026 in Data Centers
Live Poll
Do you trust the long-term reliability of decentralized infrastructure projects when dedicated corporate funding disappears?
Shipyard has officially concluded its engineering and maintenance role for the InterPlanetary File System (IPFS) as of September 30, 2026. This move leaves critical components including Kubo, Helia, and IPFS Desktop without their dedicated maintenance teams.
Why it matters
The change follows a decision by Protocol Labs to decline the renewal of Shipyard’s funding, shifting the future of the network's public infrastructure into uncertainty. Protocol Labs now holds the authority to decide the status of bootstrap nodes and public gateways.
Shipyard transitioned its operational responsibilities for the decentralized file-sharing network through the end of September. Affected software includes Kubo, the primary IPFS implementation, and Helia, a modular JavaScript library for the protocol.
The players
Shipyard
An engineering firm previously focused on maintaining core software and infrastructure for the IPFS ecosystem.
Protocol Labs
A research and development lab that acts as the primary authority for IPFS infrastructure and bootstrap nodes.
The details
Shipyard operated as a dedicated engineering unit tasked with maintaining the InterPlanetary File System, a peer-to-peer hypermedia protocol. With this transition, core software like Kubo—the node implementation used for hosting and retrieving content—no longer receives dedicated upkeep from the former maintainer. Additionally, IPFS Desktop and the Helia library have lost their primary engineering support stream.
Timeline
September 30, 2026: Shipyard ended all engineering and infrastructure operations for IPFS.
The Tech Race
This development follows a pattern set by the transition of Libp2p governance where core infrastructure shifts its primary maintainer. It marks a significant departure from the previous model of sustained, dedicated engineering for the protocol's core implementations.
Users of Kubo, Helia, and IPFS Desktop should monitor their deployments for updates as dedicated maintenance from the original team has ceased. The availability of public infrastructure nodes like ipfs.io is subject to future decisions by Protocol Labs.
The takeaway
The decentralization of software maintenance remains a challenge when tied to single-source funding models. Stakeholders should watch for future announcements from Protocol Labs regarding the long-term support strategy for public bootstrap nodes.
Further reading
For broader context on how decentralized networks manage node uptime, read our latest analysis in Data Centers.
Source note: This article includes information reported by TokenPost.
Live Poll
Do you trust the long-term reliability of decentralized infrastructure projects when dedicated corporate funding disappears?
