---
title: Storj
slug: storj
url: "https://toolweight.com/options/storj"
homepage: "https://www.storj.io/"
categories: s3-compatible-storage
last_verified: 2026-07-23
license: CC-BY-4.0
---

# Storj

> Decentralised erasure-coded storage: USD 4/TB stored, USD 7/TB egress, no regions.

Storj splits every object into erasure-coded pieces spread across thousands of independent operator nodes worldwide, then reassembles them on read. Durability comes from that spread rather than from replicas in a datacentre, and there are no regions to choose. It is priced attractively and its access-grant model is the most granular here, but reassembly means first-byte latency is structurally higher than a conventional store.

## Identity

|  |  |
| --- | --- |
| Name | Storj |
| Company | Storj Labs |
| One-liner | Decentralised erasure-coded storage: USD 4/TB stored, USD 7/TB egress, no regions. |
| Site | https://www.storj.io/ |
| Docs | https://docs.storj.io/ |
| Founded | 2014 |
| Brand | https://toolweight.com/vendors/Storj |
| Compared in | 1 |

## Where it is compared

### [S3-compatible storage](https://toolweight.com/compare/s3-compatible-storage)
Ranked **#3 of 12** on default weights.
| Field | Value | Confidence | Verified | Source | Note |
| --- | --- | --- | --- | --- | --- |
| True cost /mo (USD) | $39 /mo | Inferred | 2026-07-23 | https://www.storj.io/pricing | Storage 1 TB x $4 = $4.00. Egress 5 TB x $7 = $35.00. No per-request charges. Total $39.00. Excludes Storj's per-segment fee (about $0.0000088 per segment per month), because it scales with object count and shape rather than with anything this scenario fixes, but do not read that as negligible: the scenario's 1 M writes, if they are roughly 1 MB objects, are about 1 M segments, which is around $8.80 a month, a fifth of the total again. |
| True cost /mo (AUD) | A$59.28 /mo | Inferred | 2026-07-23 | - | $39.00 x 1.52. |
| True cost from Sydney (AUD) | A$59.28 /mo | Inferred | 2026-07-23 | - | Unchanged from the headline figure: Storj has one global price and no regions, so there is no Australian tariff to apply. Read it alongside the 150 ms first-byte figure, the price is the same from Sydney, the latency is not. |
| Storage $/TB/mo | $4 /TB/mo | Vendor-claimed | 2026-07-23 | https://www.storj.io/pricing | Joint-cheapest storage rate on this page, alongside iDrive e2. |
| Egress $/TB | $7 /TB | Vendor-claimed | 2026-07-23 | https://www.storj.io/pricing | $0.007/GB, an order of magnitude under AWS but not free, so Storj loses to R2 on read-heavy work despite the cheaper storage. |
| Egress cap (x stored) | - | Unknown | 2026-07-23 | https://www.storj.io/pricing | Not applicable: egress is metered at $0.007/GB from the first byte, so there is no free-egress ceiling to exceed. |
| Class A $/M ops | $0 /M ops | Vendor-claimed | 2026-07-23 | https://www.storj.io/pricing | No request metering. Storj bills a per-segment fee instead, which scales with object count and size rather than with API calls. |
| Class B $/M ops | $0 /M ops | Vendor-claimed | 2026-07-23 | https://www.storj.io/pricing | - |
| Min retention | 0 ms | Inferred | - | - | - |
| Min billed object | 0 B | Inferred | - | - | No size floor, but the per-segment fee means very small objects carry disproportionate overhead. |
| S3 API coverage | 80 % | Inferred | - | - | Delivered through an S3 gateway rather than natively. CRUD, multipart, presigning, versioning and object lock work; the more exotic bucket-level APIs generally do not. |
| Presigned URLs | ● | Inferred | - | - | - |
| Multipart upload | ● | Inferred | - | - | - |
| Versioning | ● | Vendor-claimed | 2026-07-23 | https://storj.dev/dcs/api/s3/object-versioning | - |
| Lifecycle rules | - | Unknown | - | - | We could not confirm the state of lifecycle configuration support through the S3 gateway. |
| Event notifications | ○ | Inferred | - | - | - |
| CDN integration | partner | Inferred | - | - | Linksharing serves objects publicly and there are documented CDN partnerships, but no bundled edge cache. |
| Max object size | 5 TB | Inferred | - | - | - |
| IAM granularity | 4 | Inferred | - | - | Access grants are macaroon-derived: scope by bucket, prefix, permission and expiry, and delegate further without contacting the server. Genuinely more granular than most vendors' key models, just shaped differently from IAM. |
| Sydney region | ◐ | Inferred | - | - | Storj has no regions, objects are erasure-coded across globally distributed operator nodes. Geographic placement constraints exist for compliance use cases, but that is not a Sydney region in the ordinary sense. |
| TTFB from Sydney | 150 ms | Inferred | - | - | Reads require fetching enough erasure shards from enough independent nodes to reconstruct the object, so first-byte latency is structurally higher and more variable than a conventional store. Throughput on large objects is good; small-object latency is not. |
| Durability (nines) | 11  nines | Inferred | 2026-07-23 | - | - |
| Uptime SLA | 99.95 % | Inferred | 2026-07-23 | - | - |
| Object lock / WORM | ● | Vendor-claimed | 2026-07-23 | https://storj.dev/dcs/api/s3/object-lock | - |
| Replication model | erasure-coded | Vendor-claimed | 2026-07-23 | https://storj.dev/learn/concepts/data-structure | Each object is split into shards spread across thousands of independent nodes; losing whole facilities is a design assumption rather than an incident. |
| Official MCP server | ○ | Inferred | - | - | - |
| GA year | 2,020 | Inferred | - | - | - |
| Positioning | Decentralised storage sold on price and on surviving whole-facility failure. | Inferred | - | - | - |

**Verdict.** The cheapest storage on the page and a genuinely different durability model, undercut by first-byte latency the architecture cannot fix. Strong for large-object distribution and backups; poor for a hot path serving many small files.

## Alternatives

- [AWS S3](https://toolweight.com/options/aws-s3), The API everything else copies, and by far the most expensive egress in this roster.
- [Backblaze B2](https://toolweight.com/options/backblaze-b2), Cheap US and EU object storage with free egress up to three times stored volume.
- [Bunny Storage](https://toolweight.com/options/bunny-storage), Edge storage built as a CDN origin, with its own API rather than a faithful S3 one.
- [Cloudflare R2](https://toolweight.com/options/cloudflare-r2), S3-compatible object storage with zero egress fees, on Cloudflare's network.
- [DigitalOcean Spaces](https://toolweight.com/options/digitalocean-spaces), Bundled object storage plus free CDN, priced as a flat base fee with overages.
- [Hetzner Object Storage](https://toolweight.com/options/hetzner-object-storage), The cheapest credible S3 endpoint in Europe, with a deliberately thin feature set.
- [iDrive e2](https://toolweight.com/options/idrive-e2), USD 4/TB S3-compatible storage with zero-egress marketing and a fair-use cap.
- [MinIO](https://toolweight.com/options/minio), The self-hosted S3 reference implementation, your hardware, your bandwidth, your SLA.
- [Scaleway Object Storage](https://toolweight.com/options/scaleway-object-storage), European-sovereign S3 storage with multi-AZ classes and a real IAM system.
- [Tigris](https://toolweight.com/options/tigris), Globally distributed S3-compatible storage that caches objects near readers.
- [Wasabi](https://toolweight.com/options/wasabi), Flat-rate hot storage with no egress or API fees, bounded by a fair-use cap.

## Licence and attribution

Data from toolweight (https://toolweight.com), licensed CC-BY-4.0.

- Licence: [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/)
- Canonical HTML: https://toolweight.com/options/storj
- Machine-readable: https://toolweight.com/options/storj.md · https://toolweight.com/api/v1 · https://toolweight.com/mcp
- toolweight takes no affiliate revenue and sells no placements. Corrections: https://toolweight.com/suggest