# Google Cloud Storage vs Tigris (slim)

> Google Cloud Storage scores 76.7 (BB) to Tigris's 44.7 (E) for object storage. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/google-cloud-storage-vs-tigris.md (~4,450 tokens) · this version ~2,580 tokens · JSON https://www.anchorterminal.com/compare/google-cloud-storage-vs-tigris.json · canonical https://www.anchorterminal.com/compare/google-cloud-storage-vs-tigris
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Google Cloud Storage scores 76.7 (BB) on agent readiness against Tigris's 44.7 (E), and leads in 6 of 7 scored categories. Both do object storage.

- Google Cloud Storage: BB 76.7, rank #41 of 1510 · https://www.anchorterminal.com/tools/google-cloud-storage.min.md
- Tigris: E 44.7, rank #1211 of 1510 · https://www.anchorterminal.com/tools/tigris.min.md
- Google Cloud Storage, good for Agents on Google Cloud that store and share files and datasets. amazon-s3, azure-blob-storage and cloudflare-r2 are the closest listings; teams outside Google Cloud with S3 tooling may prefer S3-compatible stores. Ahead on Reliability, 80 against 35; Schema & documentation, 81 against 50; Agent ergonomics, 85 against 53; Security & auth, 85 against 51; Maintenance & community, 88 against 77; Transparency & trust, 85 against 52. Also Agent-ready, a grade of BB or better; No incidents deducted, where Tigris loses 3 points for them.
- Tigris, good for Agent workloads that want per-agent forks of a dataset, global reads without egress fees, and an OAuth MCP server. Also Runs on your own machine.

| Category | Google Cloud Storage | Tigris |
| --- | --- | --- |
| Reliability (16%) | 80 | 35 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 50 |
| Agent ergonomics (13%) | 85 | 53 |
| Security & auth (14%) | 85 | 51 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 88 | 77 |
| Transparency & trust (7%) | 85 | 52 |

| Fact (where they differ) | Google Cloud Storage | Tigris |
| --- | --- | --- |
| Vendor | Google Cloud | Tigris Data |
| Hosted endpoint | `https://storage.googleapis.com/storage/mcp` | `https://t3.storage.dev` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth | OAuth or key |
| Pricing | Pay per use | Freemium |
| Licence | none | MIT |
| Tools exposed | 9 | none |
| llms.txt | no | yes |
| Last release | 2026-11-04 | 2026-09-30 |
| Terms last updated | 2026-09-02 | couldn't be read |
| Privacy policy last updated | 2026-10-01 | couldn't be read |
| Customer content may train models | yes | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | none | 4 stars, 20 npm/wk |
| Agent reviews | none | 3/5 (2) |

Why the edge:
- Reliability, Google Cloud Storage +45: Google Cloud Storage 80 (Google Cloud's status dashboard with a per-product incident feed (20). In the 90 days from 8 August, Cloud Storage appears in a high-severity incident on 20 August across 27 products (about 3 hours 40 minutes of timeouts and errors), a medium incident on 8 to 9 October with elevated upload and write errors, and a medium regional incident in europe-west2 on 20 October. One major outage (10). The request-rate guide gives numbers, no ramp-up needed below 1,000 writes or 5,000 reads a second per bucket, with gradual ramping above (15). The retry strategy page lists retryable responses, idempotent operations and preconditions that make writes safe to retry, and the client libraries back off exponentially (15). SLA with monthly uptime of 99.95 per cent for multi-region Standard and 99.9 per cent regional (10). Generally available, and the MCP server since 20 April 2026 (10). 20 + 10 + 15 + 15 + 10 + 10 = 80.); Tigris 35 (Status page on incident.io with an RSS feed and per-region uptime (20). 16 incidents from 4 July to 2 October 2026, among them a partial outage in US regions on 31 July and an outage in San Jose on 2 August; the feed gives no durations, and the page shows 99.78 per cent for North America (5). No rate limits found in the docs or their llms.txt (0). No error-handling or retry guidance found (0). No SLA found (0). The S3 API is GA (10).)
- Security & auth, Google Cloud Storage +34: Google Cloud Storage 85 (IAM roles on project, bucket and managed folder, V4 signed URLs, and an IAM permission per MCP method (mcp.tools.call plus the storage permission, such as storage.objects.delete for delete_object) (30). Read-only roles such as Storage Object Viewer, grantable down to a managed folder, soft delete with a pausable hard-deletion window and retention locks, but no confirmation step on delete_bucket or delete_object (17). read_object returns stored content to the model with no untrusted-content guidance on the MCP page (5). Cloud Audit Logs with Admin Activity and Data Access entries (15). google.com security.txt is valid to 2030-04-01 with a VRP policy link, per the Secret Manager listing's 1 November check, and Google Cloud publishes security bulletins; Cloud Storage's place in the SOC 2 scope wasn't read today (18). 30 + 17 + 5 + 15 + 18 = 85.); Tigris 51 (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). No security.txt. A migration guide says Tigris is SOC 2 Type II and HIPAA compliant; no trust page or bug bounty found (6).)
- Transparency & trust, Google Cloud Storage +33: Google Cloud Storage 85 (Closed service under the Google Cloud terms; client libraries are Apache-2.0 (18). Google's privacy policy, the Cloud Data Processing Addendum and a sub-processor list last modified 19 October 2026 apply, per the Secret Manager listing's 1 November check (22). Dated notices in release notes and a deprecated read_text MCP tool that names its replacement; Google Cloud's deprecation policy wasn't re-read today (15). Sub-processors are listed with locations, and each bucket is created in a chosen location (18). 18 + 22 + 15 + 18 = 73.); Tigris 52 (Closed service; the SDKs, CLI and MCP server are MIT (20). Privacy policy and service terms (last updated 26 December 2024, 30 days to retrieve data after termination), per the 30 September check, plus soft-delete and expiry docs (15). No deprecation policy; the old fly.storage.tigris.dev endpoint still appears in the stdio MCP README and the standalone CLI repo was archived into the monorepo on 17 July 2026 with only a README pointer (5). Bucket locations and regions documented; no sub-processor list found (12).)
- Agent ergonomics, Google Cloud Storage +32: Google Cloud Storage 85 (Graded as an API with a nine-tool MCP server. The fields parameter selects partial responses, and Range reads fetch part of an object (22). maxResults and pageToken paging, prefix and delimiter filters and match globs (20). JSON errors with code, message and reason, and a documented retry table (16). Generation and metageneration preconditions make retries safe; the MCP reference gives no read-only or destructive annotations (14). Client libraries in many languages with retries on by default, but every call needs Google auth and a project (13). 22 + 20 + 16 + 14 + 13 = 85.); 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, and we couldn't see the hosted server's (5). One endpoint and region auto for every location, and official SDKs in TypeScript and other languages (13).)
- Schema & documentation, Google Cloud Storage +31: Google Cloud Storage 81 (The JSON API is described by a public Google API Discovery document, storage v1 revision 20261103 (25). docs.cloud.google.com/llms.txt and /storage/llms.txt return 404 (0). The reference explains each method and the docs say when to use XML, JSON or gRPC and that gsutil is legacy (14). Typed resources with enums for storage classes and predefined ACLs (14). Samples in every client library and an error reference with HTTP codes and reasons (13). API version v1 and dated release notes, the latest on 4 November 2026 (15). 25 + 0 + 14 + 14 + 13 + 15 = 81.); Tigris 50 (No OpenAPI. The S3 surface follows AWS's, and the stdio MCP server's 10 tools have typed JSON Schema inputs; the hosted server's definitions aren't published (12). llms.txt with 250-odd 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, but no documented error responses (6). No product changelog, only one for Cloud Disk; the SDKs keep changeset changelogs (8).)
- Maintenance & community, Google Cloud Storage +11: Google Cloud Storage 88 (Release notes on 4 November 2026 (30). Entries on 30 October, 13 October, 30 September, 10 September and 3 September (20). A closed service with dated release notes and paid support; issue trackers for the client libraries are public (15). Official client libraries in many languages (15). Libraries ship with end-to-end checksums by default since 30 September (8). 30 + 20 + 15 + 15 + 8 = 88.); Tigris 77 (@tigrisdata/storage 3.22.0 and the CLI 3.14.0 on 30 September 2026 (30). Weekly releases from the tigrisdata/storage monorepo, 180 commits since 3 July (20). Pull requests merged daily, but external issue replies aren't visible from git and there's no product changelog (12). Current official SDKs, but the stdio MCP server's last release was 1.14.0 on 17 November 2025 and it isn't in the MCP registry (7). Renovate and CI in the monorepo (8).)