Hiberden's cloud Destination is S3-compatible and provider-open. It talks to object storage through a single S3 backend with a configurable endpoint, so it works with any S3-compatible provider, including:
- Amazon S3
- Backblaze B2
- Cloudflare R2
- Wasabi
- MinIO (self-hosted)
You point Hiberden at your own account by setting the endpoint, region, and bucket. The endpoint field's help text says it plainly: "Leave blank for AWS S3. For B2, Wasabi, or R2, paste the provider's S3 endpoint." It is your storage, your account, and your bill: Hiberden writes to and verifies the cloud copy, but never hosts your data. For the step-by-step setup, see Cloud (S3-compatible).
Your credentials stay local
Your cloud access key and secret are stored in your operating system's secure keyring on your own machine, never in Hiberden's catalog database and never on any Hiberden server. If you want to grant Hiberden the narrowest access that still works, see S3 minimal permissions.
Storage class
The storage class is STANDARD, and it is required. Hiberden reads every cloud copy back from the bucket and re-hashes it immediately after writing it, so the storage class has to serve reads right away. Colder classes such as Glacier are not selectable in the app today. The field's help text in the app: "STANDARD is required, verification reads the stored archive back immediately".
Verified like any other copy
A cloud copy is verified the same way as every other Destination: Hiberden re-reads the object and re-hashes it against the recorded SHA-256. Restoring a single file from a cloud copy is supported (a ranged read of just that file's bytes) for archives whose catalog recorded per-file offsets and hashes. All recent archives do; very old ones may not. See What "Verified" means.