Protocol Lab Shuts Down IPFS Funding – Shipyard Retreats

I’ll be honest: as I write this, I feel a bit disheartened. IPFS—the revolutionary decentralized storage network that brought us all a step closer to a freer, more censorship-resistant web—now faces an uncertain future. And that’s because the project is missing something that ultimately sustains most decentralized initiatives: stable, long-term support.
Shipyard, the team that quietly pulled the strings for years, kept the protocol running, and supplied the community with documentation and tools, is now stepping back. The reason? Funding from Protocol Labs—the deep-pocketed backer behind IPFS—has dried up. Come December, it’s all over—and despite their best efforts, Shipyard couldn’t find a way to keep the project alive on their own.
“Without this support, we can no longer provide the necessary resources,” is the diplomatic way of saying, “We’re giving up because we’ve run out of oxygen.” And who could blame them? Open-source projects like IPFS thrive when people pour in time, passion, and sometimes even their careers—but at the end of the day, rent, salaries, and server costs still need to be paid.
IPFS Without Steady Maintenance: A Domino Effect?
One might think, “Wait, the protocol still exists, right? It’ll keep running somehow.” Unfortunately, that’s not entirely accurate. IPFS is like a finely tuned clockwork—when one gear fails, the whole machine stalls. Shipyard wasn’t just a development team; they were essentially the maintenance crew for critical parts of the network. Without them, vital public services like IPFS-Cluster or bootstrapping nodes (which help new users join the network) could slow down, become unstable, or even collapse.
Protocol Labs, the organization behind IPFS and Filecoin, now faces a tough choice: “Do we save the project—or let it wither away?” There’s been no official statement yet, but I’d wager they’re feverishly exploring options. Maybe another team takes over. Maybe a new funding strategy emerges. Or perhaps the project is gradually decommissioned.
The Bitter Truth: Decentralization Is Great—But Who Pays?
Here’s the core issue, and it’s far from new: How do we fund open-source infrastructure in the long run? Many of crypto and Web3’s grandest visions sound inspiring—until reality hits: someone eventually has to foot the bill. And often, that someone isn’t the user who just wants to store data decentralized.
Shipyard was one of t



he few teams that tackled the problem head-on. They didn’t just write code—they created documentation, tutorials, and community support. In decentralized tech, these contributions are often overlooked because “everyone’s supposed to contribute for free.” But let’s be real: if no one is paid for their work, who’s left in the end?
Three Possible Paths Forward
The future of IPFS now depends on who fills the void—or whether the project survives at all. Three scenarios loom large:
1. Protocol Labs Steps In
The most obvious solution. Perhaps Protocol Labs assembles a new team or takes maintenance in-house. But: Big corporations rarely act out of pure altruism. If they keep the project alive, it’s likely because they see long-term value—whether for Filecoin, their reputation as champions of open tech, or both.
2. The Community Takes Over
Open-source history is full of projects kept alive by volunteers. Think Linux or Wikipedia—both run because people dedicate time without pay. But for IPFS, this would be a massive undertaking. Without paid developers, maintenance becomes a side hustle, and sooner or later, burnout sets in.
3. Commercialization
Parts of IPFS could transition into paid services while the core remains open source. Pragmatic on the surface—but caution is due. If too much shifts behind closed doors, IPFS risks losing its decentralized soul.
A Warning to the Industry
I believe Shipyard’s story should serve as a lesson. The Web3 world talks endlessly about freedom, censorship resistance, and individual empowerment—but if we don’t figure out how to sustain these projects, many will end up as hollow shells.
IPFS is an invaluable tool. It lets us store data without a central authority deciding what’s allowed. But without people willing to maintain the infrastructure, this revolutionary network could become a ghost ship—present, but no longer seaworthy.
What Can We Do?
If you use IPFS or care about decentralized tech, this is the moment to act. Whether you contribute time, knowledge, or even money, every bit helps. Support the community, improve documentation, or donate to projects working on its evolution.
Because one thing is certain: technology alone isn’t enough. It needs people willing to keep it alive. And if we want IPFS—and other decentralized projects—to have a future, we must ask ourselves today how to make that happen. Not in a year, or two. Right now.