Key Points:
- Shipyard will wind down its engineering, maintenance and infrastructure operations for IPFS on Sept. 30 after Protocol Labs declined to renew its funding.
- Projects including Kubo, Helia, Boxo, Rainbow, IPFS Desktop and IPFS Companion could lose dedicated maintenance unless other developers assume responsibility.
- IPFS will continue operating, but the shutdown raises questions about the long-term stewardship of key decentralized infrastructure and public services.
The future of some of the InterPlanetary File System’s most widely used software and public infrastructure is entering a new phase after Shipyard announced it will end its dedicated IPFS operations on Sept. 30. The decision follows Protocol Labs’ refusal to renew Shipyard’s funding, removing the financial support behind an engineering collective that has played a significant role in maintaining the open-source ecosystem.
The development does not represent the shutdown of IPFS itself. Instead, it marks a significant change in how parts of the decentralized storage network will be developed, maintained and funded.
Funding Loss Leaves Core Projects Without Dedicated Maintainers
Shipyard said the end of its operations will affect projects including Kubo, Helia, Boxo, Rainbow, IPFS Desktop and IPFS Companion. Unless other contributors step forward, these projects will no longer have dedicated maintainers following the Sept. 30 wind-down.
IPFS is an open-source protocol that enables data to be stored and shared across peer-to-peer networks. Rather than depending exclusively on centralized servers, the system allows content to be distributed across participating nodes.
Protocol Labs created IPFS and Filecoin, a blockchain network designed to incentivize decentralized data storage. Shipyard was established in 2024 as an independent collective of longtime IPFS developers who had previously worked at Protocol Labs.
The funding decision therefore creates a direct stewardship challenge for software that remains important to the broader decentralized web ecosystem.
Public IPFS Infrastructure Also Faces Transition
Shipyard will also stop operating several public services, including ipfs.io, dweb.link, delegated-ipfs.dev and IPFS bootstrap nodes.
According to Shipyard, Protocol Labs owns the relevant domains and infrastructure and will determine their future. That gives Protocol Labs an important role in deciding whether these services continue under a different operating structure or are replaced by alternative infrastructure.
The distinction between IPFS and its public services is important. IPFS itself is an open protocol and can continue to operate through independently maintained implementations and nodes. However, the loss of dedicated operators could create maintenance and reliability challenges for specific tools and services.
Protocol Labs Moves Toward Lighter Stewardship
Protocol Labs engineering and research lead Molly Mackinlay said in an online forum discussion that IPFS would transition toward “lighter-weight stewardship” through IPFS Foundation grants to individual maintainers.
She also indicated that development would continue on decentralized public infrastructure.
The proposed approach could distribute responsibility across a broader group of developers rather than concentrating it within a single engineering organization. That may reduce dependence on one funded maintainer, but it also creates uncertainty around coordination, security reviews and long-term development priorities.
For open-source infrastructure, funding is often as important as technical decentralization. Software can be permissionless and community-owned while still requiring sustained engineering resources to remain secure and reliable.
The Next Test for Decentralized Infrastructure
Shipyard’s September wind-down will provide a practical test of whether the wider IPFS community can absorb responsibilities previously handled by a dedicated team. The immediate opportunity is for independent maintainers and organizations to preserve development continuity, while the principal risk is fragmentation if critical projects struggle to attract sustained support.
IPFS is not disappearing, but the transition underscores a broader challenge for decentralized technology: removing centralized control does not eliminate the need for durable funding, technical stewardship and infrastructure operators. The months following Sept. 30 will show whether IPFS can maintain that support through a more distributed model.
Comparison, examination, and analysis between investment houses
Leave your details, and an expert from our team will get back to you as soon as possible
