Backblaze

1. What you get with Backblaze
2. How the integration works
3. Good to know

Backblaze B2 charges roughly a fifth of what the big clouds charge for object storage — around $6 per terabyte per month at current list prices — and speaks the S3 API, so anything built for S3 works with B2 unchanged. For backups, that maths is hard to argue with. Connect your Backblaze account and Rocketeers stores your site backups in B2 automatically, so a copy is always waiting when you need one.

#What you get with Backblaze

• S3-compatible object storage, so no proprietary lock-in — your backups stay portable.
• Storage priced at a fraction of AWS S3, which matters when backups accumulate for months.
• Automatic, scheduled site backups shipped to your own B2 buckets by Rocketeers.
• Free egress up to three times your average monthly storage, so restoring backups usually costs nothing.
• Data kept in your own account: your buckets, your retention, your control.

#How the integration works

Create a bucket for backups in your Backblaze account, then generate an application key — ideally one scoped to just that bucket. Add the key ID and application key to Rocketeers, and it takes care of the rest: uploading backups on schedule via the S3-compatible API, organising them per site and pruning old archives according to your retention settings. Restores pull straight from your bucket.

#Good to know

• The first 10 GB of storage is free, which is enough to trial the whole backup pipeline before committing.
• B2 has datacenter regions in the US and Europe; pick the region that matches where your data should live, as buckets don't move between regions afterwards.
• Scoped application keys are the right tool here — a key restricted to one bucket can't touch anything else in your account.
• Egress through Backblaze's CDN and compute partners (including Cloudflare) is free entirely, if you ever serve files directly from B2.