The 3-2-1 backup rule and Restic guides covered earlier in this series both pointed toward cloud storage for the genuinely critical off-site backup component, without settling on which specific provider actually makes sense for homelab-scale usage. Comparing cloud backup providers for this specific use case reveals meaningful cost and complexity differences that matter considerably more at homelab scale than at real enterprise scale.
Why Provider Choice Matters More for Homelabs Than It Might Seem
Enterprise cloud storage decisions typically weigh factors like SLA guarantees and enterprise support contracts. For a homelab’s off-site backup needs specifically, the practical decision usually comes down to a much simpler question: cost per terabyte stored and retrieved, and how straightforward the tool (Restic, in the case of the earlier guide) can actually interact with the provider’s API.
AWS S3: The Established Default
Amazon S3 is the original and still most widely integrated cloud storage service, supported natively by essentially every backup tool, including Restic. Its pricing structure, however, includes notable egress fees (charges for downloading data back out) beyond the storage cost itself — a real consideration specifically for backup use cases, since a real restore scenario means downloading everything back, potentially incurring meaningful egress charges exactly when you’re already dealing with a data loss situation.
Best for: users already invested in the broader AWS ecosystem, or needing S3-specific features beyond simple backup storage Watch out for: egress fees during restores, and a pricing structure truly more complex than homelab-scale usage typically needs
Backblaze B2: Homelab-Friendly Pricing
Backblaze B2 has become particularly popular in homelab communities specifically because of its considerably simpler, lower-cost pricing structure — notably lower storage costs than S3, and critically, free egress up to a reasonable multiple of your stored data volume when paired with certain CDN partners, or simply lower egress rates than S3 in general.
Best for: homelab users prioritizing straightforward, low-cost storage specifically for backup purposes, where real restore scenarios (requiring egress) are infrequent but need to remain affordable when they do happen Watch out for: a smaller feature set than AWS’s broader ecosystem, though this is largely irrelevant for pure backup storage use cases
Wasabi: Aggressively Simple Flat-Rate Pricing
Wasabi takes simplicity further, offering flat-rate storage pricing with no separate egress or API request charges at all under normal usage patterns — a single, predictable monthly cost based purely on storage volume, regardless of how often you actually access or restore that data.
Best for: users who specifically want to avoid any surprise charges and prefer completely predictable monthly costs, particularly valuable if you anticipate testing restores periodically (as the 3-2-1 guide recommended) without worrying about egress costs each time Watch out for: a minimum storage duration commitment (typically 90 days) meaning frequently deleted and re-uploaded data doesn’t behave quite as cost-effectively as with pure pay-for-what-you-use providers
Comparing Restic Integration
All three integrate with Restic () through S3-compatible APIs — Backblaze B2 and Wasabi both offer S3-compatible endpoints specifically to ease this kind of tooling compatibility, meaning the actual Restic configuration differences between providers are generally minimal, mostly just different endpoint URLs and credentials.
A Practical Cost Comparison Approach
Rather than relying on general reputation, calculate actual expected costs based on your specific homelab’s real backup volume: your total data size (from the 3-2-1 planning covered earlier), expected restore frequency (hopefully rare, but worth planning for), and how long you intend to retain historical snapshots — plugging these into each provider’s actual current pricing calculator, since pricing details do shift over time.
Encryption Regardless of Provider Choice
Whichever provider you choose, Restic’s client-side encryption () means the provider itself never has access to your actual unencrypted data — a meaningful point when evaluating providers, since it somewhat reduces how much you need to weigh a specific provider’s own security practices, given your data is already encrypted before it ever reaches their infrastructure.
A Practical Recommendation for Homelab Use
For most homelab users specifically backing up a moderate volume of really important data (documents, photos via Immich, configuration backups) with infrequent but real restore testing needs, Backblaze B2 offers the most commonly recommended balance of low cost and straightforward Restic integration within the homelab community specifically. Wasabi is worth strong consideration if cost predictability matters more to you than the absolute lowest possible price. AWS S3 makes most sense if you’re already using AWS for other purposes and want to consolidate billing and management in one place.
Final Thoughts
Comparing cloud backup providers for the specific, narrower use case of homelab off-site backup reveals that the “best” choice depends considerably on real usage patterns — expected restore frequency, retention duration, and existing ecosystem investment — rather than any single provider being universally correct. Combined with Restic’s client-side encryption and straightforward multi-provider support, any of these three actually fulfills the off-site component of the 3-2-1 backup strategy covered earlier in this series.
Leave a Reply