Meter
S3-compatible is an API claim, not a pricing or feature promise
S3-compatible storage implements some or all of the Amazon S3 API so S3-aware software can communicate with it. Compatibility is an operation-by-operation integration claim, not proof of identical pricing, Object Lock behavior, regions, or backup-tool support.
Put your own numbers through the calculator to see what this meter does to a normal month and to the day you restore.
S3-compatible means compatible with an API surface, not identical to Amazon S3
S3-compatible storage implements some or all of the Amazon S3 API surface so software written for S3-style buckets and objects can communicate with the service. The exact operation list, authentication behavior, limits, and extensions can differ. [1] [2] [3]
A true compatibility label does not prove support for multipart edge cases, versioning, lifecycle rules, Object Lock, legal holds, governance mode, compliance mode, or one backup tool's repository workflow. Those requirements must be checked separately. [1] [4] [5]
| Claim | What it establishes | What it does not establish | Source ref |
|---|---|---|---|
| S3-compatible endpoint | The service accepts documented S3-style API calls [1] | That every Amazon S3 operation is implemented | [1] |
| S3-aware backup tool | The tool can attempt its S3 workflow against the endpoint [2] | That every call, permission, or retention feature the tool uses succeeds | [2] |
| Object Lock support | A separate retention API contract when explicitly documented [5] | It cannot be inferred from generic S3 compatibility | [5] [1] |
| Price compatibility | does not apply. API naming does not standardize storage, request, retrieval, or egress prices [6] [7] | That two compatible providers produce the same receipt | [6] [7] |
The dataset records 48 compatible, 8 incompatible, and 5 not published offers
The provider dataset carries an explicit s3_compatible field on every offer. Across 61 offers, 48 are true, all 8 Azure Blob records are false, and all 5 Google Cloud Storage records are not published. No bare null is used. [8]
The table reports the captured field without upgrading not published to true and without treating false as a quality judgment. It answers only the S3 compatibility question recorded by the dataset. [8]
The dataset records 48 compatible, 8 incompatible, and 5 not published offers18 rows
| Provider | Captured offers | S3-compatible state | Interpretation | Source ref |
|---|---|---|---|---|
| Amazon S3 | 15 | 15 true [8] | Reference API; class and bucket-type feature scope still varies | [8] |
| Azure Blob Storage | 8 | 8 false [8] | The captured offer is not marked S3-compatible | [8] |
| Google Cloud Storage | 5 | 5 not published [8] | The checked pricing source does not establish full S3 compatibility | [8] |
| Cloudflare R2 | 2 | 2 true [8] | Compatibility is operation-specific; S3 Object Lock APIs are not implemented [1] | [8] [1] |
| Backblaze B2 | 1 | 1 true [8] | Feature and tool requirements remain separate | [8] |
| Wasabi | 1 | 1 true [8] | Feature and tool requirements remain separate | [8] |
| IDrive e2 | 1 | 1 true [8] | Feature and tool requirements remain separate | [8] |
| DigitalOcean Spaces | 2 | 2 true [8] | The vendor publishes an operation-level compatibility matrix [2] | [8] [2] |
| Scaleway Object Storage | 3 | 3 true [8] | Feature and tool requirements remain separate | [8] |
| OVHcloud Object Storage | 5 | 5 true [8] | Class-specific feature support still varies | [8] |
| Hetzner Object Storage | 1 | 1 true [8] | Feature and tool requirements remain separate | [8] |
| Akamai Cloud Object Storage | 1 | 1 true [8] | Feature and tool requirements remain separate | [8] |
| Vultr Object Storage | 5 | 5 true [8] | The vendor publishes an operation-level compatibility matrix [3] | [8] [3] |
| Storj | 1 | 1 true [8] | Feature and tool requirements remain separate | [8] |
| Oracle OCI Object Storage | 3 | 3 true [8] | Native retention rules are not proof of S3 Object Lock equivalence | [8] |
| Tigris | 4 | 4 true [8] | Feature and tool requirements remain separate | [8] |
| Filebase | 1 | 1 true [8] | The current matrix omits operations required for an S3 Object Lock target [4] | [8] [4] |
| Telnyx Cloud Storage | 2 | 2 true [8] | Region-specific Object Lock support remains a separate check | [8] |
Compatibility filters the offers; the receipt still decides the cost
Protocol compatibility belongs in the eligibility contract. After the required operations, retention controls, region, and backup-tool workflow are verified, the comparison still needs storage, requests, retrieval, temporary-copy storage, and destination-aware egress. [1] [7]
Compatible providers can expose incompatible egress rules. Backblaze B2 publishes a proportional allowance and overage, R2 removes the internet-egress charge but retains request and class-specific retrieval meters, and Wasabi applies a fair-use policy with no published excess rate. [9] [6] [10]
| Provider | Compatibility state | Recovery-cost boundary | Source ref |
|---|---|---|---|
| Backblaze B2 | true in the captured dataset [8] | Free egress up to 3 times average monthly storage, then $0.01/GB [9] | [8] [9] |
| Cloudflare R2 | true with an operation-specific matrix [8] [1] | Internet egress not charged; Class A and B operations billed; Infrequent Access retrieval $0.01/GB [6] | [8] [1] [6] |
| Wasabi | true in the captured dataset [8] | Inside-policy egress not charged; an excess per-GB price is not published [10] | [8] [10] |
| Read-only restore | Requires read and restore operations supported by the selected endpoint [1] | Early deletion: does not apply unless a separate mutation occurs [7] | [1] [7] |
Sources
Every figure above comes from one of these pages, on the date shown. Each numbered reference in the text links to its entry here. Vendors change prices; if a date looks old, check the source. Three vendors publish a machine-readable feed and the rest are re-checked by hand, which is why the dates are not uniform.
The source ledger10 sources
- 1Cloudflare developer docs: Apidevelopers.cloudflare.com · checked 2026-07-26
- 2DigitalOcean documentation: S3 compatibilitydocs.digitalocean.com · checked 2026-07-26
- 3Vultr documentation: S3 compatibility matrixdocs.vultr.com · checked 2026-07-26
- 4Filebase: Compatibility matrixfilebase.com · checked 2026-07-26
- 5AWS documentation: Object lockdocs.aws.amazon.com · checked 2026-07-26
- 6Cloudflare developer docs: R2 pricingdevelopers.cloudflare.com · checked 2026-07-25T15:34:44Z
- 7Amazon Web Services: S3 pricingaws.amazon.com · checked 2026-07-26
- 8This repository: providers.jsonrepository · checked 2026-07-25T15:34:44Z
- 9Backblaze: Transaction pricingwww.backblaze.com · checked 2026-07-25T15:34:44Z
- 10Wasabi: Faqwasabi.com · checked 2026-07-25T15:34:44Z