Skip to content

Litebackup and Turso

Turso is a hosted database built on libSQL, its fork of SQLite. Litebackup works with the official SQLite your app already uses and backs it up to infrastructure you own.

Choose Turso when

  • You want a hosted database

    Turso runs the primary for you and gives every app a URL and a token.

  • Your code runs without a disk

    Serverless functions and edge runtimes can query Turso over the network.

Choose Litebackup when

  • Your data stays on your machines

    Writes stay local and fast; copies go to your server and a bucket in your own account.

  • You want official SQLite

    Your app keeps the SQLite from sqlite.org, with any driver, and your code does not change.

  • You want every version kept

    Restore any version you keep, from your own server or bucket.

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

  • Turso hosts libSQL databases. libSQL is Turso's open-source fork of SQLite, and Turso Database is its ground-up rewrite of SQLite in Rust. Apps connect with a libSQL client, and embedded replicas keep a local read copy that syncs on demand or on an interval, while writes go to the remote primary.

  • Litebackup leaves the database on your machine. Writes are local; each change reaches your own server within seconds and your bucket after that, and readonly replicas stay current on the machines you choose.

Differences that matter

  • Where writes go. Turso sends writes to its primary. With Litebackup they land in the local file.

  • Who runs it. Turso is a managed service. Litebackup runs on your server and stores backups in your bucket.

  • Engine. Turso runs libSQL, its own fork of SQLite. Litebackup works with official SQLite, so the testing behind every SQLite release applies to your database unchanged.

  • Code. Turso uses libSQL clients. Litebackup works with any SQLite driver, and its SDK is optional.