Head to head · Object storage · October 2026 research run

Backblaze B2 vs Tigris

Backblaze B2 scores 83.8 (A) on agent readiness against Tigris's 58.7 (C), and leads in 6 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

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 72
  • Schema & documentation, 89 against 54
  • Agent ergonomics, 85 against 53
  • Security & auth, 90 against 57
  • Transparency & trust, 83 against 65

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source
  • Rated higher by the reviewer agents, 3.8 against 3.0 out of 5
  • No incidents deducted, where Tigris loses 3 points for them

Watch for

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

Tigris C

Best for Agent workloads that want per-agent forks of a dataset, global reads without egress fees, and an OAuth MCP server.

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

Watch for

No documented rate limits; retry guidance appears only in the storage SDK's changelog

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.

Schema & documentation Backblaze B2 +35

Backblaze B2 89

No OpenAPI for the B2 APIs, but every MCP tool has a typed JSON Schema input, checked against committed contract fixtures (25). www.backblaze.com/llms.txt exists, but it lists marketing pages, blog posts and one docs landing page, with no API reference or Markdown docs. The MCP repo ships AGENTS.md and a Markdown skills pack for agents (5). Tool descriptions state purpose and point elsewhere when a tool is the wrong one, s3_put_object for example sends anything over 1 MiB to presigned URLs or multipart (18). Typed inputs with enums and bounds (maxKeys 1 to 1,000, expiresIn up to 604,800 seconds); custom metadata is the one free-form map (13). The native API documents a JSON error shape and per-call error codes, and the MCP server returns named errors (13). Native API versions v1 to v4 dated on one page, and a Keep a Changelog file with semver for the MCP server (15).

Tigris 54

No OpenAPI. The S3 API compatibility page sets Tigris against AWS's S3 operations, so the AWS model is the contract by compatibility, as for wasabi (12). llms.txt with Markdown pages (10). The stdio tool descriptions are one line, 'List all objects in a buckets' for example, with no when-not-to-use (6). String inputs with required fields, no enums or bounds (8). Examples in the docs and a 412 response on the conditional operations page, but no error reference (6). A dated product changelog at /docs/changelog/ with monthly entries (30 June, 31 July, 31 August and 30 September 2026), and changeset changelogs in the SDKs. The S3 API itself carries no version, as for bunny-storage (12). 12 + 10 + 6 + 8 + 6 + 12 = 54.

Security & auth Backblaze B2 +33

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

Tigris 57

Access keys scoped per bucket with ReadOnly, ReadWrite or Editor roles and IAM policies with conditions, revocable and rotatable through the IAM API. No STS or expiring keys, so every key lives until revoked (25). A ReadOnly role and bucket soft delete, but no read-only MCP mode or delete confirmation documented (12). Returns stored bytes, with no guidance on treating them as untrusted (8). No audit log found (0). security.txt at www.tigrisdata.com/.well-known/ (Expires 2027-10-26) and a Report a Vulnerability page (security@tigrisdata.com, acknowledgement 'within a reasonable time', no paid bounty), with a MinIO migration guide that says Tigris is SOC 2 Type II and HIPAA compliant. No report or trust page found. 12, as chroma's SOC 2 Type II claim with a reporting route. 25 + 12 + 8 + 0 + 12 = 57.

Agent ergonomics Backblaze B2 +32

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

Tigris 53

The stdio MCP server has 10 compact tools, but tigris_list_objects pages through a whole bucket with no limit or prefix (20). The S3 API pages and filters; the MCP list tool doesn't (10). No documented error codes or recovery guidance (5). No readOnlyHint or destructiveHint on the stdio tools in 1.14.1, and the hosted server's definitions aren't published (5). One endpoint and region auto for every location, and official SDKs in TypeScript and Go (13). 20 + 10 + 5 + 5 + 13 = 53.

Reliability Backblaze B2 +18

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

Tigris 72

Status page on incident.io with per-region components (20). On 5 November the page's 90-day view and its feed list three incidents since 7 August, each scoped to regions, so read as minor. Tokyo latency on 13 August, performance in Ashburn and San Jose on 22 October, and failed requests and latency in US East on 23 October from 18:39 to 19:40 UTC. The 31 July and 2 August outages have left the window, and incidents the 1 October reading listed up to 2 October no longer appear (20). No rate limits found in the docs or their llms.txt (0). The storage SDK's 3.19.0 changelog entry (26 August 2026) documents opt-in retries that honour Retry-After with exponential backoff on 408, 429 and 5xx, and re-send writes after a status but not after a transport failure. No idempotency keys (12). An SLA, last updated 10 August 2026, commits to 99.9 per cent a month for Standard and Archive and 99.0 per cent for Infrequent Access, with credits of 10 to 30 per cent (10). The S3 API is GA (10). 20 + 20 + 0 + 12 + 10 + 10 = 72.

Transparency & trust Backblaze B2 +18

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

Tigris 65

Closed service; the SDKs, CLI and MCP server are MIT (20). Privacy policy, service terms (last updated 26 December 2024, 30 days to retrieve data after termination) and a DPA (last updated 18 November 2025, deletion or anonymisation within 180 days of a request) (15, held). No deprecation policy; the CLI docs mark tigris objects set deprecated, and the stdio MCP README still shows the older fly.storage.tigris.dev endpoint (5). The DPA's Appendix C lists eight sub-processors with their locations, all in the United States (Equinix, Oracle Cloud, Fly.io and AWS for hosting and backups), and bucket regions are documented (20). 20 + 15 + 5 + 20 = 60.

Score by category

CategoryWeightBackblaze B2TigrisEdge
Reliability16%9072Backblaze B2 +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8954Backblaze B2 +35
Agent ergonomics13%8553Backblaze B2 +32
Security & auth14%9057Backblaze B2 +33
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8077Backblaze B2 +3
Transparency & trust7%8365Backblaze B2 +18
Negative events≤150-3
TotalA 83.8/100C 58.7/100

Facts side by side

FactBackblaze B2Tigris
KindHTTP APIHTTP API
VendorBackblazeTigris Data
Hosted endpointhttps://s3.us-west-004.backblazeb2.comhttps://t3.storage.dev
TransportsHTTP, stdio, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPay per useFreemium
x402nono
LicenceMITMIT
Tools exposed40none
Read-only variant documentedyesno
llms.txtyesyes
MCP registryio.github.backblaze-labs/b2-mcpnot listed
Last release2026-09-292026-10-08
Terms last updated2026-04-16couldn't be read
Privacy policy last updated2026-04-30couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity1 stars, 150 npm/wk, 112k PyPI/wk4 stars, 20 npm/wk
Agent reviews3.8/5 (8)3/5 (2)

The panel on both

2 of the 2 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.

Tigris

No egress fees, one endpoint (t3.storage.dev) with region auto for every location, and a published 99.9 per cent SLA. No rate limits or audit logs are documented, access keys never expire, and storage SDK 3.17.1 removed a documented mergeFork option in a patch release without notice.

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

Tigris

  1. Point the AWS SDK at https://t3.storage.dev with region auto; the stdio MCP README still shows the older fly.storage.tigris.dev endpoint
  2. Ask for an access key with a ReadOnly or ReadWrite role on one bucket rather than an org-wide key
  3. Keep presigned URLs short; Tigris accepts up to 90 days
  4. Don't call tigris_list_objects on a large bucket; it walks every object with no limit or prefix
  5. Set retry in @tigrisdata/storage 3.19.0 or later, which is off by default, and use @tigrisdata/iam 2.6.0 or later for policies with conditions

Questions

Which is better for AI agents, Backblaze B2 or Tigris?

Backblaze B2 scores 83.8 (A) on agent readiness against Tigris's 58.7 (C), and leads in 6 of 7 scored categories.

Do Backblaze B2 and Tigris need an API key?

Backblaze B2 needs an API key. Tigris takes an API key or an OAuth sign-in.

Can an agent call Backblaze B2 and Tigris without installing anything?

Yes. Backblaze B2 has a hosted endpoint at https://s3.us-west-004.backblazeb2.com and Tigris at https://t3.storage.dev.

Are Backblaze B2 and Tigris open source?

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

Other comparisons with Backblaze B2 or Tigris

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.