Developer-first Database Backup Storage

A backup that lives on the same server as the database it protects is not a backup. Database backup storage on files.link is the off-site, second-location copy — the one that survives a dropped table, a ransomwared host, or a region going dark. It is built for the unglamorous nightly job: take a dump, compress it, push it somewhere durable, and forget about it until the day you desperately need it.

The whole thing is automatable from cron or CI. A typical pipeline pipes pg_dump into gzip, then runs three REST calls: POST /v1/files/{folderId} (returns { success, urls:[{url,id,...}] }), a PUT of the dump's bytes to the presigned url, and POST /v1/files/confirm-upload with { ids:[...] }. The Authorization header is your raw API key, so it drops cleanly into a backup script without an SDK. A working sketch:

pg_dump $DATABASE_URL | gzip > db-$(date +%F).sql.gz # POST to /v1/files/{folderId}, read .urls[0].url and .urls[0].id curl -T db-$(date +%F).sql.gz "$PRESIGNED_URL" # POST /v1/files/confirm-upload {"ids":["<id>"]}

Retention is where the cold storage tier earns its keep. Keep the last few nights on standard storage for instant restores, and sweep older dumps — the ones you must retain for compliance but will probably never read — into the cold tier at a fraction of the cost, accepting a brief retrieval step and a 90-day minimum retention. Restores pull back over the global CDN with no separate egress fee, so a 3 AM emergency download doesn't generate a surprise line item the way bandwidth-metered object stores can.

Keep dumps private — they contain everything — by storing them as private files and downloading only via short-lived signed URLs minted at restore time. Everything is encrypted at rest and in transit. Pair this with kubernetes-backup-storage for cluster state, terraform-state-storage for infra, and log-file-storage for the audit trail; see no-egress-fees-storage and s3-alternative for the cost comparison that usually drives teams here. Billing is prepaid credits, so a growing backup history stays a predictable line on your budget.