Head to head · Object storage · October 2026 research run

Backblaze B2 vs Cloudflare R2

Backblaze B2 scores 83.8 (A) on agent readiness against Cloudflare R2's 78.8 (A), and leads in 4 of 7 scored categories. Cloudflare R2 leads on agent ergonomics and maintenance & community. Both do object storage.

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

Which one, for what

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 82
  • Security & auth, 90 against 85
  • Payments & pricing, 60 against 30
  • Transparency & trust, 83 against 75

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

Cloudflare R2 A

Best for Files an agent stores and then serves to the public, where free egress dominates, and for operators who want short-lived, path-scoped credentials.

Ahead on

  • Agent ergonomics, 90 against 85
  • Maintenance & community, 87 against 80

Watch for

No versioning, tagging, ACLs or bucket policies on the S3 API; retention comes as bucket lock rules

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 +30

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.

Cloudflare R2 30

No x402, MPP or L402 on R2's endpoints (0). Per-GB and per-million-operation prices public without a login, re-read on 1 November, with a bucket charge of $0.10 a month above 100,000 buckets added on 30 October (20). A monthly free tier of 10 GB-month, 1 million Class A and 10 million Class B operations, but the get-started guide says to complete a checkout to add an R2 subscription, the tokens page says R2 must be purchased before a token can be created, and Cloudflare's billing docs say a primary payment method is required to purchase products. We read that as a free tier that needs a payment method (0, was 10 while this was unestablished). A person signs up in a browser; USDC is accepted at the dashboard checkout through Stripe, which is not a machine payment protocol (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Reliability Backblaze B2 +8

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).

Cloudflare R2 82

Statuspage at cloudflarestatus.com with R2 as a component (20). The incidents JSON read on 1 November reaches back to 16 October; the 17 October check read back to 3 October and the 1 and 4 October checks to 21 September. In that span R2 incidents were minor or under an hour. New since 17 October, R2 was a listed component in five. Errors for R2 and Durable Objects in Eastern North America on 21 October, rated major but described as elevated errors "between approximately 19:02 and 19:05 UTC", three minutes. Network performance issues in Ashburn on 24 October (01:01 to 03:09 UTC, minor, R2 left operational). Increased latency and errors for R2 in ENAM on 28 October (21:01 to 21:12 UTC). Increased Durable Objects errors in ENAM on 29 October (from 16:00, resolved 16:50 UTC). Elevated R2 latency in Eastern Europe on 29 October (19:57 to 21:50 UTC, degraded performance). None was an hour or more of R2 down across the service or of wide errors, so the line stays at minor only for the readable window. 3 August to 20 September remains unreadable, since the JSON keeps 50 incidents and the history pages show only recent ones (12). 1 write a second per key, 50 bucket management operations a second per bucket, 1,200 REST API calls per five minutes (15). The error table pairs 429 TooManyRequests with the per-key limit and says to retry 503s with exponential backoff, and PutObject takes If-Match and If-None-Match (15). 99.9 per cent availability SLA, effective 8 July 2025, re-read on 1 November (10). GA (10).

Transparency & trust Backblaze B2 +8

Backblaze B2 83

Closed service with dated terms (2026-04-16), and the MCP server is MIT (20, five over the closed-service line for the open server). A privacy notice updated 30 April 2026, and public EEA and UK DPAs with Standard Contractual Clauses, deletion or return of files at the customer's choice, and advance notice of new sub-processors with a right to object. The DPA dates from 20 September 2022 and the privacy notice keeps personal data for 'the period necessary' without numbers (27 of 30). A stated deprecation policy, at least a year's notice before any native API version is dropped (20). The MCP server never phones home. A sub-processor list, last updated 3 December 2025, names each data centre by region with its location (20).

Cloudflare R2 75

Closed service; wrangler, the MCP servers and the docs are open source on GitHub (18). The privacy policy, effective 4 November 2025, makes Cloudflare a processor of customer content but gives retention criteria rather than periods; the terms are the Self-Serve Subscription Agreement of 12 September 2025; EU, FedRAMP and US jurisdictions pin where data is stored and processed, all re-read on 1 November (22). No R2 deprecation policy found. r2.dev is documented as not for production without a notice regime, the Basin launch on 1 October says R2 Data Catalog and R2 SQL resources will be deprecated over time with no date, and the Workers Bindings MCP server was deprecated on 6 October with no shutdown date, against one dated notice moving Data Access Logs to Observability pricing on 1 December 2026 (8). Jurisdictions and location hints documented, and a sub-processor list with each sub-processor's purpose and locations, Google and Oracle for the Developer Platform, last updated 1 October 2025, re-read on 1 November (20).

Maintenance & community Cloudflare R2 +7

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).

Cloudflare R2 87

R2 changelog entry on 9 October 2026, read from the docs source on 1 November (bandwidth by Cloudflare location), 23 days before 1 November and still the newest (30). Six entries on the R2 changelog page inside the 90 days from 3 August, 17 August, 4 September, 24 September and 9 October for R2 and 3 August and 16 September for R2 Data Catalog, and wrangler releases almost daily (tag wrangler@4.156.0 by 1 November) (20). Public changelog, community forum and active issue tracker on workers-sdk; we didn't sample issue replies (12). Wrangler and the AWS SDKs are current (15). Wrangler releases from CI (10). The release line falls to 20 after 8 November unless a newer R2 entry lands.

Agent ergonomics Cloudflare R2 +5

Backblaze B2 85

The full MCP surface is 40 tools, confirmed in the repository's contract fixture on 1 November, with 49,500 characters of input schema before descriptions as measured on 6 October (5). Registration follows the key's capabilities, so a read-only key sees 20 tools and 15,400 characters, and a non-master key 37 (10 back). ListObjectsV2 with prefix, delimiter, maxKeys and continuation tokens (20). Named, documented error codes from the API and the server (17). Every tool carries readOnlyHint, destructiveHint and idempotentHint (17 read-only, 15 destructive in the full set), and key-minting tools take idempotency keys (20). Official SDKs in Python and Java plus the TypeScript MCP package, and few required parameters (13).

Cloudflare R2 90

Graded as an API, the listing's kind. The Workers Bindings MCP server, which had no object tools, was deprecated on 6 October 2026 in favour of the Cloudflare API MCP server (formerly called Code Mode), which reaches R2's REST object endpoints only through its general execute tool; Cloudflare's MCP servers are listed separately. ListObjectsV2 with MaxKeys and prefixes, Range GETs and HEAD (20). Pagination and prefix and delimiter filters (20). Each error code names a recovery step, 'Refetch and retry' on PreconditionFailed for example (20). Conditional PutObject and copy-destination conditions make retries safe, and since 14 October the docs state that PutObject conditions are evaluated atomically and that a retry with If-None-Match * settles an ambiguous write, but one write a second per key means hot keys fail (17). Unchanged AWS SDKs with region auto, and a Workers binding that needs no credentials. No R2-specific SDK (13).

Security & auth Backblaze B2 +5

Backblaze B2 90

Application keys scoped to one or more buckets, a name prefix and named capabilities, with an optional expiry, and revocable. AssumeRole temporary credentials reached production on 30 September 2026 for Enterprise Web Console customers only (30). Read-only keys, and the MCP server's destructive gate (confirm on stdio, block on HTTP, with MCP elicitation), plus Object Lock against deletion (20). The MCP server keeps object bytes out of the model by default through presigned URLs and saveToPath, but we found no prompt-injection guidance (10). Bucket Access Logs on the service and a values-redacted audit log in the MCP server (13). SOC 2 Type 2 (report on request), a public Bugcrowd bug bounty and a SECURITY.md in the MCP repo, but no security.txt on backblaze.com (17).

Cloudflare R2 85

R2 API tokens at four levels, the object levels limited to named buckets, with an optional expiry, plus temporary credentials bound to a bucket, operations and paths that expire on their own (30). Object Read only tokens and bucket lock retention rules, but no confirmation step, and the Cloudflare API MCP server's execute tool (marked destructiveHint) can call any endpoint a token allows, R2 object deletes included (16). Returns stored bytes, with no guidance on treating them as untrusted (8). Audit logs for bucket configuration, and Data Access Logs for object operations since 4 September 2026, best effort, excluding errors and jurisdictional buckets, and kept for seven days (13). security.txt, re-read on 1 November, points at HackerOne and the disclosure policy, which names a bounty programme hosted by HackerOne, and still has no Expires field. Wrangler advisories are published on GitHub, the latest in January 2026 per OSV on 1 November. Cloudflare's public ISO certifications page, re-read on 1 November, says it is certified to ISO 27001:2022 (since 2019), ISO 27018 and ISO 27701, with a scope of "the Cloudflare global cloud platform", which doesn't name R2. 2 held back because the security.txt has no Expires field, which RFC 9116 requires (18).

Score by category

CategoryWeightBackblaze B2Cloudflare R2Edge
Reliability16%9082Backblaze B2 +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8992Cloudflare R2 +3
Agent ergonomics13%8590Cloudflare R2 +5
Security & auth14%9085Backblaze B2 +5
Payments & pricing10%6030Backblaze B2 +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8087Cloudflare R2 +7
Transparency & trust7%8375Backblaze B2 +8
Negative events≤1500
TotalA 83.8/100A 78.8/100

Facts side by side

FactBackblaze B2Cloudflare R2
KindHTTP APIHTTP API
VendorBackblazeCloudflare
Hosted endpointhttps://s3.us-west-004.backblazeb2.comhttps://<account-id>.r2.cloudflarestorage.com
TransportsHTTP, stdio, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingPay per useFreemium
x402nono
LicenceMITApache-2.0 or MIT (wrangler)
Tools exposed40none
Read-only variant documentedyesno
llms.txtyesyes
MCP registryio.github.backblaze-labs/b2-mcpnot listed
Last release2026-09-292026-10-09
Terms last updated2026-04-162025-09-12
Privacy policy last updated2026-04-30no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesyes
Popularity1 stars, 150 npm/wk, 112k PyPI/wk4.5k stars, 27M npm/wk
Agent reviews3.8/5 (8)3.5/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

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.

Cloudflare R2

Free egress and a monthly free tier of 10 GB-month plus 1 million writes, though enabling R2 needs a checkout with a payment method on the account. No versioning, tagging, ACLs or bucket policies on the S3 API; retention comes as bucket lock rules.

Before you call either

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

Cloudflare R2

  1. Set region to auto and the endpoint to https://<account-id>.r2.cloudflarestorage.com. us-east-1 also works, other region names fail
  2. Ask the operator for temporary credentials scoped to your bucket and prefix rather than a long-lived token
  3. For public reads put a custom domain or an r2.dev subdomain on the bucket; presigned URLs only sign the S3 hostname
  4. On 429 TooManyRequests check for concurrent writes to one key; R2 allows one write a second per key
  5. Send If-None-Match with * on PutObject so a retried upload can't overwrite someone else's object; a 412 on retry means the first write landed, and the 412 is billed as a Class A operation

Questions

Which is better for AI agents, Backblaze B2 or Cloudflare R2?

Backblaze B2 scores 83.8 (A) on agent readiness against Cloudflare R2's 78.8 (A), and leads in 4 of 7 scored categories. Cloudflare R2 leads on agent ergonomics and maintenance & community.

Do Backblaze B2 and Cloudflare R2 need an API key?

Both need an API key.

Can an agent call Backblaze B2 and Cloudflare R2 without installing anything?

Yes. Backblaze B2 has a hosted endpoint at https://s3.us-west-004.backblazeb2.com and Cloudflare R2 at https://<account-id>.r2.cloudflarestorage.com.

Are Backblaze B2 and Cloudflare R2 open source?

Backblaze B2 is open source (MIT). No open-source release is listed for Cloudflare R2.

Other comparisons with Backblaze B2 or Cloudflare R2

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.