Already have a bucket? Bring it.
ArchiveBridge works with any S3-compatible bucket — Wasabi and Backblaze B2 are the ones we see most. Ten minutes of setup, no storage minimum, and storage billing stays directly between you and your provider.
1. Create a bucket
Sign up with Wasabi (Sydney region: s3.ap-southeast-2.wasabisys.com) or Backblaze B2 — both are S3-compatible with no egress fees on the plans that matter. Create one bucket per organisation, e.g. acme-archivebridge. Total time: about four minutes.
2. Create an access key
In your provider's console, create an access key + secret scoped to that bucket (both providers support per-bucket keys). This is the only credential ArchiveBridge needs — it never sees your provider login.
3. Paste it into ArchiveBridge
In the console's storage settings, enter endpoint, region, bucket and the key pair. ArchiveBridge tests the connection before saving, and your first protection run queues automatically.
The honest trade-offs.
No storage minimum
Our managed storage bills a 1 TB minimum (that's how we buy it). Your own bucket bills whatever your provider charges for actual use — ideal when a client has 200 GB of cold data, not two terabytes.
Storage billing stays yours
You pay your provider directly at their published rates; we never mark up or resell your storage. ArchiveBridge bills management only — A$29/TB/month, metered daily.
The escape hatch is literal
Copies sit in your bucket, under your keys, in standard S3 object format. Every claim on our security page about restoring without us applies doubly when the bucket is yours.
One trade-off to know
Immutable (object-lock) backups currently require our managed storage, which is provisioned lock-capable from birth. BYO buckets can be swapped for managed storage later if ransomware-proof copies become a requirement.
Start with the number.
The free scan works the same whichever storage you choose — see your reclaimable GB first, pick a bucket second.
Weighing it against Microsoft’s built-in tier? Microsoft 365 Archive vs third-party archiving →