Litebackup backs up SQLite databases from your app machines to your own Droplet and encrypted object storage. Your app machines can run anywhere.
Create the server
Create a Debian 13 Droplet on DigitalOcean (referral link). The link selects the Debian 13 x64 image. We recommend Debian 13 or Ubuntu 26.04 LTS; the Fedora, Rocky Linux, and AlmaLinux images also work. Choose a region near your app machines, pick a size, and add your SSH key. After the Droplet starts, install Litebackup over SSH.
Choose a VM size
| Load | Example workload | VM starting point | Disk starting point |
|---|---|---|---|
| Low | A few machines and dozens of lightly written databases | Basic, 2 vCPUs / 4 GiB | 80 GiB SSD |
| Medium | Several machines and hundreds of tenant or agent databases | Basic, 4 vCPUs / 8 GiB | 160 GiB SSD |
| High | Dozens of machines, thousands of databases, or frequent concurrent syncs | Basic, 8 vCPUs / 16 GiB | 320 GiB SSD |
These are starting recommendations, not database or machine limits: size for your active data, concurrent writes, recent history, and room for restores or bucket downtime. Watch CPU, memory, disk, and sync progress after launch, and choose a Litebackup plan covering your databases and machines.
The plans above include SSD storage. Choose a larger disk if your active databases and recent history need it. DigitalOcean Spaces is an option for your backup bucket; you can also use S3, R2, Google Cloud Storage, or another S3-compatible store.
Configure networking
Assign a public IPv4 address. If you attach a DigitalOcean Cloud Firewall, add the inbound rules below and keep its outbound rules enabled. Check any firewall inside the Droplet too.
| Direction | Port | Purpose |
|---|---|---|
| Inbound | TCP 443 | Litebackup clients and the HTTPS console |
| Inbound | TCP 22 | SSH, restricted to your administration address |
| Outbound | HTTPS, DNS, time synchronization | Downloads, registration, bucket access, and a correct clock |
TCP 443 must reach the VM directly. If you enable IPv6, allow the matching traffic there too.
Install Litebackup on the Droplet
Connect over SSH using the public IPv4 address:
ssh root@YOUR_SERVER_IP
On the Droplet, run:
curl -fsSL https://litebackup.com/server.sh | bash
The installer prints a setup link.
Claim the server and connect a bucket
Open the setup link within 24 hours, sign in, and name your server. Connect a bucket you own, save your recovery kit separately, and choose your retention period. Setup supplies your HTTPS address; no custom domain is needed.
Back up your first SQLite database
On the machine that holds your database, open Machines → Add machine in the Litebackup console and follow its install and join commands. Run them as the user that owns your app's databases, or as root for a system service that reaches every database. Then run, as the same user:
litebackup start /var/lib/app/main.sqlite
litebackup status
Use the path to an existing SQLite file. Continuous backup runs in the litebackup background process. Your app keeps using its usual SQLite driver and file, without waiting for uploads. Keep that file on a durable disk or volume.
Check the console for the server and cloud backup versions. For application integration, see the TypeScript and Go SDKs; for a service with no code changes, see the CLI. Practice a restore into a new file.
Provider reference
Install
Create a Debian 13 Droplet (referral link), or compare cloud and Linux installation guides.