Loading page
Loading page
Storage · Pinata alternative
Run your own IPFS node with Kubo to add, pin and serve content on the peer-to-peer IPFS network.
Kubo was the first implementation of IPFS and is still the most widely used. IPFS addresses content by a hash called a CID instead of by a server location. If any node has the data for a CID, anyone can fetch it and check it is correct.
Kubo runs a node that joins the network, stores and announces the content you pin, and serves it. It includes a web UI, an HTTP gateway for browsers, an RPC API to control the daemon, and a command-line tool.
Kubo suits developers building on IPFS: web3 projects that store metadata, teams that publish static sites to IPFS, and anyone who wants a gateway they control. It is a tool for technical users, not a consumer file sync app.
Pinning services charge for stored data and gateway bandwidth. With your own node, your pins are under your control and you can run a gateway for your own apps.
The trade-off is resources and care. The project asks for at least 6 GB of RAM, and under-sized nodes can crash or fail to announce data. You must keep the RPC API off the public internet, watch disk use as pins grow, and update Kubo yourself. Content you publish is public to anyone with the CID.
Containers: ipfs/kubo:latest
Step 1
Choose the Starter plan. It costs $20 a month and runs up to 3 apps.
Step 2
Open App templates in the dashboard, choose IPFS (Kubo), and click Deploy. We set up the containers, secrets and domain.
Step 3
Wait a few minutes for the first deploy, then open your new URL and finish the IPFS (Kubo) setup screen.