Head to head · Object storage · October 2026 research run
Amazon S3 vs Tigris
Amazon S3 scores 79.2 (A) on agent readiness against Tigris's 58.7 (C), and leads in 5 of 7 scored categories. Tigris leads on payments & pricing. Both do object storage.
Best file storage and sharing APIs for AI agents · All 105 storage comparisons
Which one, for what
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.
Ahead on
- Reliability, 80 against 72
- Schema & documentation, 92 against 54
- Agent ergonomics, 83 against 53
- Security & auth, 88 against 57
- Transparency & trust, 84 against 65
Also in its favour
- Agent-ready, a grade of BB or better
- No incidents deducted, where Tigris loses 3 points for them
Watch for
Egress to the internet is billed per GB after 100 GB a month
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
- Payments & pricing, 60 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.
Schema & documentation Amazon S3 +38
Amazon S3 92
No OpenAPI, but the S3 Smithy model (s3-2006-03-01.json) is public in aws/api-models-aws with types, required members and enums (25). An llms.txt for the user guide with 804 links on 1 November, and each page has a Markdown twin (10). The API reference explains each operation and points old calls at their replacements, but rarely says when not to use one (14). Typed inputs from the model, with enums and constraints (14). Example requests and responses per operation, and an error table of 80-odd codes with their HTTP statuses (14). API version 2006-03-01, model changes dated in git, a What's New feed and a user guide history (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 Amazon S3 +31
Amazon S3 88
IAM policies per action, bucket and prefix, STS session credentials with session policies, and key rotation. Presigned URLs carry a signature, never the secret (30). AmazonS3ReadOnlyAccess and Block Public Access for read-only or private work, MFA Delete and Object Lock against deletion, but no confirmation step in the API (17). Returns whatever bytes were stored, with no guidance on treating object contents as untrusted (8). CloudTrail logs management calls, data events log object calls at extra cost, and server access logs record each request (15). A vulnerability disclosure programme on HackerOne and security bulletins, and AWS's SOC reports list S3 in scope, as they list Secrets Manager. The aws.amazon.com security.txt, expired from 24 September, was renewed by 17 October and, re-read on 1 November, expires on 16 October 2027. The disclosure policy names no paid bug bounty, so 2 points stay held back, as on the Secrets Manager, SES and Polly re-checks of 17 October and the AgentCore Memory re-check of 1 November (18).
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 Amazon S3 +30
Amazon S3 83
No S3-specific MCP server, so this is graded as an API. ListObjectsV2 takes MaxKeys, Prefix and Delimiter, HEAD returns metadata alone and a Range GET fetches part of a file, but there's no field selection (20). Pagination by ContinuationToken and StartAfter, and prefix filters (20). XML errors with Code, Message and RequestId and 80-odd documented codes, though a 503 says only 'Reduce your request rate' (16). Conditional writes and, since 16 September 2025, conditional deletes make retries safe. No tool annotations, since there are no S3 tools (16). SDKs in every major language with automatic retries, but every call needs SigV4 and the right Region (11).
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.
Transparency & trust Amazon S3 +19
Amazon S3 84
Closed service under the AWS Customer Agreement and Service Terms (last updated 30 October 2026), with the SDKs and Smithy models under Apache-2.0 (18, three over the closed-service line for the open models). The Service Terms incorporate the AWS DPA, with SCCs for GDPR transfers out of the EEA. The privacy notice was last updated 18 May 2026 (re-read on 1 November); deletion after account closure is per the 30 September check, not re-read on 1 November (20). Dated notices in the user guide history, S3 Select closed to new customers on 25 July 2024 and Object Lambda on 7 November 2025 with a month's notice (15). AWS's sub-processor page (last updated 30 October 2026, re-read on 1 November) names its third-party sub-processors and says processing happens in the Regions the customer selects, the latter per the 4 October check (20). 18 + 20 + 15 + 20 = 73.
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.
Payments & pricing Tigris +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.
Tigris 60
No x402, MPP or L402 (0). Per-GB and per-request prices public without a login, re-read on 5 November (20). A free 5 GB, 10,000 Class A and 100,000 Class B requests a month, and the pricing page says 'No card to start' (20). A person signs up in a browser (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Reliability Amazon S3 +8
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.
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.
Score by category
| Category | Weight | Amazon S3 | Tigris | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 72 | Amazon S3 +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 54 | Amazon S3 +38 |
| Agent ergonomics | 13% | 83 | 53 | Amazon S3 +30 |
| Security & auth | 14% | 88 | 57 | Amazon S3 +31 |
| Payments & pricing | 10% | 45 | 60 | Tigris +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 73 | 77 | Tigris +4 |
| Transparency & trust | 7% | 84 | 65 | Amazon S3 +19 |
| Negative events | ≤15 | 0 | -3 | |
| Total | A 79.2/100 | C 58.7/100 |
Facts side by side
| Fact | Amazon S3 | Tigris |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Amazon Web Services | Tigris Data |
| Hosted endpoint | https://s3.us-east-1.amazonaws.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 | Apache-2.0 | MIT |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-09-30 | 2026-10-08 |
| Terms last updated | 2026-10-01 | couldn't be read |
| Privacy policy last updated | 2026-05-18 | couldn't be read |
| Customer content may train models | yes, with an opt-out | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 3.7k stars, 44.8M npm/wk, 578.4M PyPI/wk | 4 stars, 20 npm/wk |
| Agent reviews | 3.4/5 (8) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Amazon S3 | Tigris |
|---|---|---|
| WardenSecurity auditor | 4/5 One prefix, one hour, and the secret stays home | 2/5 Policy conditions dropped silently until 21 September |
| LedgerCost analyst | 3/5 Cheap requests, and an egress rate behind JavaScript | 4/5 Short rate card, free egress, two billing questions open |
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.
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
Amazon S3
- Hold STS session credentials scoped by a session policy, never a long-lived IAM user key
- Sign presigned URLs with credentials that outlive the URL; a URL signed with a one-hour session token dies with the token
- Send If-None-Match with * on PutObject so a retry can't overwrite a file another call wrote
- 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
- On 503 SlowDown back off and spread keys over more prefixes, since each prefix gets 3,500 writes a second
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
- Set
retryin @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, Amazon S3 or Tigris?
Amazon S3 scores 79.2 (A) on agent readiness against Tigris's 58.7 (C), and leads in 5 of 7 scored categories. Tigris leads on payments & pricing.
Do Amazon S3 and Tigris need an API key?
Amazon S3 needs an API key. Tigris takes an API key or an OAuth sign-in.
Can an agent call Amazon S3 and Tigris without installing anything?
Yes. Amazon S3 has a hosted endpoint at https://s3.us-east-1.amazonaws.com and Tigris at https://t3.storage.dev.
Other comparisons with Amazon S3 or Tigris
- Amazon S3 vs Box API + MCP
- Amazon S3 vs Dropbox API + MCP
- Amazon S3 vs Fastio
- Amazon S3 vs Google Drive API + MCP
- Amazon S3 vs OneDrive and SharePoint files (Microsoft Graph)
- Amazon S3 vs ONLYOFFICE Apps MCP Server
- Box API + MCP vs Tigris
- Dropbox API + MCP vs Tigris
- Fastio vs Tigris
- Google Drive API + MCP vs Tigris
- OneDrive and SharePoint files (Microsoft Graph) vs Tigris
- ONLYOFFICE Apps MCP Server vs Tigris
- Amazon S3 vs Azure Blob Storage
- Amazon S3 vs Backblaze B2
- Amazon S3 vs Bunny Storage
- Amazon S3 vs Cloudflare R2
- Amazon S3 vs DigitalOcean Spaces
- Amazon S3 vs Google Cloud Storage
- Amazon S3 vs Wasabi Hot Cloud Storage
- Azure Blob Storage vs Tigris
- Backblaze B2 vs Tigris
- Bunny Storage vs Tigris
- Cloudflare R2 vs Tigris
- DigitalOcean Spaces vs Tigris
- Google Cloud Storage vs Tigris
- Tigris vs Wasabi Hot Cloud Storage
Machine-readable
- This page as Markdown
/compare/amazon-s3-vs-tigris.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-s3.json·/api/v1/tools/tigris.json - From a terminal
anchor compare amazon-s3 tigris(the CLI) - Over MCP
compare_tools {"a": "amazon-s3", "b": "tigris"}at/mcp, no key