Plans and pricing
Plan rows below mirror the Crust Network pricing page at the time of last verification. Always confirm on the official pricing URL before purchasing, since storage, bandwidth, and feature allowances change.
| Plan | Price | Storage | Bandwidth | Highlights |
|---|---|---|---|---|
| On-chain storage order | Pay per file in CRU | Per file, no account cap | Retrieval via public IPFS gateways |
|
Features
SDK languages: JavaScript, Substrate APIs, Any IPFS Pinning Service client
Headquarters: Decentralized (Polkadot ecosystem)
Strengths
- On-chain proofs reduce trust-in-vendor risk; you can verify storage independently of any single operator.
- W3Auth endpoint speaks the standard IPFS Pinning Service spec, so ipfs-cli and ipfs-cluster work out of the box.
- Cross-chain pinning means a Polygon, Ethereum, or BNB contract can trigger a Crust order without a Substrate dependency.
Considerations
- Paying in a volatile native token is a non-starter for some procurement teams.
- Retrieval performance varies with the responsiveness of the storage nodes serving your file; no single SLA.
Sources
- Crust IPFS W3Auth Pinning Service — https://wiki.crust.network/docs/en/buildIPFSW3AuthPin
- Crust storage primer — https://wiki.crust.network/docs/en/build101
- Crust on Polygon docs — https://docs.polygon.technology/tools/storage/crusthelpers
Compare other IPFS providers
See the full vendor neutral comparison at /ipfs or jump directly to the other providers below.
FAQ
Frequently asked questions
Does Crust Network offer a free tier?
No subscription; pay per storage order with CRU tokens.
How is Crust Network priced?
Pay-per-file in CRU. The order amount depends on file size and replication target; the network distributes the payment to the storage nodes that hold and prove the file.
What SDKs does Crust Network ship?
Crust Network provides clients for JavaScript, Substrate APIs, Any IPFS Pinning Service client. See the official docs for installation and usage.
When should I pick Crust Network over other IPFS providers?
Crypto-native teams that want verifiable, decentralized pinning paid on-chain rather than monthly invoices. On-chain proofs reduce trust-in-vendor risk; you can verify storage independently of any single operator.