Shipyard to End All IPFS Maintenance Sept. 30 After Protocol Labs Cuts Funding

MakeCryippreferred on

• Interplanetary Shipyard will stop all IPFS engineering, maintenance, and infrastructure work on September 30, 2026.
• Protocol Labs, Shipyard’s main funder since 2024, declined to renew that funding.
• Kubo, Helia, Boxo, Rainbow, IPFS Desktop, and IPFS Companion will lose their dedicated maintainers.

Interplanetary Shipyard, the organization that has kept the IPFS and libp2p protocols running since 2024, said it will shut down all of its IPFS engineering, maintenance, and infrastructure work on September 30, 2026, after Protocol Labs decided not to renew Shipyard’s funding.

What Loses Its Maintainer

IPFS is a peer-to-peer protocol that lets files and websites live across many computers instead of one central server, and it underpins a wide range of crypto and web3 products. After September 30, Kubo, Helia, Boxo, Rainbow, IPFS Desktop, and IPFS Companion, the software libraries and apps most of that ecosystem runs on, will have no dedicated maintainer.

Shipyard also plans to stop operating public infrastructure including the ipfs.io and dweb.link gateways, delegated-ipfs.dev, and IPFS’s bootstrap nodes, and says their future is now Protocol Labs’ call, not Shipyard’s.

Built to Escape This Exact Dependency

The shutdown lands harder than a typical funding lapse because of how Shipyard came to exist. Shipyard launched in April 2024 as an independent nonstock corporation, spun out after Protocol Labs itself pledged in late 2023 to decentralize IPFS governance.

Its founding announcement argued that the projects built on IPFS and libp2p had grown too broad for one company to steward alone, and it named Protocol Labs as its “anchor financial partner for 2024-2025,” alongside smaller backers including Optimism’s RetroPGF program, Cloudflare, Pinata, Fission, and CoopHive. Two years on, the exact dependency Shipyard was built to escape is what just ended it.

Not Protocol Labs’ First Cutback

A member of the IPFS community made the same point on the project’s own forum, arguing that Shipyard’s independence claims from 2023 look hollow if a single funder’s decision can end all maintenance.

That reaction lands closer to home for Protocol Labs than it might elsewhere. The company already cut 21% of its staff in February 2023 as crypto markets fell, so a funder pulling back under pressure is a pattern it has lived through before, not a first for the company.

Open Source Has Been Here Before

Open-source infrastructure running on one funder’s discretion is not new to this story either. After the 2014 Heartbleed bug showed that OpenSSL, the encryption software securing much of the web, was kept alive by a handful of underfunded volunteers, the industry built the Core Infrastructure Initiative specifically because leaving critical software to any single company’s budget had already proven too fragile. The Balancer crypto exploit also showed how vulnerabilities in widely used open-source infrastructure can create broader risks across the ecosystem. IPFS’s stewardship still runs on exactly that kind of discretion, and this week showed why that keeps being a problem.

What Happens After September 30

What comes next is unsettled. One account attributes to Protocol Labs engineering lead Molly Mackinlay a plan to shift IPFS toward “lighter-weight stewardship,” through grants to individual maintainers rather than a dedicated team.

Shipyard says it will stay available through September 30 to help projects transition and has opened a feedback form for the community. Until a successor for Kubo, Helia, Boxo, and Rainbow actually steps forward, IPFS’s core software and its public gateways are heading into October without anyone committed to maintaining them.