Head to head · Object storage · October 2026 research run

Amazon S3 vs Backblaze B2

Backblaze B2 scores 83.8 (A) on agent readiness against Amazon S3's 79.2 (A), and leads in 5 of 7 scored categories. Both do object storage.

Best file storage and sharing APIs for AI agents · All 105 storage comparisons

Which one, for what

Amazon S3 A

Best for Best when the rest of the stack is on AWS or the job needs versioning, Object Lock, replication or event notifications, and when an operator wants per-prefix, per-hour credentials for an agent.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Egress to the internet is billed per GB after 100 GB a month

Backblaze B2 A

Best for Cheap bulk storage that an agent writes and a CDN serves, and for operators who want an MCP server with real guardrails.

Ahead on

  • Reliability, 90 against 80
  • Payments & pricing, 60 against 45
  • Maintenance & community, 80 against 73

Also in its favour

  • Runs on your own machine
  • Open source

Watch for

EU upload failures on 30 October were reopened the same evening and still unresolved in the status feed on 31 October

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Backblaze B2 +15

Amazon S3 45

No x402, MPP or L402 (0). Per-GB and per-request prices are public without a login, though the Standard table on the pricing page renders by script and the figures come from AWS's public price feed, still the 15 October 2026 publication on 1 November, with the same US West (Oregon) rates (20). New accounts get up to $200 in Free Tier credits that apply to S3, and the Free Tier FAQ, re-read on 1 November, still says a payment method isn't required for most new customers and that in some cases AWS may request one to verify identity, so half (10). A person still signs up in a browser (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Backblaze B2 60

No x402, MPP or L402 (0). Per-TB storage and per-call prices public without a login (20). The first 10 GB are free and the sign-up page says no credit card is required (20). A person signs up in a browser. The Partner API can create accounts, but only for partners holding a master key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Reliability Backblaze B2 +10

Amazon S3 80

AWS Health Dashboard with per-service, per-Region history and RSS feeds (20). The dashboard's history file, re-read on 1 November, lists S3 in two open multi-service events, ME-CENTRAL-1 (UAE) since 1 March 2026 and ME-SOUTH-1 (Bahrain) since 2 March, both at service disruption. AWS says both Regions were damaged in the conflict in the Middle East, and on 15 September 2026, inside the 90-day window from 3 August, said it can't restore resources and data held only in the mec1-az2 Availability Zone or only in ME-SOUTH-1. No other S3 event falls in the 90 days to 1 November, the us-east-1 S3 feed is empty, and neither event has had an update since 15 September. One major event, read as the amazon-ses and amazon-polly re-checks of 6 October read the same two events (10). 3,500 writes and 5,500 reads a second per prefix, with no limit on prefixes, re-read on 1 November (15). 503 SlowDown is documented, the performance guide says to use aggressive timeouts and retries, the SDKs retry 503s on their own, and conditional writes make a retried PUT safe (15). SLA of 99.9 per cent a month for Standard, with 10, 25 and 100 per cent credits (last updated 28 November 2023, re-read on 1 November) (10). GA (10). 20 + 10 + 15 + 15 + 10 + 10 = 80.

Backblaze B2 90

Status page at status.backblaze.com (20). The page renders with JavaScript, but its RSS feed (status.backblaze.com/data/rss.xml) is readable. On 1 November it holds 21 items back to 3 August 2026. Three unplanned incidents fall since the 17 October check. On 27 October 'Elevated download/upload errors for a subset of customers in US-East' set the US East Region to Degraded at 15:59 UTC and back to Operational at 16:37. On 30 October US East download latency was opened at 04:41 and mitigated at 05:56, then reopened and marked mitigation applied at 16:48. 'EU Region High Upload Failures' was opened at 00:59 UTC on 30 October and called resolved at 06:30, then returned to investigating at 20:54 because 'some upload issues remain', with no later item by the feed's 31 October 17:15 date. Two items labelled scheduled maintenance describe higher download (30 September 23:49 to 1 October 02:00) and upload (1 October, posted window 06:09 to 18:09) failure rates for some EU Central customers. We read all of these as minor, partial failure rates for some customers in one region rather than a core API down, as the 6 and 17 October checks read 1 October (20). Rate limits with numbers. The rate-limits page (updated 22 January 2026) gives new accounts a default of 500 requests a second for uploads and downloads, with higher limits on request. Earlier checks missed it (15). Throttling answers 429 on the native API and 503 SlowDown on the S3 API, may carry Retry-After, and the page asks for exponential backoff. The error page advises backoff on 503, a new upload URL after a 401 on upload and b2_authorize_account again on an expired token, and the MCP server retries 408, 429 and 5xx itself (15). SLA of 99.9 per cent monthly uptime for all B2 customers, with 5 or 10 per cent credits, page dated 27 March 2019 (10). GA (10).

Maintenance & community Backblaze B2 +7

Amazon S3 73

The S3 model in aws/api-models-aws last changed on 30 September 2026, adding an IntelligentTieringReferenceDate enum value. The repository had commits to 30 October, none touching models/s3, so the last change is 32 days old on 1 November, past the 30-day line (20, down from 30, cause time). The S3 Files model changed on 20 October (a MISCONFIGURED file-system state) and What's New of 21 October extended server access log delivery to CloudWatch Logs to the GovCloud, European Sovereign Cloud and China Regions. Neither is read as a change to the S3 API, as the 17 October check read only models/s3. Model changes on 6 August, 8 September (Object Lock event holds), 11 September and 30 September, four in the 90 days from 3 August, and a user guide history entry on 30 September (20). Closed service with dated model changes, a What's New feed and AWS re:Post. Direct support is a paid plan (10). Official SDKs in every major language, generated from the same models (15). We didn't check SDK CI this run (8). 20 + 20 + 10 + 15 + 8 = 73.

Backblaze B2 80

MCP server v0.2.2 on 29 September 2026, still the newest tag and npm release on 1 November, 33 days old, and the first STS production wave on 30 September, with nothing newer in the API docs (20, down from 30 as the 30-day window passed). Six MCP releases since 18 August (0.1.0 to 0.2.2), all inside the 90 days from 3 August (20). The MCP repo merges pull requests often (numbered past #530, last commit 30 October, with security advisory fixes on 27 October and an unreleased fix for empty s3_put_object content), but we couldn't see issue replies from git, and the B2 release notes page stopped in 2016 (15). In the official MCP registry as io.github.backblaze-labs/b2-mcp at 0.2.2, marked latest on 1 November, and current official SDKs (15). CI for tests, contract checks, CodeQL and mutation testing, and open Dependabot and transitive advisories patched on main on 27 October (10).

Score by category

CategoryWeightAmazon S3Backblaze B2Edge
Reliability16%8090Backblaze B2 +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9289Amazon S3 +3
Agent ergonomics13%8385Backblaze B2 +2
Security & auth14%8890Backblaze B2 +2
Payments & pricing10%4560Backblaze B2 +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7380Backblaze B2 +7
Transparency & trust7%8483Amazon S3 +1
Negative events≤1500
TotalA 79.2/100A 83.8/100

Facts side by side

FactAmazon S3Backblaze B2
KindHTTP APIHTTP API
VendorAmazon Web ServicesBackblaze
Hosted endpointhttps://s3.us-east-1.amazonaws.comhttps://s3.us-west-004.backblazeb2.com
TransportsHTTPHTTP, stdio, Streamable HTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceApache-2.0MIT
Tools exposednone40
Read-only variant documentednoyes
llms.txtnoyes
MCP registrynot listedio.github.backblaze-labs/b2-mcp
Last release2026-09-302026-09-29
Terms last updated2026-10-012026-04-16
Privacy policy last updated2026-05-182026-04-30
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity3.7k stars, 44.8M npm/wk, 578.4M PyPI/wk1 stars, 150 npm/wk, 112k PyPI/wk
Agent reviews3.4/5 (8)3.8/5 (8)

The panel on both

3 of the 8 reviewers who reviewed both rate Backblaze B2 higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Amazon S3

STS session credentials with session policies, so an agent can hold one prefix for an hour. Egress to the internet is billed per GB after 100 GB a month.

Backblaze B2

$6.95 a TB-month, first 10 GB free, Class A, B and C API calls free, no card at signup, and a published default of 500 requests a second. The status feed shows EU upload failures on 1 and 30 October, the second reopened and unresolved on 31 October.

Before you call either

Amazon S3

  1. Hold STS session credentials scoped by a session policy, never a long-lived IAM user key
  2. Sign presigned URLs with credentials that outlive the URL; a URL signed with a one-hour session token dies with the token
  3. Send If-None-Match with * on PutObject so a retry can't overwrite a file another call wrote
  4. Track the Free plan's end date on a new account; when the plan expires AWS suspends the account and access to the stored objects
  5. On 503 SlowDown back off and spread keys over more prefixes, since each prefix gets 3,500 writes a second

Backblaze B2

  1. Take the region from the key's S3 endpoint (the second label of s3.<region>.backblazeb2.com) and pass it as the SDK region
  2. Mint a per-task application key for one bucket and a name prefix, with an expiry, rather than holding the master key
  3. Move bytes with s3_get_presigned_url so file contents never pass through the model
  4. Expect 429 on the native API and 503 SlowDown on S3 past the default 500 requests a second; honour Retry-After when present, else back off exponentially
  5. On 401 expired_auth_token call b2_authorize_account again; after a failed upload fetch a new upload URL
  6. Expect fewer than 40 tools with a non-master or read-only key; that's the server trimming tools to the key
  7. Avoid starting large transfers during Backblaze's Thursday maintenance window, 11:30 to 13:30 Pacific

Questions

Which is better for AI agents, Amazon S3 or Backblaze B2?

Backblaze B2 scores 83.8 (A) on agent readiness against Amazon S3's 79.2 (A), and leads in 5 of 7 scored categories.

Do Amazon S3 and Backblaze B2 need an API key?

Both need an API key.

Can an agent call Amazon S3 and Backblaze B2 without installing anything?

Yes. Amazon S3 has a hosted endpoint at https://s3.us-east-1.amazonaws.com and Backblaze B2 at https://s3.us-west-004.backblazeb2.com.

Are Amazon S3 and Backblaze B2 open source?

No open-source release is listed for Amazon S3. Backblaze B2 is open source (MIT).

Other comparisons with Amazon S3 or Backblaze B2

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.