Mudassir Khan

IPFS provider

Crust Network — Pricing, Features, SDKs

Crust Network is a Substrate-based decentralized storage protocol that adds on-chain incentives to IPFS pinning. You submit a storage order with a file's CID and CRU payment; the network selects storage nodes, which periodically publish Merkle proofs on-chain to show they are still holding the data. An IPFS W3Auth Pinning Service endpoint lets ordinary IPFS pinning clients talk to the network without Substrate code.

Visit Crust NetworkRead the docsPricing

Free tier

No subscription; pay per storage order with CRU tokens.

Pricing model

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.

Best for

Crypto-native teams that want verifiable, decentralized pinning paid on-chain rather than monthly invoices.

Last verified

2026-06-02

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.

PlanPriceStorageBandwidthHighlights
On-chain storage orderPay per file in CRUPer file, no account capRetrieval via public IPFS gateways
  • Cryptographic proof of storage (Merkle proofs on-chain)
  • Standard IPFS Pinning Service API via W3Auth
  • Cross-chain pinning from Ethereum, Polygon, and Substrate chains

Features

pinningpublic-gatewaypinning-service-apisdk-jscustom-domain

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

Compare other IPFS providers

See the full vendor neutral comparison at /ipfs or jump directly to the other providers below.

Page maintained by Mudassir Khan · Verified 2026-06-02. Pricing and features change frequently — confirm on the provider's official pages before purchasing.