awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
ipfs avatar

ipfs/kubo

0
View on GitHub↗
17,056 stars·3,165 forks·Go·35 viewsdocs.ipfs.tech/how-to/command-line-quick-start↗

Kubo

Kubo is a peer-to-peer implementation of the InterPlanetary File System (IPFS) designed for decentralized data storage and content delivery. It uses content-addressing, directed acyclic graphs, and distributed hash tables to identify, distribute, and retrieve data across a network without relying on central servers.

The project differentiates itself by providing a virtual filesystem via FUSE, which maps decentralized network namespaces to local operating system directories for direct file access. It also includes integrated HTTP gateways that translate peer-to-peer content into standard web traffic, enabling the hosting of static websites and the delivery of verifiable data to web browsers.

The system covers a broad range of capabilities including network orchestration, real-time message propagation via PubSub, and content pinning to ensure data persistence. It features comprehensive monitoring through Prometheus and OpenTelemetry, alongside security tools for content filtering, network address blocking, and automated TLS certification.

Kubo can be deployed as a standalone daemon, integrated as a library into custom applications, or run via containerized images.

Features

  • Content-Addressable Storage - Identifies data by the hash of its content rather than its location to ensure integrity and deduplication.
  • Peer-to-Peer File Sharing - Provides a decentralized system for hosting and retrieving files across a peer-to-peer network.
  • Peer-to-Peer Distribution Protocols - Implements a decentralized system for distributing and retrieving data using content-addressing and distributed hash tables.
  • Content Pinning - Allows locking specific content identifiers to the local node to prevent garbage collection.
  • Filesystem Mounts - Maps the peer-to-peer filesystem onto the local operating system directory structure for direct file access.
  • Network Namespace Mounting - Exposes network namespaces as local directories for access via standard filesystem operations.
  • P2P Store Mounting - Exposes a peer-to-peer data store as a local directory to interact with network files.
  • Network Namespace Exposure - Exposes network namespaces to the operating system as local directories for use with standard filesystem tools.
  • Content Pinning - Prevents automatic garbage collection of specific data to ensure it remains stored on the local node.
  • Content Identifiers - Applies specific profiles to ensure content identifiers are generated reproducibly across different implementations.
  • Content-Addressable Transfers - Implements data movement based on content hashes rather than traditional server locations to ensure integrity.
  • Content Provider Advertising - Publishes provider records to the routing system to announce content availability to other peers.
  • Decentralized Content Distribution - Distributes and retrieves data across a decentralized network using content-addressing and distributed hash tables.
  • Decentralized Naming Systems - Shares and resolves naming system records in real-time using the Distributed Hash Table or delegated publishers.
  • Decentralized Website Hosting - Hosts websites at custom domains by linking DNS records to content identifiers.
  • DNS Resolution - Maps human-readable domain names to decentralized network addresses for efficient content and peer discovery.
  • HTTP Gateways - Translates peer-to-peer content into standard web traffic for access through traditional web browsers.
  • Peer-to-Peer Networking - Provides tools for deploying and managing peer-to-peer nodes, including routing and peer discovery.
  • Bootstrap Node Discovery - Uses trusted bootstrap nodes to discover the network and locate other peers during startup.
  • HTTP-to-P2P Translation - Translates standard web requests into peer-to-peer protocol calls to make decentralized data accessible via browsers.
  • PubSub Messaging Systems - Provides a real-time message distribution system using publish-subscribe patterns for network-wide data propagation.
  • Content Path Mapping - Maps decentralized content paths to a local directory structure using a filesystem in userspace.
  • FUSE Virtual Filesystems - Maps decentralized content and network namespaces to a local operating system directory for standard file access.
  • Directed Acyclic Graphs - Organizes related blocks of data into a hierarchical structure to represent files and directories.
  • Distributed Hash Tables - Maps content identifiers to peer network addresses across a decentralized network to enable efficient data discovery.
  • P2P Routing Stacks - Implements a specialized routing stack to manage how the system discovers content providers and resolves decentralized records.
  • Deduplication - Adds files to the system without duplicating the physical space they occupy on disk.
  • Node Management Interfaces - Exposes internal system operations and configuration settings through a standardized remote procedure call interface.
  • Storage Configurations - Defines the on-disk storage structure, including mount points and storage types for data persistence.
  • Publish-Subscribe Messaging - Distributes real-time updates and records across the network using a publish-subscribe mechanism for low-latency discovery.
  • NAT Traversal Mechanisms - Automatically finds and advertises relay addresses for nodes located behind restrictive NATs.
  • NAT Traversal - Upgrades relayed connections to direct connections using hole punching when port forwarding is unavailable.
  • Encrypted Relaying - Routes network traffic through intermediary nodes to enable connectivity for peers behind restrictive NAT firewalls.
  • Routing Delegation - Offloads peer discovery and record lookups to remote HTTP endpoints to reduce local resource consumption.
  • Node Management RPCs - Exposes core node functions and data organization over an HTTP API for external clients.
  • Library Integrations - Embeds core peer-to-peer functionality directly into custom applications rather than running a standalone daemon.
  • PubSub Message Propagation - Distributes updates instantly using a publish-subscribe mechanism to reduce name resolution latency.
  • Circuit Relay Hosting - Acts as a circuit relay to help other peers establish connections when situated behind firewalls.
  • Traffic Routing - Uses a client-server model to delegate routing queries to specialized routers.
  • Virtual Filesystem Schemes - Provides a writable mount point to manipulate content-addressed data using standard system tools.
  • Content - Blocks specific content from being served by a node to comply with operator policies.
  • Content Filtering Rules - Prevents the node from hosting or routing specific data based on defined rules and public blocklists.
  • Metric and Performance Monitors - Exports internal system metrics and provider statistics to external tools for health and resource tracking.
  • Node Management Interfaces - IPFS controls node operations via a command-line tool, a web-based user interface, and a remote procedure call API.
  • Observability Tracing - Integrates the OpenTelemetry suite to track request flows and internal operations for performance analysis.
  • Prometheus Exporters - Provides a Prometheus endpoint to surface internal performance data for external monitoring.
  • Administrative Interfaces - Administers configuration and secret keys through a restricted interface bound to specific network addresses.
  • RPC Integration Interfaces - Manages node operations and settings programmatically through a remote procedure call interface.
  • Data Storage and Search - Go implementation of the InterPlanetary File System protocol.
  • Databases & Data - Implementation of the IPFS protocol for decentralized storage.
  • Distributed Filesystems - Peer-to-peer filesystem for global data distribution.

Star history

Star history chart for ipfs/kuboStar history chart for ipfs/kubo

How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI

Projects sharing features with Kubo

These projects share indexed features with Kubo. Shared tags can include platform or build tooling; verify the primary use case before treating a result as a replacement.
  • ipfs/ipfsipfs avatar

    ipfs/ipfs

    23,137View on GitHub↗

    IPFS is a peer-to-peer hypermedia protocol and content-addressed storage system that identifies data by cryptographic hashes rather than network locations. It enables the creation of a decentralized web by organizing files and directories as directed acyclic graphs of linked content identifiers. The project differentiates itself through the use of a distributed hash table for locating peers and a system of signed records to map human-readable names to changing content. It also provides HTTP gateways that translate standard web requests into peer-to-peer queries, allowing decentralized data to

    ipfsipfs-protocolipfs-web
    View on GitHub↗23,137
  • ipfs/go-ipfsipfs avatar

    ipfs/go-ipfs

    17,059View on GitHub↗

    go-ipfs is an implementation of an IPFS node, providing a distributed filesystem and a content-addressable storage system. It enables the storage and retrieval of data based on unique cryptographic hashes rather than fixed network locations, allowing files to be shared across a peer-to-peer network without a central authority. The system utilizes a distributed hash table and a peer-to-peer gossip protocol to route requests and propagate network state and metadata. It organizes data using a Merkle DAG structure to support efficient deduplication and versioning of content. Capabilities include

    Go
    View on GitHub↗17,059
  • ipfs-shipyard/ipfs-desktopipfs-shipyard avatar

    ipfs-shipyard/ipfs-desktop

    6,535View on GitHub↗

    ipfs-desktop is a graphical application for managing a local IPFS node, hosting content, and interacting with the peer-to-peer network. It serves as a desktop client that provides a visual interface for content-addressed storage management, peer-to-peer file sharing, and the administration of the node lifecycle. The project differentiates itself by providing a comprehensive suite of controllers for node health, gateway routing, and static site hosting. It includes a dedicated content-addressed storage browser for importing and organizing files, a gateway controller to route network content th

    JavaScript
    View on GitHub↗6,535
  • hellozeronet/zeronetHelloZeroNet avatar

    HelloZeroNet/ZeroNet

    18,748View on GitHub↗

    ZeroNet is a decentralized web browser and server that enables the hosting and accessing of websites without central servers. It functions as a peer-to-peer content distribution network that utilizes BitTorrent and Bitcoin cryptography to replicate and share site data across a distributed network of users. The system emphasizes censorship-resistant publishing and privacy through the integration of hidden services to anonymize network traffic. Site identity and content updates are managed via a cryptographic system using public-key pairs instead of centralized account passwords. The platform

    JavaScript
    View on GitHub↗18,748
Compare all 30 related projects→

Frequently asked questions

What does ipfs/kubo do?

Kubo is a peer-to-peer implementation of the InterPlanetary File System (IPFS) designed for decentralized data storage and content delivery. It uses content-addressing, directed acyclic graphs, and distributed hash tables to identify, distribute, and retrieve data across a network without relying on central servers.

What are the main features of ipfs/kubo?

The main features of ipfs/kubo are: Content-Addressable Storage, Peer-to-Peer File Sharing, Peer-to-Peer Distribution Protocols, Content Pinning, Filesystem Mounts, Network Namespace Mounting, P2P Store Mounting, Network Namespace Exposure.

Which projects share features with ipfs/kubo?

Projects with overlapping indexed features include: ipfs/ipfs — IPFS is a peer-to-peer hypermedia protocol and content-addressed storage system that identifies data by cryptographic… ipfs/go-ipfs — go-ipfs is an implementation of an IPFS node, providing a distributed filesystem and a content-addressable storage… ipfs-shipyard/ipfs-desktop — ipfs-desktop is a graphical application for managing a local IPFS node, hosting content, and interacting with the… hellozeronet/zeronet — ZeroNet is a decentralized web browser and server that enables the hosting and accessing of websites without central… ipfs/js-ipfs — js-ipfs is an HTTP client library that connects to any IPFS daemon, enabling JavaScript applications to interact with… fosrl/pangolin — Pangolin is a zero-trust remote access platform designed to provide secure, identity-aware connectivity to private…