What do your database backups really cost to keep?
Most backup scripts upload a full dump every night and keep 30 of them. Deduplication changes that math. Set your numbers below; every rate is editable, and the comparison includes the DIY options.
Your backup setup
Daily backups of one rolling dump file (the standard cron pattern).
Compressed dump on disk (e.g. pg_dump --format=custom)
How much of the data changes between backups
Daily snapshots kept before pruning
Off by default: on raw storage alone, restic + B2 is the cheapest option below. The toggle prices in the pipeline you build and babysit yourself: scheduling, monitoring, prune/check jobs, restore drills.
dump x 30 snapshots, no dedupe
92% less. Only changed chunks are stored
flat tier, storage + dedupe + verification included
Lite · 500 GBMonthly cost, side by side
Storage only. Toggle engineering time above for total cost of ownership.
Assumptions & rates (edit anything)
The model: full-copy cost stores the whole dump every day for the retention window (dump x days). Deduplicated storage stores the first dump in full, then only changed chunks per day (dump + (days - 1) x dump x change rate), the content-addressed approach restic and Backup Data share. Backup Data pricing uses the published tiers: free 5 GB, Lite $12/500 GB, Pro $20/1 TB, Galaxy $49/2.5 TB. Rates are US-region list prices as of mid-2026; request, egress, and restore fees are excluded (they favor no one until you restore; then egress favors leaving S3). Real dedupe ratios depend on your data; run one backup on the free tier and read the actual compressionRatiofrom the SDK's progress events.
Check the math on your real data
The free tier is 5 GB: one pg_dump and one SDK call shows your actual dedupe ratio, no card required.