kubo
The original and most widely used IPFS implementation in Go, providing a full-featured node for decentralized content-addressed storage.
What is kubo?
Kubo is the first and most widely used implementation of the InterPlanetary File System (IPFS), written in Go. It provides a complete IPFS node that enables decentralized, content-addressed storage and peer-to-peer data sharing, forming a core building block for the distributed web. It runs as a network service with features like a command-line interface, WebUI dashboard, and HTTP gateway.
Developers and operators building decentralized applications (dApps) or infrastructure that require resilient, peer-to-peer data storage and sharing. This includes public node operators, backend engineers integrating IPFS into services, and researchers experimenting with distributed web protocols.
Developers choose Kubo for its proven stability, broad ecosystem interoperability, and comprehensive feature set as the original IPFS implementation. Its opinionated approach to standards like UnixFS, HTTP Gateways, and Bitswap ensures maximum compatibility across the IPFS network.
Overview
IPFS implementation in Go: a daemon that stores and serves content-addressed data, with a CLI, HTTP Gateway, and RPC API
Use Cases
Best For
- Running a full, production-ready IPFS node for decentralized application backends.
- Operating a public HTTP gateway to serve IPFS content to traditional web browsers.
- Managing and pinning large datasets with content-addressed storage via its CLI and API.
- Experimenting with IPFS core protocols (Bitswap, DHT) in a stable, reference implementation.
- Building tooling or services that require programmatic control of an IPFS daemon via its HTTP RPC API.
- Setting up a node with content filtering capabilities for public or regulated deployments.
Not Ideal For
- Projects needing a lightweight, embeddable IPFS client for browser or mobile apps
- Environments with strict memory constraints (e.g., less than 6 GB RAM) where instability risks are high
- Use cases requiring only read-only access to IPFS content without node management overhead
- Teams preferring fully GUI-driven node management without CLI dependency
Pros & Cons
Pros
As the first and most widely used IPFS implementation, Kubo offers proven reliability and maximum ecosystem interoperability, ensuring compatibility with standard protocols like UnixFS and Bitswap.
Includes a full CLI, WebUI dashboard, HTTP gateway, and RPC API, providing out-of-the-box tools for node management, content serving, and programmatic control.
Backed by the IPFS Shipyard team with regular releases, extensive documentation, and active community forums, reducing risks of abandonment or stale development.
Offers Docker images, detailed configuration guides, and metrics monitoring, making it suitable for robust, scalable node deployments in decentralized infrastructures.
Cons
Requires at least 6 GB of RAM and multiple CPU cores for optimal performance, with explicit warnings about instability, OOM errors, and data inaccessibility on underprovisioned hardware.
Advanced features like delegated routing or content blocking demand manual tuning and deep protocol knowledge, creating a steep learning curve beyond basic node operation.
Community-maintained packages (e.g., via PPA or Homebrew) come with security warnings, as the maintainers do not vouch for supply chain integrity, pushing users toward building from source for safety.
Frequently Asked Questions
Related Projects
go-ethereumGo implementation of the Ethereum protocol
lndLightning Network Daemon ⚡️
cosmos-sdkFramework for building performant, customizable blockchains with native interoperability
tendermint⟁ Tendermint Core (BFT Consensus) in Go
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.