Static sites only. If your build produces HTML, CSS, and JavaScript files, it works. Hugo, Astro, Next.js static export, Gatsby, Jekyll, 11ty, and more. Dynamic server-side rendering, serverless functions, and edge functions are not supported.

It depends on what you need. Pinner hosts built static files with content-addressed storage on a peer-to-peer network. It does not offer serverless functions, edge functions, CI/CD, or preview deployments. If you need those features, keep your current platform. If you want content-addressed hosting with no vendor lock-in on storage and no per-seat charges, Pinner is worth a look.

Content addressing: every file gets a permanent, verifiable hash that doesn't change. Peer-to-peer storage means your content lives on independent providers, not one company's servers. No vendor lock-in. No per-seat pricing. Pay for storage and bandwidth only. Crypto payments with no KYC.

Yes. Use your current platform for your development workflow (previews, CI/CD, serverless functions) and Pinner for the final static asset hosting layer. Pinner hosts standard static files, so you can build anywhere and deploy to Pinner.

Your static files are stored on the Sia network, where independent storage providers host your data. Providers only get paid when they cryptographically prove they're storing your files. The storage layer is decentralized, not locked to a single provider. The serving layer uses standard HTTP gateways.