Litebackup backs up SQLite databases from your app machines to your own Compute Engine VM and encrypted object storage. Your app machines can run anywhere.
Create the server
In Compute Engine, create a VM near your app machines. We recommend Debian 13 from the debian-cloud project or Ubuntu 26.04 LTS from Canonical; the RHEL, Rocky Linux, and AlmaLinux public images also work. Then select an E2 machine type and an SSD Persistent Disk. Use a standard VM for an always-on server, 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 | e2-standard-2, 2 vCPUs / 8 GB | 80 GB SSD Persistent Disk |
| Medium | Several machines and hundreds of tenant or agent databases | e2-standard-4, 4 vCPUs / 16 GB | 160 GB SSD Persistent Disk |
| High | Dozens of machines, thousands of databases, or frequent concurrent syncs | e2-standard-8, 8 vCPUs / 32 GB | 320 GB SSD Persistent Disk |
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.
Keep the server files on Persistent Disk. Check the disk auto-delete setting before deleting or replacing a VM. Google Cloud Storage in the same region is a natural bucket choice; S3, R2, and S3-compatible storage also work. Disk, external IPv4, bucket, and network charges are separate.
Configure networking
Assign an external IPv4 address; reserve a static address if it should stay the same across stop/start cycles. Allow HTTPS traffic and verify that a VPC firewall rule permits TCP 443 to this VM. Allow SSH from your administration address, or use your existing IAP/OS Login access.
| 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 Google Cloud Marketplace, or compare cloud and Linux installation guides.