IPFS decentralizes everything except the budget: Shipyard hands off Kubo, Helia and ipfs.io by Sept 30

Who owns what is the awkward part. Shipyard supplied the engineers; Protocol Labs owns the domains and infrastructure behind ipfs.io, dweb.link and the rest, and it decides what happens to them once Shipyard is gone ^[5]. Moving maintainers into a Delaware nonstock corporation ^[6] did not move the hostnames that other people's code has already hard-coded. The protocol layer is genuinely indifferent to who runs a gateway. A client config file is not.

Shipyard named this exposure itself at launch, asking aloud what happens when a single funder changes strategy or prioritizes different work ^[7]. The answer was supposed to be grants, commercial support and contracted engineering, with $3 million sought in community contributions and early backing from Optimism RetroPGF, Cloudflare, Pinata, Fission and CoopHive ^[8]. Protocol Labs remained the anchor anyway, and its non-renewal is what the August announcement points to ^[9]. Two years of diversification did not change who could switch the work off.

The load being handed over is not trivial. Shipyard's own July 23 analysis put ipfs.io and dweb.link at 614 million requests and 45 terabytes for 10 million daily users ^[11], numbers the publisher says have not been independently measured ^[12]. Divide the bytes by the requests and the average response is about 73 kB ^[16], which describes a web of small content-addressed objects rather than heavy media. The window those 614 million requests cover is not stated, so the per-user rate cannot be derived from it.

Shipyard also says it re-architected the gateways to carry roughly three times the traffic while cutting operating and maintenance cost by about 80% ^[13]. Per unit of traffic that works out near a fifteenth of the earlier cost ^[17]. Which cuts both ways: a successor inherits the efficient version, and anyone who lets it lapse and rebuilds later starts again from the pre-optimization bill.

For an operator the audit is mechanical rather than clever. URL builders and SDK defaults containing ipfs.io or dweb.link. Nodes still dialing Shipyard-operated bootstrap peers. Routing calls to delegated-ipfs.dev or Someguy. CI steps that reach check.ipfs.network ^[4][2]. Kubo, Helia and Boxo will still compile on October 1. What ends is the assigned engineer whose job was the next release and the next bug fix ^[2], along with Shipyard's contributions to go-libp2p, js-libp2p and IPFS specification work ^[3]. Nobody has published what Protocol Labs was paying for that ^[10], which means the people best placed to replace it are bidding blind.