Litebackup backs up SQLite databases from your app machines to your own Cloud Compute instance and encrypted object storage. Your app machines can run anywhere.
Create the server
In Vultr, deploy a Cloud Compute instance near your app machines. Under Marketplace Apps, select Litebackup, choose an x64 plan, and add your SSH key. The Litebackup image uses Debian 13 and starts setup on first boot.
If the listing is not available, choose an operating system and use the manual install below. We recommend Debian 13 or Ubuntu 26.04 LTS; Fedora, Rocky Linux, AlmaLinux, and Arch Linux also work. You can browse the Vultr Marketplace from your account.
Choose a VM size
| Load | Example workload | VM starting point | Disk starting point |
|---|---|---|---|
| Low | A few machines and dozens of lightly written databases | Cloud Compute, 2 vCPUs / 4 GB | 80 GB SSD |
| Medium | Several machines and hundreds of tenant or agent databases | Cloud Compute, 4 vCPUs / 8 GB | 160 GB SSD |
| High | Dozens of machines, thousands of databases, or frequent concurrent syncs | Cloud Compute, 8 vCPUs / 32 GB | 640 GB 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 examples use Regular Performance plans with included SSD storage. High Performance plans with NVMe storage are another option for sustained disk activity. Use a bucket you own on S3, R2, Google Cloud Storage, or an S3-compatible service.
Configure networking
Choose a plan with a public IPv4 address. Create a Vultr Firewall group, add the inbound rules below, and attach it to this instance. A group must have rules and be attached to filter traffic; check the instance firewall as well.
| 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.
Open the setup link
Connect over SSH using the public IPv4 address:
ssh root@YOUR_SERVER_IP
The Marketplace image runs setup on first boot. Your SSH login displays a setup link when registration finishes. If it is still running, wait a moment and check:
sudo litebackup-marketplace-status
Manual install on a plain VM
If you created a plain VM instead of the Litebackup image, run:
curl -fsSL https://litebackup.com/server.sh | bash
The installer asks for sudo when needed and prints the same 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
Open Vultr, or compare cloud and Linux installation guides.