Head to head · Storage object · October 2026 research run
Bunny Storage vs Tigris
Bunny Storage has a score of 58.7 (C) against Tigris's 44.6 (E). Both do storage object. The largest gap is reliability, 40 points.
Which one, for what
Pick Bunny Storage for
- reliability (+40)
- schema & documentation (+14)
- payments & pricing (+10)
- transparency & trust (+13)
Pick Tigris for
- security & auth (+6)
- maintenance & community (+14)
Score by category
| Category | Weight this run | Bunny Storage | Tigris | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 75 | 35 | Bunny Storage +40 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 64 | 50 | Bunny Storage +14 |
| Agent ergonomics | 13%16.2 | 57 | 53 | Bunny Storage +4 |
| Security & auth | 14%17.5 | 45 | 51 | Tigris +6 |
| Payments & pricing | 10%12.5 | 40 | 30 | Bunny Storage +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 63 | 77 | Tigris +14 |
| Transparency & trust | 7%8.8 | 64 | 51 | Bunny Storage +13 |
| Negative events | ≤15 | 0 | -3 | |
| Total | 58.7 · C | 44.6 · E |
Facts side by side
| Fact | Bunny Storage | Tigris |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | bunny.net | Tigris Data |
| Hosted endpoint | https://storage.bunnycdn.com | https://t3.storage.dev |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | none | none |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | not listed |
| Last release | 2026-08-14 | 2026-09-30 |
| Popularity | 46 stars, 10k npm/wk | 4 stars, 20 npm/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
Verdicts
Bunny Storage
$0.01 a GB-month for Standard storage, no request fees, free traffic to the CDN. Zone passwords are the only storage credential, read-write or read-only, with no expiry, prefix scope or usage log.
Tigris
No egress fees, and one endpoint (t3.storage.dev) with region auto for every location. 16 status incidents between 4 July and 2 October 2026, including outages in US regions on 31 July and 2 August.
Before you call either
Bunny Storage
- Use the regional hostname you were given when the zone was created (storage.bunnycdn.com is Frankfurt). Other regions return a 401
- Send the body as raw bytes with --data-binary. Base64 or form encoding gets a 401
- Add the Checksum header (uppercase SHA-256 hex) on uploads so a corrupt transfer fails instead of landing
- End a listing path with a slash, expect one JSON array for the whole folder, and keep to 5 listings in flight
- On a SlowDown 503 from the S3 endpoint wait the Retry-After seconds, then back off exponentially
Tigris
- 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 - Ask for an access key with a ReadOnly or ReadWrite role on one bucket rather than an org-wide key
- Keep presigned URLs short; Tigris accepts up to 90 days
- Don't call tigris_list_objects on a large bucket; it walks every object with no limit or prefix
- Use @tigrisdata/iam 2.6.0 or later before writing policies with conditions
Other comparisons with Bunny Storage or Tigris
Machine-readable
/api/v1/tools/bunny-storage.json·/api/v1/tools/tigris.json- This page as Markdown,
/compare/bunny-storage-vs-tigris.md