Google Cloud Storage vs Wasabi Hot Cloud Storage

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.

Wasabi Hot Cloud Storage 46

Closed service. The newest dated change we found on 2 November is still the hosted MCP article of 28 August 2026, 66 days before the check (20). Dated entries in the 90 days from 4 August are that article and the API news note of 24 August. The console notes are still dated only 'Summer 2026', and the Wasabi Cloud NAS 3.1.0.32 entry only 'August 2026'; docs pages re-stamped since (the announcements page on 5 October, the sign-up guide on 21 October) record no dated service change (10). An announcements page and email support, with no public issue tracker or forum found (8). No Wasabi SDK. AWS SDKs are the supported clients, and the only MCP registry entry for Wasabi is still a third party's, io.github.mrfentmen/wasabi-mcp (5). No packages to check (3).

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.

Wasabi Hot Cloud Storage 59

No OpenAPI file. The S3 reference documents differences from AWS S3 API version 2006-03-01 and lists the supported IAM and STS actions, so the AWS model is the contract by compatibility (12). llms.txt at docs.wasabi.com with about 1,490 Markdown pages on 2 November (10). The reference explains Wasabi's own operations (MOVE, compose, append) and leaves the rest to AWS's documentation (10). Typed through the AWS model, with Wasabi's extra headers described in tables (9). An error table of more than 60 codes with HTTP statuses, and request examples for the extensions, but the general error page lists only four statuses (11). API versions are pinned, but the API news page is still the one-line update of 24 August 2026 and its archive stops at June 2024 (7).

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.

Wasabi Hot Cloud Storage 68

Graded as an API. The MCP beta's tool definitions are not published. Responses are sized through S3's own controls (max-keys, prefix, delimiter, HEAD and Range), which Wasabi supports by compatibility and does not document itself (18). Pagination and prefix filters as in S3 (18). Named error codes with messages, and little recovery guidance beyond a few such as 'Try again in five minutes' (12). A PUT by key can be repeated safely. No conditional-write or retry guidance was found (10). AWS SDKs and the AWS CLI work with a changed endpoint, and there is no Wasabi SDK. The endpoint must match the bucket's region, or PUT and DELETE fail (10).

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.

Wasabi Hot Cloud Storage 65

Graded as a hosted API on the S3 surface. Status page at status.wasabi.com with a readable history feed (20). In the 90 days to 2 November 2026, per the 9 October check (not re-read on 2 November, since the feed now starts at 10 October and the history page is drawn by script), S3 in Frankfurt was unavailable for 27 minutes on 4 August, PUT latency and errors hit US-EAST-1 on 26 August, and there were two console access incidents and one WACM reporting fault. The feed read on 2 November adds a power event in AP-SOUTHEAST-1 (Singapore) on 10 October, with errors or failed requests in that region from 02:27 UTC until a fix was reported at 02:55 (resolved 04:11), and otherwise only announced maintenance. All read as minor, as each touched one region or one component (20). No request limits with numbers for the S3 API. The fair use policy adjusts concurrency per account, and only the Account Control API has figures (0). The error table lists RequestRateLimitExceeded and a 503 Unavailable ("Try again later"), with no Retry-After or backoff guidance found (5). An SLA page is published. Its current text is drawn by script, and the version of 21 February 2024 gives credits of 10 per cent below 99.9 per cent monthly uptime and 25 per cent below 99.0 (10). The S3 API is generally available, and the MCP server is a beta (10).

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.

Wasabi Hot Cloud Storage 71

Closed service under a Customer Agreement whose current text is drawn by script. The version of 22 September 2025 is clear on ownership and deletion of content (13). That version says content is irretrievably deleted after deletion or termination, and the DPA of 14 July 2025 covers return and destruction and breach notice. The current privacy policy and DPA were unread, and no retention periods in days were found (18). Dated notices for the FTP and TLS 1.0 and 1.1 retirements and 51 days' notice of the July 2026 price rise, but no general deprecation policy (10). A sub-processor list with locations and purposes (version of 19 December 2025), and the data centre operator named for each of 16 regions (18).

Google Cloud Storage 30

No x402, MPP or L402 (0). Per-operation and per-GB prices public without login, though the regional storage table draws by script (20). Always Free covers 5 GB-months and small operation counts in three US regions, but a Google Cloud billing account is needed; whether a card is required wasn't confirmed today (10). A person creates the project and billing account in a browser (0). 0 + 20 + 10 + 0 = 30.

Wasabi Hot Cloud Storage 40

No x402, MPP or L402 (0). $7.99 a TB-month is public without a login, with the 1 TB and 90-day minimums stated in the pricing FAQ (20). A free trial with no card, 100 GB for 30 days with a company email (20). A person fills in a form with a phone number, opens an emailed invitation and sets up MFA. The Account Control API creates sub-accounts only for partners and control accounts (0).