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.
IPFS Website Hosting / DELIVERY & RETENTION
IPFS website hosting, without the guesswork.
Choose a hosting arrangement you can explain: who keeps the files, how browsers retrieve them, and what happens when a release needs to change.
Compare responsibilities before plans
A hosting proposal may bundle storage, gateway access, naming, and deployment tools. Break those features into separate responsibilities before comparing plans. Confirm what an upload response means, when retention is complete, and which delivery limits apply. A large storage allowance does not tell you how a site will behave during a traffic spike or a provider incident.
Match the operating model to your team
Managed pinning can reduce node maintenance, while a self-operated node gives direct control over retained releases. Either model still needs monitoring, access recovery, and a publishing owner. A second copy can help, but only after you review shared dependencies such as the cloud region, billing account, and credential store. Do not count dashboards as proof of independence.
Budget for a real visitor journey
Measure the bytes and requests involved in a representative visit rather than multiplying every visitor by the entire repository size. Separate storage, outgoing traffic, gateway requests, domain services, backups, and operator time. Provider prices and limits change, so record the assumptions behind any estimate and check current terms before making a commitment.
Keep a way out
Save source revisions, approved artifacts, root CIDs, and the retention purpose of each release somewhere you control. Test moving a release to another retention arrangement before a migration becomes urgent. A portable artifact is most useful when another operator can identify it and retrieve its nested files without access to one particular dashboard.
Technical reference: IPFS persistence and pinning documentation. Review the relevant configuration before applying it to a production environment.
COMMON QUESTIONS
IPFS Website Hosting: the details
Is pinning the same as a gateway?
No. Pinning concerns retention; a gateway provides a retrieval interface. A provider may offer both, but the responsibilities remain separate.
Can a local laptop host production content?
It can provide content while reachable, but sleep, power, and connectivity interruptions need an availability plan. Do not make it the only copy by accident.
FIELD GUIDES
Go deeper in the Website Lab
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.