A host that's built to stick around
Fleek's hosting shut down in January 2026 and took sites with it. Your data on Pinner lives on a network of independent hosts paid to keep it, not on our servers. Pay with crypto or card. No KYC for crypto.
Any file, any size. Encrypted before it leaves your device.
A unique fingerprint derived from your file's contents.
A permanent link. Valid as long as your content is pinned.
Any file, any size. Encrypted before it leaves your device.
A unique fingerprint derived from your file's contents.
A permanent link. Valid as long as your content is pinned.
What happened to Fleek?
A hosting service that's no longer hosting
Encrypts and distributes your files
Host A
Encrypted shard
Host B
Encrypted shard
Host C
Encrypted shard
Host D
Encrypted shard
Encrypts and distributes your files
Host A
Encrypted shard
Host B
Encrypted shard
Host C
Encrypted shard
Host D
Encrypted shard
Storage
Your data lives on a network, not our servers
Zero-knowledge encryption
Keys never leave your device. We can't read your files.
Verifiable storage
Hosts prove they're holding your data. Or they don't get paid.
Open source
Fully open on GitHub. Don't take our word for it. Read the code.
Getting Started
Deploy your static site
If you have your site files (HTML, CSS, JS), deploy them to Pinner and get a live URL. Static sites, portfolios, documentation sites, and dApps all work. No server-side rendering or dynamic backends.
Frequently Asked Questions
Your site files (HTML, CSS, JS) and your custom domain if you had one. Content addresses (CIDs) are determined by your file's content, so the same files produce the same CIDs. Deploy your files to Pinner, point your domain, and you're live.
Fleek retired their IPFS hosting services in January 2026, and hosted sites went offline. Their hosting and storage services are no longer available.
At the distribution level, not much. We serve your site over HTTP and peer-to-peer, and if we stop operating, your site goes offline. The difference is storage: Fleek's data lived on their own infrastructure and disappeared when they shut down. Pinner stores data on the Sia network, where independent hosts are paid to store it and must prove they're doing it to get paid. The data doesn't live on our servers.
If you have the original files, yes. Content addresses (CIDs) are determined by your file's content, not by the provider. The same file has the same CID on any IPFS service.
Yes. If you have your IPNS private key, you can import it into Pinner and continue publishing to the same IPNS address. The address stays the same; only the publishing service changes.
Static sites: HTML, CSS, and JavaScript. Portfolios, documentation, landing pages, blogs generated by static site generators (Hugo, Astro, Next.js static export, Gatsby, Jekyll, 11ty, and more). No server-side rendering or dynamic backends.
What You Get
| Factor | Pinner |
|---|---|
| What you pay for | Storage and bandwidth only |
| Storage layer | Sia network: hosts prove they're storing your data to get paid |
| Content addressing | Every file gets a permanent, verifiable hash |
| Payment methods | Crypto or card. No KYC for crypto. |
| Static site hosting | HTML, CSS, JS. Deploy and go |
| Domain support | Custom domains with SSL, IPNS addresses |
| IPFS pinning | Standard CIDs and content addressing |
| Data durability | Your data lives on independent hosts, not one company's servers |
Built On
Your content stays pinned and available.
Permanent links, distributed across independent hosts. No single point of failure.