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 / COLLECTION
Infrastructure
Keep content reachable.
Hosting is a set of responsibilities rather than a single storage number. Explore retained copies, gateways, readable names, self-operated nodes, and the operating work around them. Separate each layer before comparing providers or changing production configuration.
Read the hosting guide for the cost and responsibility model, the domain guide for DNSLink and HTTPS, and the VPS checklist for self-operation. Keep a release manifest and meaningful retrieval checks across all three. The practical goal is not an unsupported promise of permanent availability; it is an architecture whose dependencies, limits, and recovery path you understand.
Start with IPFS Website Hosting or IPFS Hosting, 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.
DNSLink and IPFS gateways: connect a domain without breaking releases
Understand what DNSLink changes, what HTTPS delivery still needs, and how to test a custom domain before switching its published release.