{"slug": "ipfs-maintainer-shipyard-winds-down-after-protocol-labs-declines-funding-renewal", "title": "IPFS maintainer Shipyard winds down after Protocol Labs declines funding renewal", "summary": "Shipyard, the independent maintainer of core IPFS software and public infrastructure, will wind down its operations on September 30th after Protocol Labs declined to renew funding, co-founders Cameron Wood and Adin Schmahmann announced on August 24th. The shutdown affects maintenance of Kubo, Helia, Boxo, and Rainbow, as well as gateways, bootstrap nodes, and testing services, exposing the fragility of IPFS's reliance on a single funder.", "body_md": "# IPFS maintainer Shipyard winds down after Protocol Labs declines funding renewal\n\n**Cameron Wood and Adin Schmahmann will stop maintaining core IPFS software and public infrastructure on September 30th.**\n\nBy [RuntimeWire Staff](/author/runtimewire-staff)\n· Published\n\nPrimary source: [Shipyard](https://ipshipyard.com/blog/2026-the-end-of-ipfs-at-shipyard/)\n\n## Why it matters\n\nIPFS can remain decentralized at the protocol layer while its maintenance depends on one budget. Shipyard's closure exposes that gap across core code, gateways, and bootstrap infrastructure.\n\n[Cameron Wood](https://ipshipyard.com/author/cewood/?ref=runtimewire) and [Adin Schmahmann](https://ipshipyard.com/author/aschmahmann/?ref=runtimewire) will wind down [Shipyard](https://ipshipyard.com/?ref=runtimewire)'s [IPFS](https://docs.ipfs.tech/?ref=runtimewire) engineering, maintenance, and infrastructure operations on September 30th after [Protocol Labs](https://research.protocol.ai/about/?ref=runtimewire) declined to renew its funding, the co-founders said in [an August 24th blog post](https://ipshipyard.com/blog/2026-the-end-of-ipfs-at-shipyard/?ref=runtimewire).\n\nThe cutoff gives Shipyard just over five weeks to hand off a collection of open-source projects and public services that many IPFS users encounter without knowing who keeps them running. Shipyard maintains core implementations including Kubo, Helia, Boxo, and Rainbow. It also operates gateways, bootstrap nodes, testing services, and collaborative infrastructure.\n\nWood and Schmahmann built Shipyard around the maintainers already doing that work. Schmahmann, a former IPFS technical lead at Protocol Labs, has contributed to IPFS, libp2p, and Filecoin software since 2018. Wood previously led teams responsible for the IPFS.io gateway, JavaScript preload nodes, libp2p and distributed hash table bootstrap nodes, IPFS collaborative clusters, and the Bad Bits deny list. His earlier distributed-systems work included roles at Atlassian, Rocket Internet, Ververica, Alibaba, and Kraken, according to [Shipyard's team page](https://ipshipyard.com/team/?ref=runtimewire).\n\nTheir shutdown announcement lands two years after Shipyard was formed to give IPFS maintainers an independent home. The structure was supposed to spread responsibility beyond Protocol Labs, the organization that created and incubated IPFS. Funding remained concentrated enough that Protocol Labs' decision can still end Shipyard's IPFS work.\n\n### The risk Shipyard named at launch\n\nShipyard publicly launched on April 8th, 2024, as a Delaware nonstock corporation staffed by longtime IPFS and libp2p maintainers. In the [launch announcement](https://blog.ipfs.tech/shipyard-hello-world/?ref=runtimewire), Schmahmann described the move as an \"exit to community\" and identified Protocol Labs as Shipyard's anchor financial partner for 2024 and 2025.\n\nThat announcement also posed the question that now defines Shipyard's closure: what happens when a single funder changes strategy or prioritizes different work?\n\nShipyard planned to answer that vulnerability with a wider mix of public-goods contributions, grants, commercial support, and contracted engineering. It named Optimism RetroPGF, Cloudflare, Pinata, Fission, and CoopHive among its early supporters and said it was seeking an additional [$3 million in community contributions](https://blog.ipfs.tech/shipyard-hello-world/?ref=runtimewire).\n\nProtocol Labs nevertheless remained the financial anchor. The [August 24th announcement](https://ipshipyard.com/blog/2026-the-end-of-ipfs-at-shipyard/?ref=runtimewire) ties the wind-down directly to its decision against renewing funding. Shipyard has not attached a dollar figure to Protocol Labs' support, making it difficult to measure how much replacement funding would be needed to preserve the current operation.\n\nThe dependence was not hidden. It was the problem Wood, Schmahmann, and their colleagues set out to solve. Their experience shows how slowly financial control moves even after maintainers and code have been moved into an independent organization.\n\n### What stops on September 30th\n\nShipyard said Kubo, Helia, Boxo, Rainbow, IPFS Desktop, IPFS Companion, Someguy, Service Worker Gateway, and IPFS Check will lose their dedicated maintainers. That means no assigned Shipyard engineers handling releases, new features, bug fixes, or long-term stewardship.\n\nContributions to upstream projects including go-libp2p and js-libp2p will cease as well. Shipyard will end its work on IPFS specifications, standards, and technical coordination.\n\nThe infrastructure consequences are broader. Shipyard plans to stop operating ipfs.io, dweb.link, check.ipfs.network, delegated-ipfs.dev, IPFS bootstrap nodes, and collaborative clusters including Wikipedia-on-IPFS. Protocol Labs owns the associated domains and infrastructure and will decide what happens to them after Shipyard's departure.\n\nThose services carry significant traffic, according to Shipyard's own measurements. In a [July 23rd, 2025 analysis](https://ipshipyard.com/blog/2025-a-post-gateway-world/?ref=runtimewire), Wood and Schmahmann said ipfs.io and dweb.link handled 614 million requests and 45 terabytes of data for 10 million daily users. The figures were reported by Shipyard and have not been independently measured here.\n\n[Shipyard says it re-architected gateway infrastructure](https://ipshipyard.com/blog/2026-the-end-of-ipfs-at-shipyard/?ref=runtimewire) to handle about three times as much traffic while cutting operating and maintenance costs by roughly 80%. It also built inbrowser.link, which retrieves and verifies IPFS content in a browser. In May, [Shipyard began redirecting public gateway navigation to that service](https://ipshipyard.com/blog/2026-ipfs-gateways-redirect-inbrowser-link/?ref=runtimewire).\n\nCloudflare has supported Shipyard's public IPFS gateway infrastructure. In its [May 14th, 2024 announcement](https://blog.cloudflare.com/cloudflares-public-ipfs-gateways-and-supporting-interplanetary-shipyard/?ref=runtimewire), Cloudflare presented the transition as a way to strengthen independent stewardship. That support added traffic and responsibility to the organization whose anchor funding has now ended.\n\n### Decentralized code, concentrated maintenance\n\nIPFS software will remain open source, and outside contributors can continue developing it. That does not replace the people who triage bugs, coordinate releases, respond to security problems, operate bootstrap nodes, maintain specifications, and absorb the cost of public gateways.\n\nShipyard's [public profile in the Protocol Labs directory](https://directory.plnetwork.io/teams/cldvnvdoh00rju21kgexerzsx?ref=runtimewire) lists 10 members, including engineers who have spent years working on IPFS implementations and production infrastructure. Replacing that concentration of knowledge requires money, organizational ownership, and engineers willing to assume work that has largely been delivered as a public good.\n\nWood and Schmahmann had planned further work on simpler HTTP-native implementations, sustainable content routing, large SHA-256 objects, and pseudonymous retrieval through Tor and onion services. Those projects will end at Shipyard unless other maintainers take them forward.\n\nThrough September 30th, the co-founders say Shipyard will focus on transferring context and helping operators understand their dependencies. The remaining question belongs to the organizations that rely on IPFS: whether they will fund maintenance directly, take ownership of individual projects, or leave a smaller volunteer group to carry infrastructure that Shipyard says reaches tens of millions of users.", "url": "https://wpnews.pro/news/ipfs-maintainer-shipyard-winds-down-after-protocol-labs-declines-funding-renewal", "canonical_source": "https://runtimewire.com/article/ipfs-maintainer-shipyard-winds-down-protocol-labs-funding", "published_at": "2026-08-24 16:21:57+00:00", "updated_at": "2026-08-24 16:43:56.181664+00:00", "lang": "en", "topics": ["ai-infrastructure"], "entities": ["Shipyard", "Protocol Labs", "IPFS", "Cameron Wood", "Adin Schmahmann", "Kubo", "Helia", "Boxo"], "alternates": {"html": "https://wpnews.pro/news/ipfs-maintainer-shipyard-winds-down-after-protocol-labs-declines-funding-renewal", "markdown": "https://wpnews.pro/news/ipfs-maintainer-shipyard-winds-down-after-protocol-labs-declines-funding-renewal.md", "text": "https://wpnews.pro/news/ipfs-maintainer-shipyard-winds-down-after-protocol-labs-declines-funding-renewal.txt", "jsonld": "https://wpnews.pro/news/ipfs-maintainer-shipyard-winds-down-after-protocol-labs-declines-funding-renewal.jsonld"}}