Help us build a more resilient and
participatory internet through decentralization.
An Important Announcement As of January 2024, many of the core maintainers of IPFS and libp2p have begun working as a separate team in the Protocol Labs network. In this next chapter as an independent entity, we are excited to embark upon advancements to the Interplanetary Stack in service of web2 and web3 development teams — and we need your help! Shipyard depends upon ecosystem sponsorships and partners to keep the promise and potential of IPFS alive for the long term. We've secured a major 2-year commitment so far, and are raising an additional $3M in community contributions to sustain our work as technical stewards in 2024. These contributions will allow us to maintain several mission-critical implementations of IPFS and libp2p.

Work with us

Are you building on IPFS and libp2p and want direct access to our team technical experts? Our partners receive direct access to our technical team to support your development, contract services, and more.

Protocol Patron

Great for startups and any projects that use IPFS or libp2p

$450/ month

What's Included:

  •   SLA (48-hour response time)
  •   Shipyard Maintainers Channel
  •   Shipyard Sponsor

Network Node

Great for established projects with a dedicated dependency on IPFS and libp2p

$5000/ month

What's Included:

  •   Custom Version & Uptime Report
  •   Access to Slack Connect
  •   Shipyard Maintainers Channel
  •   SLA (24-hour response time)
  •   Shipyard Sponsor

About Shipyard

Interplanetary Shipyard is an engineering collective that delivers user agency through technical advancements in IPFS and libp2p. As the core maintainers of open source projects in the Interplanetary Stack (including IPFS, libp2p, Kubo, Rainbow, Boxo, Helia), and supporting performance measurement tooling (Probelab), we are committed to open source innovation and building bridges between traditional web frameworks and the decentralized ecosystem. To achieve this, our engineers work alongside technical teams in web2 and web3 to promote adoption and drive practical applications.

Read more about our IPFS and libp2p roadmap how we plan to further advance IPFS by migrating away from centralized gateways into native browsers in 2024.

Supported by:

Find us on the Internet: Twitter | Github