Run IPFS on a VPS: a practical Kubo operations checklist
Plan a node around administrative boundaries, storage, monitoring, retained releases, and recovery—not just a successful daemon start.
IPFS WEBSITE LAB / TOPIC
Pinning
Retention needs an owner.
Pinning connects an approved release to infrastructure expected to retain it. These guides introduce that responsibility, compare operating models, and carry it into a self-operated node checklist.
Do not use a cached browser response as a substitute for checking the retained release. Record which root CIDs matter, where copies are kept, and who receives a failed retrieval alert. Include a previous working release in a deliberate rollback plan. Reading the first-site and hosting guides together makes it easier to distinguish a successful upload from an ongoing availability arrangement.
Start with IPFS Website Hosting or IPFS VPS, then continue with the field guides below.
IPFS hosting, pinning, and costs: plan the whole delivery path
Compare local nodes, managed pinning, and gateway delivery without treating an upload or a cached page as an availability guarantee.
Build your first IPFS static website: from folder to CID
Prepare a portable static site, publish the right directory, and check that every page and asset survives the move to IPFS.