Bunny Storage

Bunny Storage — Edge storage built as a CDN origin, with its own API rather than a faithful S3 one. Bunny Storage exists to feed bunny.net's CDN, and it is very good at that: geo-replication across storage regions including Sydney, single-digit-millisecond edge delivery, and USD 0.01 per gigabyte for both storage and European or North American transfer. It is in this roster because people evaluate it against S3 providers, but its native interface is proprietary and S3 compatibility has never been the design goal. Built by bunny.net. Founded 2014.

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.

• CDN integration — free-bundled, tied for best across 4 of 12 tools.
• TTFB from Sydney — 20 ms, the best figure of the 10 here.
• Uptime SLA — 99.99 %, the best figure of the 9 here.
• Replication model — multi-region, tied for best across 2 of 12 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.

• S3 API coverage — 30 %, the weakest of the 12 here. AWS S3 records 100 %.
• Versioning — No. Backblaze B2 records Yes.
• Object lock / WORM — No. Backblaze B2 records Yes.
• Lifecycle rules — No. Cloudflare R2 records Yes.

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. 25 of 28 tracked fields carry a value for Bunny Storage, and 7 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. Bunny Storage is ahead on Egress $/TB ($10 /TB against $90 /TB) and True cost /mo (USD) ($60 /mo against $472.6 /mo). AWS S3 takes S3 API coverage (100 % against 30 %) and Versioning (Yes against No). That pattern repeats across the rest of the roster — see Bunny Storage alternatives for the other rivals, each compared the same way.

Company

bunny.net

Founded

2014

Fields we track

25 of 28

Last verified

2026-07-23

Included because people shortlist it against S3 providers, but it is a CDN origin with storage attached rather than an object store with a CDN attached. Superb Sydney delivery; do not expect S3 semantics, and read the regional egress table before modelling the cost.

S3 API coverage

30 %12th of 12

Inferred

True cost /mo (USD)

$60 /mo6th of 9

Inferredverified 2026-07-23source

Egress $/TB

$10 /TB7th of 11

Vendor-claimedverified 2026-07-23source

Versioning

○No9th of 11

Inferred

CDN integration

free-bundled1st of 12

Inferredverified 2026-07-23

Object lock / WORM

○No9th of 11

Inferred

TTFB from Sydney

20 ms1st of 10

Inferred

Lifecycle rules

○No11th of 11

Inferred

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

• Static sites, images and video served to a global audience through Bunny's CDN.
• Australian delivery where edge latency matters more than API compatibility.
• Replacing a CDN plus origin bucket with a single bill.
• CDN integration is your binding constraint. Bunny Storage records free-bundled, the best figure in the S3-compatible storage roster. We define that field as how you get cached edge delivery in front of the bucket.
• TTFB from Sydney is your binding constraint. Bunny Storage records 20 ms, the best figure in the S3-compatible storage roster. We define that field as typical time to first byte for an uncached GET of a small object from a client in Sydney, using the provider's nearest available location.
• Uptime SLA is your binding constraint. Bunny Storage records 99.99 %, the best figure in the S3-compatible storage roster.
• Replication model is your binding constraint. Bunny Storage records multi-region, the best figure in the S3-compatible storage roster.

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

• S3 API coverage. Bunny Storage records 30 %, the weakest of the 12 tools in the S3-compatible storage roster. AWS S3 records 100 % on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Versioning. Bunny Storage records No on the S3-compatible storage table. Backblaze B2 records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Object lock / WORM. Bunny Storage records No on the S3-compatible storage table. Backblaze B2 records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Lifecycle rules. Bunny Storage records No on the S3-compatible storage table. Cloudflare R2 records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• IAM granularity. Bunny Storage records 2, 11th of 12 in the S3-compatible storage roster. MinIO records 5 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.

What we don't know. 3 of the 28 fields we track for Bunny Storage are still blank: Egress cap (x stored), Max object size and Durability (nines). 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.