Litestream
Open-source tool that continuously replicates SQLite databases to object storage like S3.
Liked for continuously backing up SQLite to object storage123 with point-in-time recovery from WAL chunks,45 and for pairing well with PocketBase.67 The main caveats are a few seconds of possible downtime depending on WAL flush timing,8 and extra setup complexity that some feel erodes SQLite's advantage over Postgres.9
Why people recommend it
Offsite backups · 3
Commenters use it to stream SQLite backups to object storage and restore from them.
“the pod restores the current litestream backup from object storage. No persistent volumes needed. No issues so far.”
Show 1 more
“a sketchy single VPS node with a server, a SQLite instance, and a LiteStream hookup has a better recovery story”
Proven in use · 3
Users report running it across projects without problems.
“the pod restores the current litestream backup from object storage. No persistent volumes needed. No issues so far.”
Show 1 more
“I love litestream. I've used it with pocketbase and it works.”
Point-in-time recovery · 2
It backs up WAL chunks directly, enabling efficient point-in-time restores.
“Litestream offers point-in-time recovery for SQLite by backing up chunks of WAL directly, which I expect is a lot more efficient than this mechanism.”
PocketBase pairing · 2
Users call SQLite plus Litestream with PocketBase a productive setup.
“sqlite+litestream [1] is fantastic, i highly recommend it.”
“I love litestream. I've used it with pocketbase and it works.”
Transparent design · 1
SQLite works as normal while Litestream operates transparently, in a Unix-like way.
Caveats and dissent
Data-loss window · 1
A few seconds of downtime is possible depending on WAL flush frequency and write burstiness.
Full local copy · 1
The whole database must be on disk on the process doing the reads.
Added complexity · 1
One commenter feels it makes a SQLite setup less simple and less battle-tested than Postgres.
“running it on top of LiteFS or LiteStream seems like starts to make the setup a lot less simple and lot less battle tested”
Often compared with
From the makers not counted in the ranking
“Litestream author here. You can use the built-in file replication.”
Threads where it came up
- SQLite Is All You Need 2 mentions
- Alternatives to MinIO for single-node local S3 1 mention
- Running SQLite Apps on Docker and Kubernetes with Litestream 1 mention
- A zero-dependency, ultra-lightweight database time machine for SQLite 1 mention
- SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers 1 mention
- An AI agent deleted our production database. The agent's confession is below 1 mention
Data: litestream.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 12
“celld's Litestream + locking on S3 approach”
“the pod restores the current litestream backup from object storage. No persistent volumes needed. No issues so far.”
“Litestream offers point-in-time recovery for SQLite by backing up chunks of WAL directly, which I expect is a lot more efficient than this mechanism.”
“running it on top of LiteFS or LiteStream seems like starts to make the setup a lot less simple and lot less battle tested”
“I use Litestream for offsite backups.”
“I use it in several projects.”
“a sketchy single VPS node with a server, a SQLite instance, and a LiteStream hookup has a better recovery story”
“a format like LTX/Litestream uses to provide transaction-aware features like point-in time restore”
“I love litestream. I've used it with pocketbase and it works.”
“sqlite+litestream [1] is fantastic, i highly recommend it.”
“(Litestream replication)”
“I love the unix ethos of Litestream's design.”