ipfs infrastructure maintenance deprecation devops

Shipyard winds down IPFS maintenance September 2026

Protocol Labs defunds Shipyard; Kubo, Helia, Boxo, and public IPFS infrastructure lose dedicated maintainers—plan migration or alternatives now.

Summary

If you run IPFS nodes, use Kubo/Helia, or depend on ipfs.io/dweb.link, your tooling enters maintenance-only mode. No new features, uncertain bug-fix cadence, and public bootstrap/gateway infrastructure status unknown until Protocol Labs decides.

Why it matters

Implementation verdict

Replaces: Shipyard as your IPFS vendor support. Requires: immediate audit of which projects you depend on (Kubo, Helia, Boxo, IPFS Desktop, Companion, etc.) and contingency plans for ipfs.io/dweb.link services by Sept 30, 2026. Not worth waiting—start forking critical paths or switching to alternatives now if you can't self-maintain.

Sources

1.Protocol Labs has informed us that it will not be renewing Shipyard's funding
2.Our final day of our IPFS related work will be September 30, 2026
3.Projects maintained by Shipyard will no longer have dedicated maintainers responsible for new features, bug fixes, releases, or long-term stewardship. These include: Kubo, Helia, Boxo, Rainbow, IPFS Desktop, IPFS Companion, Someguy, Service Worker Gateway, IPFS Check, and others
4.Shipyard will cease operating the public infrastructure it currently manages, including ipfs.io, dweb.link, check.ipfs.network, delegated-ipfs.dev, the IPFS bootstrap nodes

Dev Signal

Get briefs like this in your inbox — free, every weekday.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs