Ipfs Cluster is an open source coordinator for operators who run several IPFS nodes and want them to share the work of storing the same content. It is aimed at system administrators, developers and infrastructure teams who need to allocate, replicate and track pinned data across a group of IPFS daemons instead of a single machine. The project is free, released under the Apache 2.0 license, and written in Go.
The current release is v1.1.6, and the code repository was last updated on 2026-08-30, so the project is actively maintained at the time of writing. Ipfs Cluster for Windows suits people who are comfortable with the command line and with running background services. If you only want to browse IPFS content or run one node, a lighter tool will likely serve you better. This page explains where Ipfs Cluster fits and how to set it up carefully.
What Is Pinning and Why a Cluster Helps
IPFS identifies content by its hash rather than its location, and a node keeps a block only as long as it has a reason to. Pinning tells a node to keep specific content so that it is not removed during routine cleanup. On one machine this is simple. Across several machines, someone has to decide which node pins what, how many copies exist, and what happens when one node goes offline.
Ipfs Cluster handles that coordination. You submit a pin request to the cluster, and the peers agree on where the content should be allocated and replicated. The cluster also tracks the state of each pin, so you can see whether a file is fully pinned, still pending or failing on one node.
The practical benefit is redundancy. If one daemon is lost, copies held by other peers can still serve the content. The exact replication behavior depends on the settings you choose, so test with a small dataset before relying on it for anything important.
Who Should Use Ipfs Cluster for Windows
Ipfs Cluster is designed for people who run more than one IPFS node and need them to behave as a group. A small team publishing a shared document archive, for example, may want copies on two or three machines so that one failing disk does not make the archive unavailable.
Developers testing IPFS infrastructure are another natural audience. A cluster on a Windows workstation lets you experiment with allocation rules, replication and failover without renting servers. Because the tools expose an HTTP API, they can also be scripted into existing deployment or monitoring workflows.
It is less suited to casual users who simply want to view or share a file over IPFS. For that, a single node with a simple interface is easier to manage. Ipfs Cluster rewards patience: the setup only starts to make sense once you understand the difference between a node, a pin and a cluster peer.
How the Pieces Fit Together: Node, Peer and Client
A working setup has three layers. At the bottom is the IPFS daemon, usually kubo, which stores blocks and talks to the wider IPFS network. Next is the cluster peer, ipfs-cluster-service, which runs beside that daemon as a sidecar and decides what the daemon should pin.
Above the peers sits the client. ipfs-cluster-ctl sends commands to a peer's HTTP API, so you can request a pin, check its status or list what the cluster holds. Because the client works through the API, you can manage the cluster from another terminal or machine, as long as the API is reachable and properly secured.
Follower peers add another role. A follower joins an existing cluster to mirror its pin list, which suits backup or read-oriented setups. Understanding these roles makes the installation steps easier to follow and helps you decide which components you actually need.
Key features
Cluster peer service
Command-line client
Follower peers
How to install Ipfs Cluster on Windows
- 1
Get the release from GitHub
Open the Releases page of the official repository at github.com/ipfs-cluster/ipfs-cluster. Look for a Windows archive in the latest release, v1.1.6 at the time of writing. If no Windows build appears there, the source code can be compiled, but that route needs a Go toolchain and suits developers rather than everyday operators.
- 2
Verify the checksum
Download only from the official website or the Releases page. Compare the SHA-256 hash of the downloaded file with the checksum published alongside the release, for example with Get-FileHash in PowerShell. Do not run the file if the hashes differ.
- 3
Extract the binaries
Unzip the archive into a dedicated folder that you control. If you want to run ipfs-cluster-service and ipfs-cluster-ctl from any terminal, add that folder to your PATH environment variable and open a new terminal window to confirm the commands resolve.
-
Install the IPFS daemon
Ipfs Cluster runs alongside kubo, so install a kubo build and initialize its repository before starting the cluster service. Follow the kubo documentation for Windows-specific steps, and confirm that the daemon starts cleanly on its own first.
How to use Ipfs Cluster
Once the binaries are in place, the basic workflow is to start a daemon, initialize the cluster peer and then manage pins from the client. Begin with a small test file so you can see each stage clearly before you use the cluster for real data.
- Start the kubo daemon and confirm that it responds on its local API.
- Initialize ipfs-cluster-service and start the peer, pointing it at your running daemon.
- Check that the peer responds, using ipfs-cluster-ctl to read its status.
- Submit a small test pin with ipfs-cluster-ctl and watch its status change as the cluster processes it.
- Review where the pin was allocated, then add more peers only after the first one behaves as expected.
For machines that should only follow an existing cluster, use ipfs-cluster-follow instead of writing a full peer configuration by hand. Keep a note of each change you make, because a cluster is easier to debug when you can trace which setting caused a behavior.
Pros & cons
- Free and open source under the Apache 2.0 license
- Separate tools for running peers, controlling the cluster and following it
- Coordinates pinning and replication across several IPFS daemons
- Written in Go and recently updated, with the latest code change dated 2026-08-30
- Requires familiarity with IPFS concepts and the command line
- Needs a separate kubo daemon running alongside each peer
- Windows builds should be confirmed on the Releases page before you plan around them
- Built for operators, so it is not a casual file-sharing tool
Is Ipfs Cluster safe?
Ipfs Cluster is open source and free, but it runs as background services that talk to an HTTP API, so treat it like any server software. Get the program from the official GitHub repository or its Releases page, and verify the SHA-256 checksum or signature published with the release before running anything. A mismatch means the file should not be used.
Bind the API to localhost or a trusted private network unless you have deliberately configured authentication and access controls. An exposed cluster API can let strangers change pins or read cluster state. Keep kubo and the cluster tools on versions that work together, and read the release notes before upgrading a running peer.
- Official source only. Download from github.com/ipfs-cluster/ipfs-cluster. Ignore ads and lookalike domains.
- Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
- Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
Alternatives
Ipfs Cluster sits at a different level than many tools in this catalog. Kubo (IPFS) is the reference node that stores and serves content, and it is the daemon Ipfs Cluster builds on rather than a competitor. IPFS Desktop puts a node in the system tray for personal use, while Pinner CLI focuses on pinning content from the command line without coordinating several peers. Storj is a decentralized storage network with its own storage nodes, a different model from pinning on IPFS. Choose Ipfs Cluster when several IPFS daemons need to share pinning responsibilities, and choose a single node or a simpler pinning tool when one machine is enough.
Specifications
- Price
- Free
- Type
- Open source
- License
- Apache 2.0
- Latest version
- v1.1.6
- Last update
- 30 Aug 2026
- Windows support
- Likely (builds for Windows; check releases)
- Source code
- github.com/ipfs-cluster/ipfs-cluster
Frequently asked questions
Yes. Ipfs Cluster is free and released as open source under the Apache 2.0 license, so you can use, study and modify the code under its terms. Costs can still arise from the servers, storage or bandwidth you use to run your nodes, but the software itself has no price tag.
It is generally safe when you get it from the official GitHub repository and check the SHA-256 checksum or signature before running it. The main risk is operational rather than the download itself, since an exposed cluster API can be misused. Follow the safety guidance, keep the API on a private network, and review release notes before upgrading.
Yes, in practice. The cluster peer is designed to run alongside kubo (go-ipfs), the reference IPFS node, which does the actual storing and serving of content. Install and start kubo first, then connect the cluster service to it.
A cluster peer takes part in coordinating pins across the cluster, while a follower peer tracks a cluster through ipfs-cluster-follow without the full configuration of a regular peer. Choose the role based on whether the machine needs to take part in the cluster's decisions or simply mirror its state.
Its core tools are command-line applications. ipfs-cluster-service runs the peer, and ipfs-cluster-ctl manages it through the HTTP API. This makes it well suited to scripts and servers. If you prefer a visual approach for a single node, IPFS Desktop is the better fit.
A single node pins content only on its own disk. Ipfs Cluster allocates and replicates pins across several daemons and tracks their status centrally, so one machine failing does not automatically remove content from the group. That coordination adds work, so it is worth the effort mainly when redundancy matters.
Verdict
Ipfs Cluster for Windows suits operators and developers who need several IPFS daemons to share pinning and replication, and who are comfortable with the command line. It is free, open source under Apache 2.0, and recently updated. It is not a casual file-sharing app. If you run one node or only want to browse IPFS content, a simpler tool will serve you better. Start with a test cluster on non-critical data, and check the latest version on the official website before you deploy.