S3-compatible object storage providers

• On-premises or air-gapped deployments where data cannot leave your control
• Teams that need AWS-grade IAM semantics without AWS
• A local development target that behaves like production S3

The reference point, not a competitor; run it only if you already operate storage hardware.

• Apps already deployed on Fly.io, where the integration is native
• Globally distributed reads without running a CDN yourself
• Zero egress without committing to Cloudflare's ecosystem

The most interesting design: data gravity handled, no egress, Sydney via Fly, but youngest vendor with no SLA.

• Large-object distribution, datasets, model weights, video masters
• Backups where surviving a whole-region failure matters more than latency
• Workloads that benefit from delegatable, expiring, prefix-scoped access grants

The cheapest storage with a different durability model, undercut by first-byte latency the architecture cannot fix.

• Backup and archive targets where object lock matters and latency does not
• Anyone already serving through Cloudflare or Fastly, egress becomes free
• Workloads whose egress genuinely stays under three times stored volume

The sensible cheap, feature-complete middle, but no APAC region rules it out for Australia.

• Public assets, media and package registries where egress dwarfs storage
• Anything already fronted by Cloudflare Workers or the Cloudflare CDN
• Escaping an AWS bill that is mostly bandwidth

The default for read-heavy work, the only provider where egress stops being a line item.

• Media archives and backup vaults with predictable, low read volume
• Australian workloads that need in-country storage at a flat rate
• Teams that want AWS-shaped IAM policies without the AWS bill

Great for large, long-lived objects with low reads; 90-day retention and egress cap punish everything else.

• Backup and MSP workloads where storage volume dominates and reads are rare
• Object-lock immutability at the lowest price on this page
• Teams comfortable verifying terms directly with a vendor before committing

Cheapest storage alongside Storj, object lock included, but egress terms too illegible to price; fine for backups.

• EU data residency obligations with a European legal entity behind them
• Workloads needing real IAM policies rather than scoped access keys
• Multi-AZ durability without hyperscaler pricing

The most feature-complete non-hyperscaler, but 300 ms away; pick it when EU data residency is required.

• Static assets and user uploads served from Sydney with a bundled CDN
• Teams who want one predictable line item instead of five metered ones
• Existing DigitalOcean deployments where traffic stays on the internal network

Buy it for the bundling and Sydney region, not the feature set; no versioning or bucket events.

• Workloads already inside AWS where traffic stays on the internal network
• Regulatory requirements needing Object Lock compliance mode with a real SLA
• Anything depending on IAM condition keys, Access Points or S3 Tables

Still the most capable object store, and thirty-eight times Hetzner's cost here, almost entirely bandwidth.

• Static sites, images and video served to a global audience through Bunny's CDN
• Australian delivery where edge latency matters more than API compatibility
• Replacing a CDN plus origin bucket with a single bill

A CDN origin with storage attached, not an object store; superb Sydney delivery, but no S3 semantics.

• CI artefacts, build caches and cold backups where the bill is the point
• European origins where EUR 1.19/TB egress changes what is economically possible
• Anyone already running Hetzner dedicated or cloud servers

Wins the headline number by a mile but loses on features; great for caches, wrong as a system of record.