Head to head · Object storage · October 2026 research run

Bunny Storage vs Tigris

Bunny Storage scores 65.1 (B) on agent readiness against Tigris's 58.7 (C), and leads in 3 of 7 scored categories. Tigris leads on security & auth. Both do object storage.

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

Which one, for what

Bunny Storage B

Best for An agent that publishes files to be served through a CDN at the lowest price and doesn't need fine-grained credentials.

Ahead on

  • Reliability, 85 against 72
  • Schema & documentation, 67 against 54
  • Agent ergonomics, 61 against 53

Also in its favour

  • No incidents deducted, where Tigris loses 3 points for them

Watch for

Zone passwords are the only storage credential, read-write or read-only, with no expiry, prefix scope or usage log

Tigris C

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

Ahead on

  • Security & auth, 57 against 45

Also in its favour

  • Runs on your own machine

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.

Reliability Bunny Storage +13

Bunny Storage 85

Public status page at status.bunny.net with an Atom history, re-read on 4 November (20). Three storage incidents in the 90 days from 6 August, each in one region. Elevated Storage API errors in London on 18 August (02:28 to 04:29 UTC), about 10 minutes of Frankfurt unavailability on 15 October from a provider's core network outage, and intermittent listing and upload problems for storage zones in DE on 15 and 16 October. Partial incidents read as minor, so minor only (20). The 24 August and 20 November Sydney maintenance affects non-replicated zones and isn't an incident. 500 requests a second per zone and 1 Gbps per connection on S3, 250 concurrent HTTP connections per zone per server, 5 listings and 30 deletes at a time (15). The limits page documents 429 Too Many Requests on the HTTP API and 503 SlowDown with Retry-After: 5 on S3, with exponential backoff, and the S3 page says to retry a DeleteObjects bulk delete after the Retry-After interval, a deleted missing key counting as success (15). SLA of 99.99 per cent with credits of 12 to 240 hours, re-read (10). The HTTP API is GA, but S3, the only route to expiring links, is still public preview (5). 20+20+15+15+10+5 = 85.

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.

Schema & documentation Bunny Storage +13

Bunny Storage 67

No OpenAPI for the storage data plane; the storage API reference is a Markdown page, and the core spec covers zone management, now including a Get Storage Zone Regions call (12). llms.txt with Markdown pages, re-read on 4 November (10). The HTTP API page says what each call does in a line or two (12). Path-based calls with a few headers, little to type (9). curl examples for each call. The HTTP API page still documents only 201, 400 and 401, but the S3 page now has an error table (412, 400 BadDigest, MetadataTooLarge, 501, 503 SlowDown and others) and the limits page gives the response for each rate limit (12). A dated changelog, with storage entries on 14 August and 23 October 2026; the storage API itself carries no version (12). 12+10+12+9+12+12 = 67.

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 Tigris +12

Bunny Storage 45

Each zone has a read-write and a read-only password, also used as the S3 secret, with a read-only S3 password since 30 July 2026. No expiry or prefix scope, and revoking means resetting. The account API key has full access (20). Read-only passwords, and deleting the zone root needs allowRootDelete=true, but nothing finer (12). Returns stored bytes, with no guidance on treating them as untrusted (8). No audit log of storage or API key use found (3). bunny.net/.well-known/security.txt redirects to an HTML page on 4 November, and the docs name no disclosure policy, bounty or certification (2). 20+12+8+3+2 = 45.

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 Bunny Storage +8

Bunny Storage 61

No MCP server. An HTTP listing returns the whole folder as one JSON array; S3 ListObjectsV2 can page and filter by prefix (12). The docs give no pagination for HTTP listings; S3 has continuation tokens and prefixes, in preview (10). The S3 error table and the limits page's rate-limit responses give codes an agent can act on, while the HTTP API still documents three (12). A PUT by path is safe to repeat, the Checksum header rejects corrupt uploads, S3 takes conditional requests, and DeleteObjects reports each key separately (14). One PUT with one header, and official SDKs for TypeScript, PHP, .NET and Java (13). 12+10+12+14+13 = 61.

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.

Score by category

CategoryWeightBunny StorageTigrisEdge
Reliability16%8572Bunny Storage +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6754Bunny Storage +13
Agent ergonomics13%6153Bunny Storage +8
Security & auth14%4557Tigris +12
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7577Tigris +2
Transparency & trust7%6165Tigris +4
Negative events≤150-3
TotalB 65.1/100C 58.7/100

Facts side by side

FactBunny StorageTigris
KindHTTP APIHTTP API
Vendorbunny.netTigris Data
Hosted endpointhttps://storage.bunnycdn.comhttps://t3.storage.dev
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPay per useFreemium
x402nono
LicencenoneMIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-232026-10-08
Terms last updatedno date givencouldn't be read
Privacy policy last updatedno date givencouldn'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 noticeyescouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity46 stars, 10k npm/wk4 stars, 20 npm/wk
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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

Bunny Storage

$0.01 a GB-month for Standard storage, no request fees and free traffic to the CDN, with documented 429 and SlowDown handling. Zone passwords are the only storage credential, read-write or read-only, with no expiry, prefix scope or usage log, and S3 is still public preview.

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

Bunny Storage

  1. Use the regional hostname you were given when the zone was created (storage.bunnycdn.com is Frankfurt). Other regions return a 401
  2. Send the body as raw bytes with --data-binary. Base64 or form encoding gets a 401
  3. Add the Checksum header (uppercase SHA-256 hex) on uploads so a corrupt transfer fails instead of landing
  4. End a listing path with a slash, expect one JSON array for the whole folder, and keep to 5 listings in flight
  5. On a 429 from the HTTP API or a SlowDown 503 from S3 wait the Retry-After seconds where given, then back off exponentially

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, Bunny Storage or Tigris?

Bunny Storage scores 65.1 (B) on agent readiness against Tigris's 58.7 (C), and leads in 3 of 7 scored categories. Tigris leads on security & auth.

Do Bunny Storage and Tigris need an API key?

Bunny Storage needs an API key. Tigris takes an API key or an OAuth sign-in.

Can an agent call Bunny Storage and Tigris without installing anything?

Yes. Bunny Storage has a hosted endpoint at https://storage.bunnycdn.com and Tigris at https://t3.storage.dev.

Other comparisons with Bunny Storage 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.