What is Pinner?
Pinner is a content pinning service and aggregator for decentralized storage networks. We help you ensure your content remains available on decentralized networks by managing pinning operations across multiple networks.
Currently, Pinner supports IPFS (InterPlanetary File System) with plans to expand to additional storage networks.
What Pinner IS
- ✅ Pinning Service - We store and serve your content identifiers (CIDs) on our infrastructure
- ✅ Privacy-Focused - Your data stays yours; we don't mine or analyze your content for commercial purposes. We scan content we can access (like public IPFS) for abuse and legal compliance. Zero-knowledge services (coming soon) won't be scannable by design.
- ✅ Competitive Pricing - We offer straightforward, fair pricing without hidden subsidies
- ✅ Developer-Friendly - SDKs for JavaScript/TypeScript, CLI tools, and REST APIs
What Pinner IS NOT
- ❌ IPFS Gateway - We don't provide public HTTP gateways for content retrieval
- ❌ Content Delivery Network (CDN) - We don't optimize for low-latency content delivery
- ❌ File Hosting - We don't serve files directly to end users over HTTP (we do serve via the IPFS swarm)
Gateway Services
Pinner focuses on pinning; we don't bundle public gateways with our service. This keeps pricing transparent and our operations sustainable.
Why No Gateways?
We made a deliberate choice:
-
Fair Pricing - Gateways are expensive infrastructure. Bundling them forces all users to subsidize a service they may not need or want.
-
Sustainability - Serving open web content through gateways carries significant liability. Making them profitable requires pricing high enough to offset that risk. By focusing on pinning, we build a service that's sustainable long-term.
-
Clear Purpose - Pinning and gateways serve different needs. We excel at one: keeping your content available on decentralized networks.
Accessing Your Content
Since Pinner doesn't provide a gateway, you have options:
- Public Gateways - The IPFS Public Gateway Checker maintains a list of available public gateways. The IPFS Foundation operates these "public good gateways":
ipfs.io,dweb.link, andtrustless-gateway.link. Additional options include:eth.limo- ENS-powered gateway supporting multiple decentralized storage protocolsipfs.io- IPFS Foundation gatewaydweb.link- IPFS Foundation trustless gateway
- Local IPFS - Use IPFS Desktop, IPFS Companion, or ipfs-cli
- Build Your Own - Run a private gateway for your needs
- Paid Gateway - Contact us for custom gateway solutions with dedicated infrastructure and support
When to Use Pinner
| Use Case | Pinner Right for You? |
|---|---|
| Archiving important data on IPFS | ✅ Yes |
| Ensuring content availability | ✅ Yes |
| Building dApps with IPFS backend | ✅ Yes |
| Fast content delivery to users | ❌ Consider a CDN |
| Public file sharing via URL | ❌ Consider a gateway service |
| Static website hosting | 🔄 On our roadmap (semi-public gateway) |
Quick Summary
- Pinner = Pinning (keeping content available on decentralized networks)
- Pinner ≠ Gateway (serving content to users via HTTP)
- Gateway available? Contact us for custom solutions
- Why no default gateway? Better pricing, sustainability, focus