Your data.
Your rules.
Website hosting, IPFS pinning, and private storage.
No one else can read your files, not even us.
No vendor lock-in, no hidden fees.
No ID required for crypto payments
Built on Sia·Open source·Zero-knowledge encryption
design-assets.sketch (28 MB)
project-backup
15 files (2.3 GB)
Just now
photos
29 files (345 MB)
2 days ago
quarterly-report.pdf (13 MB)
design-assets.sketch (28 MB)
project-backup
1 file (1.2 MB)
7 days ago
Four ways to store
Simple tiered pricing. No hidden fees, no seats.
Private Storage
Encrypted storage where only you hold the keys. Personal use or build apps on the Sia network.
Store Privately →S3 Storage
S3-compatible object storage backed by the Sia network. Run your own gateway appliance.
S3 Compatible →Website Hosting
Host static websites on a peer-to-peer network. Replicas across independent providers, not one company's server.
Pin a zip or upload your build folder: CLI, GitHub Action, and API available.
IPFS Pinning
Pin files on a peer-to-peer network. They stay online as long as they're pinned.
Start Pinning →Built On
The problem with cloud storage nobody talks about
Your cloud provider can read your files
Traditional storage encrypts data, but they hold the keys. You're trusting a promise, not an architecture.
Deleting data doesn't mean it's deleted
You have no way to verify your data is actually gone. 'We deleted it' is not the same as 'it's gone.'
The real price is never on the pricing page
Egress fees, API call charges, support tiers, and lock-in costs add up. You find out after you're committed.
What we do better
We can't read your files
Zero-knowledge encryption means even we don't have the keys. That's not a promise. It's the architecture.
We keep our word
Uptime we commit to, pricing you can understand. No hidden fees, no bait-and-switch tiers.
You can leave
Open standards, no export fees, no lock-in. Your data stays yours even when you walk away.
Pin. Host. Store.
Upload to IPFS. Host websites. Store private data with zero-knowledge encryption. Three products, one platform, one set of credentials.
Why Pinner?
| Factor | Traditional Cloud | Private Storage | Public (IPFS) |
|---|---|---|---|
| Can we read your data? | Yes | No. Zero-knowledge encryption means we can't read your files | Yes, but it's public |
| Pricing | Complex tiers, hidden fees | Simple plans, bundled storage | Simple plans, bundled storage |
| Ownership | They can delete your data | Your data, your rules | Your data, your rules |
| Lock-in | Export fees, proprietary formats | Open standards, leave anytime | Open standards, leave anytime |
| Infrastructure | Centralized data centers | Peer-to-peer storage | Peer-to-peer storage |
| Payment options | Credit card only, ID required | Crypto or card. No ID for crypto | Crypto or card. No ID for crypto |
Questions answered
Website Hosting
Point your domain to Pinner via DNS. Your site loads at yourdomain.com with HTTPS.
Any static site generator. Hugo, Astro, Next.js static export, Gatsby, Vite, or plain HTML. Build your site, upload the output, and Pinner hosts it.
Your files are stored on the Sia network, where independent providers host your data and only get paid when they prove it's there. The serving layer runs through our gateway. A CDN layer is in progress.
IPFS Pinning
The technology behind the hosting. Your site gets a permanent, verifiable address. Tied to your files, not to us. Change the files, get a new address. Don't change them, the same link works.
Pinned means your files stay online. Unpinned content can be garbage-collected by the network. Pinned content is kept persistently.
Yes. IPFS is a public network. Anyone with the content address can retrieve it. For private data, use private storage with zero-knowledge encryption instead.
Private Storage
No. Zero-knowledge encryption means even we don't have the keys. Only you can decrypt your data.
IPFS pinning is public, content-addressed storage. Anyone with the address can see it. Private storage encrypts your data before it leaves your device. No one can read it without your keys: not us, not the storage hosts, not the network.
Yes. Private storage is not content-addressed. When you delete a file, it's gone. No ghost copies floating on the network, no caches that outlive the delete. Storage hosts are paid to keep data, and they lose income when it's removed.
S3 Storage
Yes. The S3 API is built into the open-source gateway you deploy yourself. Standard S3 operations work out of the box.
Yes. Deploy the gateway on your server, then point any S3 client, CLI, SDK, or backup tool at your own endpoint.
General
Founding Offer: first 50 accounts get their rate locked for life, a 30-day money-back guarantee, and a deployment promise: create a website and if it isn't live in 5 minutes, we'll deploy it for you. Pay for storage and bandwidth. No hidden fees.
Pay for storage and bandwidth. No hidden fees, no API call charges. Monthly or annual. Card or crypto.
Founding Offer
First 50 accounts get their rate locked for life. After that, standard terms apply.
- ✓Rate locked for life
- ✓30-day money-back guarantee, no questions asked
- ✓Create a website and if it isn't live in 5 minutes, we'll deploy it for you
- ✓Free migration from your current host
Pay with crypto or card
Simple pricing, upgrade whenever
Simple, transparent pricing. Pay for storage and bandwidth. No hidden fees, no API call charges. Pick a plan that fits the needs of any project.
Your data is yours.
Private storage. No vendor lock-in. No data mining.