← All stories
● Covered by 1 source · 1 reportMedium impact1 negative

Shipyard to Cease IPFS Maintenance and Operations by September 2026 Due to Funding Cut

🔄 Updated 50m ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Shipyard's IPFS operations will end by September 30, 2026.
  • Protocol Labs is not renewing Shipyard's funding.
  • Key projects like Kubo, Helia, and IPFS Desktop will lose dedicated maintainers.
  • Shipyard will cease operating public infrastructure like ipfs.io and dweb.link.

Funding Cut Leads to Wind-Down

Shipyard has announced that it will discontinue all engineering, maintenance, and infrastructure operations related to IPFS by September 30, 2026. This decision follows Protocol Labs' choice not to renew Shipyard's funding, which had supported their work for over two years. The organization expressed disappointment regarding the outcome.

Impact on IPFS Ecosystem

The cessation of Shipyard's activities will have significant implications for the IPFS ecosystem. Projects such as Kubo, Helia, Boxo, Rainbow, IPFS Desktop, and IPFS Companion will no longer have dedicated maintainers for new features, bug fixes, or long-term stewardship. Shipyard's contributions to upstream projects like go-libp2p and js-libp2p will also cease, along with their work on IPFS specifications and broader ecosystem coordination.

Public Infrastructure Affected

Shipyard will also stop operating the public infrastructure it currently manages. This includes critical services such as ipfs.io, dweb.link, check.ipfs.network, and delegated-ipfs.dev. The discontinuation of these services could affect accessibility and functionality for users relying on this infrastructure.

Past Contributions and Future Plans

Over the past three years, Shipyard contributed to the IPFS ecosystem by delivering verifiable websites via inbrowser.link, re-architecting IPFS gateway infrastructure to handle increased traffic with reduced costs, and advancing HTTP-native approaches to IPFS. They had plans for future developments, including simpler HTTP-native implementations, resilient content routing, and support for large SHA-256 objects, but these will not be pursued by Shipyard.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~7 min · 6 stories · Aug 24

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Shipyard, a key contributor to the InterPlanetary File System (IPFS) ecosystem, announced it will wind down all IPFS-related engineering, maintenance, and infrastructure operations by September 30, 2026, after Protocol Labs decided not to renew its funding. This cessation will leave numerous core IPFS projects and public infrastructure without dedicated maintainers, impacting the future development and stability of the decentralized web technology.