Skip to content

Litebackup and Litestream

Litestream streams SQLite changes straight to a bucket. Litebackup sends them to your own server first, which also keeps readonly replicas current and lets another server take over writes.

Choose Litestream when

  • You want the fewest moving parts

    One process on the app machine uploads directly to object storage, with no server to run.

  • You want open source

    Litestream is Apache 2.0 licensed and widely used.

  • Your databases already use WAL

    Litestream requires WAL mode and the connection settings its docs recommend.

Choose Litebackup when

  • Other machines need to read the data

    Readonly replicas on any machine stay within seconds of the writer, with app writes refused.

  • Your app runs on several servers

    One server writes, the others serve reads, and one takes over when the writer goes down.

  • You want your databases left alone

    Litebackup adds no tables and never changes how your database is configured.

  • You run many databases

    One server handles up to a million databases, with a console, people, and retention policies.

Try it on your own databases

Runs on any Linux server you already have.

Built on SQLite itself

SQLite is among the most thoroughly tested software in the world: its project keeps about 590 times as much test code as library code, with 100% branch coverage of its core (How SQLite Is Tested). Litebackup is built so your app keeps all of that.

  • Your app keeps its SQLite. It goes on using the official SQLite it already links, with any driver. Litebackup does not replace the engine, load an extension into your app, or change your file format.

  • Litebackup uses SQLite as released. It runs the unmodified SQLite library from sqlite.org and reads your changes only through features SQLite ships and documents.

  • What comes back is plain SQLite. Every replica and restore is an ordinary SQLite file that opens with any driver, and a restore passes SQLite's own quick_check before it finishes.

How they work

  • Litestream runs beside your app, captures WAL changes, and uploads them as LTX files to a bucket. Restores read the bucket: a snapshot, then the changes after it.

  • Litebackup sends each change to your own server within seconds, and the server archives it, encrypted with your key, to your bucket. Restores and replicas come from the server.

Differences that matter

  • Moving parts. Litestream needs no server. Litebackup needs one, which you install with one command on a Linux machine.

  • Your database. Litestream requires WAL mode and creates a _litestream_lock table in each database. Litebackup works with any journal mode and adds nothing to the file.

  • Replicas. Litestream offers read replicas through its VFS extension. Litebackup keeps ordinary SQLite files current on each replica machine, readable with any driver.

  • Failover. Litestream leaves it to you. With Litebackup, identical servers choose one writer, and a replica takes over when it goes down.

  • Restores. Litebackup checks every restore from end to end, including SQLite's own quick_check, before it finishes. Litestream offers an optional integrity check.

  • Price. Litestream is free and open source. Litebackup's plans are on the pricing page.

Both upload asynchronously, so writes from the last few seconds can be lost along with the machine.