Litebackup backs up SQLite databases from your app machines to your own Linode and encrypted object storage. Your app machines can run anywhere.
Create the server
Create a Linode near your app machines. We recommend Debian 13 or Ubuntu 26.04 LTS; Fedora, Rocky Linux, AlmaLinux, openSUSE Leap, and Arch Linux also work. Choose a Shared CPU or Dedicated CPU plan and your SSH key. Select a plan meeting the starting specs below, then install Litebackup with the command below.
Choose a VM size
| Load | Example workload | VM starting point | Disk starting point |
|---|---|---|---|
| Low | A few machines and dozens of lightly written databases | Shared CPU, at least 2 vCPUs / 4 GB | At least 80 GB SSD |
| Medium | Several machines and hundreds of tenant or agent databases | Shared CPU, at least 4 vCPUs / 8 GB | At least 160 GB SSD |
| High | Dozens of machines, thousands of databases, or frequent concurrent syncs | Dedicated CPU, at least 8 vCPUs / 16 GB | At least 320 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.
Use the persistent SSD included with the plan, or a mounted Block Storage volume when you need more space. Akamai Object Storage is an S3-compatible bucket option; S3, R2, Google Cloud Storage, and other compatible stores also work. Check regional transfer charges.
Configure networking
Keep a public IPv4 address assigned. Attach a Cloud Firewall with the inbound rules below, and permit outbound traffic. Check the firewall inside the Linode 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.
Install Litebackup
SSH into the VM as root or a user with sudo access, then run:
curl -fsSL https://litebackup.com/server.sh | bash
The installer asks for sudo when needed and prints a setup link. The Litebackup service starts once you finish browser setup.
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 Linode Marketplace, or compare cloud and Linux installation guides.