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 Hosting / THE INFRASTRUCTURE MAP
Know what each hosting layer does.
IPFS hosting is a system of responsibilities. Start with an architecture map, then decide which parts to operate and which parts to obtain from a provider.
Content and providers
A published release needs reachable infrastructure that can provide its content. Record where the approved directory is retained and how you will verify retrieval after updates or maintenance. Do not infer that a gateway response establishes the existence of an independent retained copy. The reader-facing delivery route and the underlying provider can share dependencies.
Gateways and browser access
An HTTP gateway allows browsers to request IPFS content through ordinary web URLs. Gateway origin structure matters when the content runs scripts or interacts with browser storage. For application interfaces, review subdomain or DNSLink gateway arrangements that provide an intentional origin boundary. Test the public route you support rather than rotating through gateway names without understanding their configuration.
Naming and HTTPS
DNSLink can signal which content path a domain name refers to. Serving the website directly through HTTPS still requires an appropriate hosting or gateway arrangement and working domain configuration. Keep both layers in your release notes. If a public domain and a DNSLink record are updated separately, verify that they refer to the intended corresponding release.
Operations and observation
A useful monitoring plan distinguishes process liveness, content availability, domain resolution, HTTPS delivery, and frontend correctness. Choose representative pages and assets, observe them from outside your own server, and record exact failures. Assign an owner to each layer. That makes a report of an unavailable website actionable instead of sending every incident to the same generic restart procedure.
Technical reference: IPFS gateway best practices. Review the relevant configuration before applying it to a production environment.
COMMON QUESTIONS
IPFS Hosting: the details
Should I use a public gateway as my entire hosting plan?
Treat its operator, limits, origin model, and availability as explicit dependencies. A public retrieval endpoint does not replace your own retention and recovery plan.
Do I need to run a gateway to use IPFS?
Not necessarily. You can use other delivery arrangements while retaining content independently. Choose according to your operational requirements.
FIELD GUIDES
Go deeper in the Website Lab
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.