# BackupData.io

> Managed backup as a service for databases, object storage, and files.
> Back up from a CLI or SDK, get immutable point-in-time snapshots with
> client-side AES-256-GCM encryption, content-defined chunking, and global
> deduplication, then restore with checksum verification. Free tier is 5 GB
> with no card required.

BackupData.io is a backup product, not a general file host and not a storage
network. It stores snapshots of data you already have somewhere else, so that
losing the original is survivable.

## Docs

- [Introduction](https://docs.backupdata.io/intro): what the product is and how the pieces fit together
- [Quick start](https://docs.backupdata.io/quick-start): first verified snapshot in about ten minutes
- [Upload and snapshot management](https://docs.backupdata.io/how-to/upload-and-snapshot-management): backup, list, restore, prune
- [Documentation home](https://docs.backupdata.io): full reference

## SDKs

- [JavaScript / Node SDK](https://github.com/Backup-Data-io/js-sdk): npm package `@lighthouse-web3/baas-js-sdk`
- [Go SDK](https://github.com/Backup-Data-io/go-sdk): same surface for Go stacks

## Guides and comparisons

- [Automating backups with GitHub Actions (and when not to)](https://www.backupdata.io/resources/guides/automate-backups-github-actions): Scheduled workflows disable themselves after 60 days of repo inactivity, and anyone with write access can exfiltrate your production credentials. Where CI is the right place for backups, and where cron still wins. (Guide, 7 min)
- [Back up model checkpoints before your spot instance disappears](https://www.backupdata.io/resources/guides/backup-model-checkpoints): GPU hours are money. A checkpoint backup pipeline for training runs, encrypted, deduplicated, off the box, with a restore drill that proves you can resume. (Guide, 6 min)
- [Backing up a Linux server without backing up the whole disk](https://www.backupdata.io/resources/guides/linux-server-backup): Provider snapshots die with the account and a full disk image wastes most of its bytes. What to actually capture on a VPS, what to skip, and how to prove a rebuild works. (Guide, 7 min)
- [Backing up Supabase, Neon and PlanetScale](https://www.backupdata.io/resources/guides/supabase-neon-planetscale-backup): Managed Postgres and MySQL providers give you PITR that lives entirely in their account. If the account goes, so does every recovery option. How to keep an independent copy. (Guide, 6 min)
- [Backup Data vs AWS Backup: which fits your stack?](https://www.backupdata.io/resources/compare/baas-vs-aws-backup): An honest comparison of Backup Data and AWS Backup: portability, encryption models, pricing, restore verification, and when each one is the right call. (Comparison, 7 min)
- [Backup Data vs Backblaze B2: a backup system or a cheap bucket?](https://www.backupdata.io/resources/compare/baas-vs-backblaze): Backblaze B2 is the best-value object storage there is. But a bucket is not a backup system. An honest comparison of where each fits for database and application backups. (Comparison, 8 min)
- [Backup Data vs BorgBackup: who runs the repository?](https://www.backupdata.io/resources/compare/baas-vs-borg): Borg is excellent software with a genuinely strong security model. The real difference isn't dedupe or encryption — both have those. It's who maintains the repo server, and single-writer locking. (Comparison, 7 min)
- [Backup Data vs pgBackRest: physical PITR or portable dumps?](https://www.backupdata.io/resources/compare/baas-vs-pgbackrest): pgBackRest gives you point-in-time recovery to the transaction, which no logical dump can match. It also restores only into the same Postgres major version. An honest comparison. (Comparison, 6 min)
- [Backup Data vs restic: managed service or self-run tool?](https://www.backupdata.io/resources/compare/baas-vs-restic): restic and Backup Data agree on how backups should work: dedupe, snapshots, client-side encryption. The real difference is who runs the system. An honest comparison. (Comparison, 7 min)
- [Backup Data vs rsync: a transfer tool is not a backup system](https://www.backupdata.io/resources/compare/baas-vs-rsync): rsync is the best file-copying tool ever written and it has no versioning, no retention, and no restore verification. An honest comparison, including when rsync is still the right answer. (Comparison, 6 min)
- [Backup requirements for SOC 2, GDPR and HIPAA](https://www.backupdata.io/resources/guides/backup-compliance-gdpr-soc2-hipaa): Auditors don't ask whether you have backups. They ask for evidence you restored one. What each framework expects, and how to handle erasure requests against immutable backups. (Guide, 6 min)
- [Backup vs replication vs snapshot vs archive](https://www.backupdata.io/resources/guides/backup-vs-replication-vs-snapshot-vs-archive): Replication copies your mistakes in milliseconds. A snapshot usually dies with the volume it's on. Four terms that get used interchangeably, and what each one actually protects against. (Guide, 5 min)
- [Docker volume backups you can actually restore](https://www.backupdata.io/resources/guides/docker-volume-backups-you-can-actually-restore): docker commit doesn't save your volumes, and copying /var/lib/docker while a database is running gives you a corrupt file. Build a Docker volume backup pipeline with verified restores. (Guide, 8 min)
- [DynamoDB backups you can actually restore](https://www.backupdata.io/resources/guides/dynamodb-backups-you-can-actually-restore): PITR and on-demand backups live in the account you're protecting against. Build a DynamoDB backup pipeline with off-provider copies, table schema captured, and verified restores. (Guide, 8 min)
- [Elasticsearch and OpenSearch backups you can actually restore](https://www.backupdata.io/resources/guides/elasticsearch-opensearch-backup): You cannot back up Elasticsearch by copying the data directory. The snapshot API is the only supported route, path.repo needs a rolling restart, and restores refuse to overwrite an open index. (Guide, 6 min)
- [Full vs incremental vs differential backup](https://www.backupdata.io/resources/guides/full-vs-incremental-vs-differential-backup): Incremental backs up changes since the last backup. Differential backs up changes since the last full. The difference only matters when you restore — and deduplication makes the whole trade-off obsolete. (Guide, 5 min)
- [How long should you keep backups?](https://www.backupdata.io/resources/guides/backup-retention-policy): Retention shorter than attacker dwell time is retention an attacker can wait out. How to size a policy with grandfather-father-son, what deduplication does to the cost, and how to automate it safely. (Guide, 6 min)
- [How to test your backups (and why checking they ran isn't testing)](https://www.backupdata.io/resources/guides/how-to-test-your-backups): A green cron job proves a script exited zero. A restore drill proves you can recover. How to run one, what to measure, and how to automate it so it happens without you. (Guide, 8 min)
- [Immutable backups: what actually stops ransomware](https://www.backupdata.io/resources/guides/immutable-backups-ransomware-protection): Modern ransomware deletes your backups first, using your own credentials. What immutability really means, which controls survive a compromised admin account, and how to build one. (Guide, 8 min)
- [Kubernetes backups: what actually needs backing up](https://www.backupdata.io/resources/guides/kubernetes-backup): etcd is not your data, and kubectl get all -o yaml is not a manifest backup. What to capture in a Kubernetes cluster, how to capture it consistently, and how to prove it restores. (Guide, 9 min)
- [MongoDB backups you can actually restore](https://www.backupdata.io/resources/guides/mongodb-backups-you-can-actually-restore): Most mongodump cron jobs have never been test-restored. Build a MongoDB backup pipeline with consistent archives, verified restores, encryption, and retention, in about 10 minutes. (Guide, 8 min)
- [MySQL backups you can actually restore](https://www.backupdata.io/resources/guides/mysql-backups-you-can-actually-restore): Most mysqldump cron jobs have never been test-restored. Build a MySQL/MariaDB backup pipeline with consistent dumps, verified restores, encryption, and retention, in about 10 minutes. (Guide, 8 min)
- [Postgres backups you can actually restore](https://www.backupdata.io/resources/guides/postgres-backups-you-can-actually-restore): Most pg_dump cron jobs have never been test-restored. Build a Postgres backup pipeline with verified restores, encryption, and retention, in about 10 minutes. (Guide, 6 min)
- [Redis backups you can actually restore](https://www.backupdata.io/resources/guides/redis-backups-you-can-actually-restore): RDB or AOF is the wrong question — you need to know which one Redis loads on boot. Build a Redis backup pipeline with consistent snapshots, off-box copies, and verified restores. (Guide, 7 min)
- [RPO vs RTO: the two numbers your backup schedule is already choosing for you](https://www.backupdata.io/resources/guides/rpo-vs-rto): RPO is how much data you lose, RTO is how long you're down. Most teams have never measured either — and the gap between the assumed RTO and the real one is where outages get expensive. (Guide, 6 min)
- [S3 versioning is not a backup: how to actually back up a bucket](https://www.backupdata.io/resources/guides/s3-bucket-backup): Versioning, replication, and lifecycle rules all live inside the account that gets compromised. Build a real off-provider S3 backup with verified restores, in about 10 minutes. (Guide, 7 min)
- [SQLite backups you can actually restore](https://www.backupdata.io/resources/guides/sqlite-backups-you-can-actually-restore): cp on a live SQLite database gives you a file that may not open, and in WAL mode it silently drops recent commits. Use .backup or VACUUM INTO, then verify the restore. (Guide, 8 min)
- [The 3-2-1 backup rule, and what it means when everything is cloud](https://www.backupdata.io/resources/guides/3-2-1-backup-rule): Three copies, two media, one off-site — written in 2009 for hard drives. What each number actually protects against, and how to apply it when all three copies live in the same AWS account. (Guide, 6 min)
- [What backup storage actually costs](https://www.backupdata.io/resources/guides/backup-storage-cost): The per-GB price is the smallest line item. Egress, API calls, early-deletion minimums and retrieval fees are where cheap storage stops being cheap — and engineer hours dwarf all of it. (Guide, 5 min)
- [What deduplication actually does in a backup system](https://www.backupdata.io/resources/guides/what-is-deduplication-in-backup): File-level dedupe misses a one-byte change. Fixed-block dedupe breaks the moment you insert data. Content-defined chunking is why 30 nightly database dumps cost barely more than one. (Guide, 6 min)

## Pricing

- Free: $0/mo, 5 GB
- Lite: $12/mo, 500 GB
- Pro: $20/mo, 1024 GB
- Premium: $49/mo, 2560 GB
- BYOS Retention: $10/mo, 0 GB

- [Pricing details](https://www.backupdata.io/#pricing): full feature breakdown per tier

## Optional

- [llms-full.txt](https://www.backupdata.io/llms-full.txt): expanded reference — API surface, concepts, limits, and what this product is not
- [Contact](mailto:mail@backupdata.io): mail@backupdata.io