What is Storj?
Storj is the decentralized object-storage network where every uploaded file is split into 80 encrypted erasure-coded pieces, distributed across thousands of independent storage nodes worldwide, and reassembled on download — only 29 of the 80 pieces are needed to reconstruct a file, providing built-in redundancy without traditional cloud regions or single points of failure. Files are end-to-end encrypted client-side with zero-knowledge architecture: Storj's network never holds your encryption keys, and even compromised storage nodes hold only encrypted shards. Storage is $0.004/GB/month ($4/TB) — among the cheapest in the industry — with 1× free egress per month equal to your stored volume on Regional, Archive, and Global tiers. The decentralized backbone, S3-compatible gateway, and developer-friendly pricing have made Storj a default destination for ML training data archives, CDN origins, and regulated-industry backups that can't trust a single cloud provider.
Storj's S3 gateway lets any tool that speaks S3 — including CloudsLinker — write to and read from the decentralized network without users managing the underlying erasure-coding mechanics. The gateway endpoint is gateway.storjshare.io, the auth is standard Access Key + Secret + Endpoint, and Storj's recommended multipart part size is 64 MB (vs the typical 8–10 MB) for optimal throughput across the distributed nodes. With 10,000 parts max per object, single objects can reach hundreds of GB without issues. CloudsLinker connects via the S3 gateway path, making Storj a drop-in destination for any cloud-to-cloud migration — particularly attractive when the source workload paid steep AWS egress fees or needs jurisdictionally-distributed redundancy that traditional clouds can't offer.
Key features of Storj
Why connect Storj to CloudsLinker
CloudsLinker connects to Storj DCS via the S3-compatible gateway with Access Key ID + Secret Access Key + Endpoint gateway.storjshare.io. Once connected, every transfer runs server-to-server using S3 multipart upload with Storj's recommended 64 MB chunk size. The gateway transparently handles client-side encryption and erasure-coding distribution to the storage node network — CloudsLinker just sees a standard S3 API. Use as source for migrating data off Storj, as destination for writing into the decentralized network, or for cross-cloud DR replicas where Storj's distributed model adds independence from any single cloud provider.
What you can do with Storj on CloudsLinker
S3-gateway server-to-server copies
Migrate from AWS S3, Wasabi, B2, or R2 into Storj's decentralized network at full multipart speed via the S3-compatible gateway.
Runs on our servers
Storj transfers execute on CloudsLinker's infrastructure — your home or office bandwidth is irrelevant to job throughput.
Scheduled & incremental sync
Hourly / daily / weekly schedules with delta mode — only changed objects are written to the Storj network on each run.
Filter by prefix, size, modified date
Migrate only specific bucket prefixes, skip files > 100 GB, or sync only this week's writes. Filters layer for surgical control.
Common Storj transfer scenarios
Cross-cloud DR independent of any single provider
S3-to-S3 replication keeps you locked inside AWS; a region-wide AWS outage or account compromise hits both copies. Schedule a CloudsLinker incremental from your primary S3 / Wasabi / B2 bucket to Storj — files land distributed across thousands of independent nodes worldwide, completely outside the source provider's failure domain. At $4/TB plus 1× free egress, a 10 TB DR copy costs ~$40/month with built-in geo-redundancy.
Privacy-first ML training dataset distribution
Open-source ML projects publishing model weights or training datasets often pay AWS thousands a month in egress. Migrate to Storj via CloudsLinker — storage at $4/TB, 1× free egress equal to stored volume, and end-to-end encryption that protects pre-release datasets even from Storj operators. Especially attractive for projects with 5–50 TB of public artifacts.
Regulated-industry backup with jurisdictional independence
Healthcare, legal, and financial customers sometimes require backups outside any single nation's jurisdiction. Storj's distributed network places erasure-coded shards across nodes in dozens of countries — no single subpoena can compel access to a complete file. CloudsLinker schedules nightly incrementals from your primary cloud (often S3 or Azure Blob) into Storj for true cross-jurisdictional redundancy.
Migrate from AWS S3 → Storj to escape egress fees
If your S3 bucket serves > $200/month in public egress, migrating to Storj cuts egress cost dramatically. The initial S3 → Storj seed pays AWS egress on the source side, but ongoing serving from Storj sits within the 1× free egress allowance for most workloads. CloudsLinker handles the multipart-parallel seed at typical 1–3 TB/day per connection.
Cold archive at $4/TB on Active Archive tier
Storj's Active Archive tier targets workloads that store more than they egress — at $4/TB storage, $0.02/GB egress, and no inactivity fees, it competes with AWS S3 Glacier Deep Archive on raw cost while providing instant retrieval (no thaw delay). CloudsLinker filters by modification date to migrate cold prefixes from S3 / GCS into Storj Active Archive.
How to connect Storj to CloudsLinker
Storj DCS uses S3-compatible authentication through Storj’s hosted gateway: Access Key + Secret + universal endpoint gateway.storjshare.io.
Before you start
Generate Storj S3 credentials from the Storj satellite console (not the same as your account login):
- Sign in to the Storj satellite at https://storj.io/login (or your enterprise satellite URL).
- Go to your project and click Access → S3 Credentials.
- Click Create S3 Credentials (or New Access Grant depending on your console version).
- Configure:
- Name — e.g.
cloudslinker-migrate - Permissions — Read for source, Read+Write+Delete for destination
- Buckets — restrict to specific buckets where possible
- Encryption passphrase — Storj generates an encryption key from this; save it securely — without it, encrypted files become unrecoverable
- Name — e.g.
- Storj displays the Access Key, Secret Key, and Endpoint once. Copy all three.
Connection steps
- In CloudsLinker, click Add Cloud → choose Storj.
- Enter a display name (e.g. “Storj — production-archive”).
- Paste the Access Key and Secret Key from step 5 above.
- Enter the Endpoint URL: gateway.storjshare.io (universal — Storj uses a single global gateway endpoint, not per-region).
- Click Confirm — CloudsLinker validates with
ListBucketsand shows the connection ready.
Multipart tuning
For best performance with Storj’s distributed network, multipart uploads use 64 MB part size by default in CloudsLinker (larger than typical S3 8–10 MB). This optimizes throughput across the erasure-coded node network.
Revoke access
To revoke CloudsLinker’s S3 credentials later: Storj satellite console → Access → S3 Credentials → find the entry → Delete. The credential becomes immediately invalid; reconnect by generating new credentials.
Storj upload & download limits you should know
Storj’s pricing model differs significantly from centralized S3-compatible providers — focus on the 1× free egress rule and the new tiered structure that replaced legacy pricing in November 2025:
- Maximum object size: 5 TB via multipart upload (using 5 GB max parts × 1,000 parts) — or up to ~640 GB with the recommended 64 MB part size.
- Maximum parts per multipart upload: 10,000.
- Recommended part size: 64 MB (larger than AWS S3’s typical 5 MB minimum, optimized for the distributed network).
- Storage pricing: $0.004/GB/month ($4/TB) on standard tiers — among the cheapest in the industry.
- Egress: 1× stored volume free per month on Regional, Archive, and Global tiers. Beyond that, $0.005–$0.02/GB depending on tier.
- Active Archive tier: $4/TB storage, but excludes free egress — outbound billed at $0.02/GB.
- No API request fees on standard tiers.
- Pricing tier transition: New projects (after Nov 1, 2025) use Global Collaboration / Regional Workflows / Active Archive tiers. Legacy projects continue on prior pricing through October 31, 2026.
- Encryption: End-to-end client-side; zero-knowledge — Storj cannot read your data.
- Erasure coding: Each file split into 80 pieces, 29 needed to reconstruct — distributed across thousands of independent storage node operators globally.
- API rate limits: Storj’s gateway throttles aggressive patterns; CloudsLinker handles back-off.
- Bucket / object count: practically unlimited.
Sources: Storj: Pricing, Storj Docs: S3 Compatibility, Storj Docs: Multipart Upload, Storj Docs: Tiered Pricing.
Storj + CloudsLinker — Frequently Asked Questions
Is Storj actually decentralized, or is it a centralized service that calls itself decentralized?
What's the maximum object size I can transfer to Storj?
What does '1× free egress' actually mean?
Are my files encrypted by Storj or by me?
How does the gateway handle multipart uploads?
Are my Storj S3 keys safe with CloudsLinker?
What's changing with the new tiered pricing in November 2025?
Can I use Storj for high-traffic CDN-style serving?
How does Storj compare to Wasabi, B2, and IDrive e2?
Is this an official Storj partnership?
Storj transfer guides
Step-by-step walkthroughs for moving data to and from Storj.
Conclusion
Storj's decentralized network turns the standard cloud-storage threat model upside down — instead of trusting one provider's datacenters, you trust math (erasure coding) and cryptography (zero-knowledge encryption). CloudsLinker treats Storj as a first-class S3-compatible target via the gateway, with multipart-tuned chunk sizes and incremental sync. Connect with Access Key + gateway.storjshare.io endpoint and run your first decentralized migration in minutes.
Online storage services supported by CloudsLinker
Transfer data between over 48 cloud services with CloudsLinker
Didn't find your cloud service? Contact: [email protected]