Backblaze B2

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Do not build this. Storage is a business of buying disks by the rack, and the price here is already below what one server's worth of redundancy costs you.

WHY THIS IS NOT A CLOSE CALL
- **Durability is the product.** A copy on one machine is not storage, it is a file. Real durability means copies across machines and sites, checked continuously, with failing disks replaced by somebody whose job that is
- A NAS in your office is a single point of failure with a fire risk attached

WHERE IT MATTERS MOST
- This is the target for your backups, and it is the cheapest part of the whole arrangement. Every backup script in this catalogue points at something like it

WHAT TO DO PROPERLY
- **Encrypt before upload**, with a key you hold. Then the storage provider is untrusted by design and where the bytes live stops mattering. restic and borg both do this and neither needs writing
- Application keys scoped to one bucket, never the master key, and rotate them
- **Object lock or immutability on the backup bucket.** A compromised server can delete its own backups, and ransomware does exactly that. This is the single most valuable setting here and almost nobody turns it on
- Lifecycle rules to expire old versions, or the bill grows quietly forever
- Watch egress against the free allowance: it is generous, and a restore is the moment you find out you exceeded it

AND THE PART THAT IS NOT THE PROVIDER
- **Restore from it onto a clean machine and write down how long it took.** An untested backup is not a backup, and that number is your actual recovery time. Almost nobody knows theirs
- A verification job that restores a sample and compares hashes, monthly
- An alert on the age of the last successful backup, somewhere you will see it

THE ONE-LINE VERSION
Rent the disks and encrypt before they see anything. Turn on object lock, and go and time a restore.