Protocol Labs has informed Shipyard that it will not renew funding, prompting the winding down of IPFS-related engineering and maintenance operations. The final day for this work is September 30, 2026. This decision marks the end of a three-year partnership where Shipyard helped shape the modern IPFS ecosystem.

During this period, Shipyard delivered verifiable websites via inbrowser.link and re-architected gateway infrastructure to handle 3× more traffic while cutting costs by around 80%. They also advanced HTTP-native approaches to simplify deployment compared to traditional libp2p-based hosting. Despite these successes, including improvements to core implementations and public infrastructure, the team could not realize future plans for simpler HTTP-native implementations or pseudonymous hosting through Tor.

Consequently, projects maintained by Shipyard will lose dedicated maintainers. These include Kubo, Helia, Boxo, Rainbow, IPFS Desktop, IPFS Companion, Someguy, Service Worker Gateway, and IPFS Check. Contributions to upstream projects like go-libp2p and js-libp2p will cease. Additionally, Shipyard will stop operating public infrastructure such as ipfs.io, dweb.link, and bootstrap nodes. Protocol Labs will determine the future of these domains and services. Shipyard aims to assist with the transition until the end of September.