Storj backups

Decentralized storage exposed through a global S3 gateway. It is S3-compatible, which means blitcp supports it out of the box: pick the storj preset in creds add, paste your keys, and every transfer gets blitcp's usual treatment — content-hash deduplication before upload, verified writes after, and incremental re-runs that skip unchanged files.

Endpoint

https://gateway.storjshare.io
One global gateway — the preset fills it automatically. Region: Not used.

Where the keys come from

Storj console → Access → Create S3 Credentials (generated from an access grant).

Set it up once

$ blitcp creds add mystorj
  Type [s3/azure/gcs/ssh/smb — or a preset: r2/b2/wasabi/…]: storj
  Storj — S3-compatible. Keys: …
  Endpoint: https://gateway.storjshare.io
  Access key ID: ********
  Secret access key: ********
  Default bucket (blank = none): backups

Then copy

blitcp ~/photos mystorj:backups/photos          # upload, dedup + verify on
blitcp mystorj:backups/photos ~/restore     # download

Re-running the same upload only transfers new or changed files. Duplicate content inside the tree is uploaded once. Credentials live in blitcp's AES-256-GCM encrypted credentials file — see the cloud storage guide for the full creds manager.

Notes

Files are erasure-coded across the network behind the gateway; large-object throughput is excellent, tiny-object latency higher than centralized stores.

Also supported: Cloudflare R2 · Backblaze B2 · Wasabi · DigitalOcean Spaces · Scaleway Object Storage · Hetzner Object Storage · IDrive e2 · Oracle OCI Object Storage · iCloud Drive