iDrive e2

iDrive e2 is USD 4/TB S3-compatible storage with zero-egress marketing and a fair-use cap. We compare it in S3-compatible storage. It is top of its roster on Egress $/TB ($0 /TB). The trade-off is being 12th of 12 on CDN integration (none).

What is iDrive e2?

iDrive e2 — USD 4/TB S3-compatible storage with zero-egress marketing and a fair-use cap. e2 undercuts almost everyone on storage at USD 0.004 per gigabyte per month and advertises no egress fees, subject to a fair-use multiple of what you store. It supports object lock and versioning, which is more than the price suggests. The documentation is thinner than its competitors' and the egress overage terms are the least clearly published in this comparison. Built by iDrive. Founded 1995.

We track it in 1 comparison — S3-compatible storage — so every claim below is a cell in a table you can open and check rather than an impression. Across those rosters it sits against 11 other tools, and what follows is where it visibly separates from them.

Where it wins.

  • Egress $/TB — $0 /TB, tied for best across 4 of 11 tools.
  • Storage $/TB/mo — $4 /TB/mo, tied for best across 2 of 11 tools.

Each of those is ranked against the whole roster on its category page, not against a hand-picked subset, so a first place here means first of everything we list.

Where it gives ground.

  • CDN integration — none, the weakest of the 12 here. Cloudflare R2 records free-bundled.
  • Replication model — single-az, 8th of 12. Tigris records multi-region.

None of these disqualify it on their own. They are the fields to check against your own requirements before you commit, because they are the ones where a competitor genuinely does better.

Provenance. 22 of 28 tracked fields carry a value for iDrive e2, and 5 of those cite a document you can open. Last verified 2026-07-23. Every figure keeps its own provenance — measured by us, claimed by the vendor, inferred, or community-reported — and we would rather print a dash than a guess.

Its nearest neighbour in our data is AWS S3. iDrive e2 is ahead on Egress $/TB ($0 /TB against $90 /TB) and Storage $/TB/mo ($4 /TB/mo against $23 /TB/mo). AWS S3 takes Event notifications (Yes against No) and Official MCP server (Yes against No). That pattern repeats across the rest of the roster — see iDrive e2 alternatives for the other rivals, each compared the same way.

At a glance
Company
iDrive
Founded
1995
Fields we track
22 of 28
Last verified
2026-07-23

iDrive e2 in S3-compatible storage

Ranked against 12 tools across 28 sourced fields. Open the full S3-compatible storage table.

The cheapest storage rate here alongside Storj, with object lock included, and the least legible egress terms in the roster — legible enough that we will not put a number in the cost column for it. Fine as a backup target, where you store far more than you read; do not build a public asset pipeline on a fair-use cap you cannot find written down.

Where it lands in this roster
Egress $/TB
$0 /TB1st of 11
Vendor-claimedverified 2026-07-23source
CDN integration
none12th of 12
Inferred
Storage $/TB/mo
$4 /TB/mo1st of 11
Vendor-claimedverified 2026-07-23source
S3 API coverage
80 %8th of 12
Inferred
Min retention
0 ms1st of 12
Inferred
Versioning
Yes1st of 11
Inferredverified 2026-07-23
Durability (nines)
11 nines1st of 8
Inferred
Object lock / WORM
Yes1st of 11
Vendor-claimedverified 2026-07-23source

When to use iDrive e2

iDrive e2 is the right call in these situations, each one drawn from a field we actually record:

  • Backup and MSP workloads where storage volume dominates and reads are rare.
  • Object-lock immutability at the lowest price on this page.
  • Teams comfortable verifying terms directly with a vendor before committing.
  • Egress $/TB is your binding constraint. iDrive e2 records $0 /TB, the best figure in the S3-compatible storage roster. We define that field as marginal list price to transfer one terabyte (1,000 GB) out to the public internet, beyond any free allowance, excluding intra-provider and CDN origin-fetch transfer.
  • Storage $/TB/mo is your binding constraint. iDrive e2 records $4 /TB/mo, the best figure in the S3-compatible storage roster. We define that field as marginal list price to store one terabyte (1,000 GB) in the provider's standard or hot class for one month, at pay-as-you-go rates with no commitment.

When not to use iDrive e2

Reach for something else when any of the following is a requirement rather than a nice-to-have:

  • CDN integration. iDrive e2 records none, the weakest of the 12 tools in the S3-compatible storage roster. Cloudflare R2 records free-bundled on the same field. If that is a hard requirement rather than a preference, start elsewhere.
  • Replication model. iDrive e2 records single-az, 8th of 12 in the S3-compatible storage roster. Tigris records multi-region on the same field. If that is a hard requirement rather than a preference, start elsewhere.

We publish this block because a comparison that only lists what a tool is good at is marketing. Every figure above sits on the same page as its source, and the field definitions are on the category tables if you want to check how we measured them.

Tools compared alongside iDrive e2

Everything below shares at least one comparison category with iDrive e2, ordered by how much overlap there is. For the reasoning on each — which fields it wins, which it loses — see iDrive e2 alternatives.

Recent iDrive e2 changes

We have not logged a dated change for iDrive e2 yet. The timeline fills in as pricing moves, features ship and things get deprecated.

Sources and gaps

What we don't know. 6 of the 28 fields we track for iDrive e2 are still blank: True cost /mo (USD), True cost /mo (AUD), True cost from Sydney (AUD), Egress cap (x stored), Sydney region and TTFB from Sydney. Those render as dashes rather than as zeroes or assumptions, because an empty cell and a bad cell are not the same thing and only one of them is honest. If you know any of these figures and can point at a document, tell us.

Every figure on this page traces back to a document you can open. Where a vendor claims a number we could not reproduce, the cell says so.