{"slug": "litestream", "name": "Litestream", "category": "databases", "category_name": "Databases", "description": "Open-source tool that continuously replicates SQLite databases to object storage like S3.", "recommenders": 8, "commenters": 12, "warners": 1, "score": 7.021, "rising": 0.04, "first": "2025-12-11", "latest": "2026-09-15", "why": "Liked for continuously backing up SQLite to object storage with point-in-time recovery from WAL chunks, and for pairing well with PocketBase.", "why_is_quote": false, "has_verdict": true, "sentiment": {"recommend": 8, "neutral": 3, "compare": 0, "warn": 1}, "spark": [0, 1, 1, 1, 0, 1, 0, 0, 2, 2, 0, 0], "listed": true, "loved": ["Offsite backups", "Proven in use"], "caveat": "Data-loss window", "short_quote": "I love litestream. I've used it with pocketbase and it works.", "icon": true, "domain": null, "github_repo": "github.com/benbjohnson/litestream", "official_url": "https://litestream.io", "pricing": "open source", "aliases": ["Litestream"], "verdict": [{"text": "Liked for continuously backing up SQLite to object storage", "cites": [{"id": 783146368, "item_id": 48946648, "url": "https://news.ycombinator.com/item?id=48946648", "by": "discordance", "date": "2026-07-17", "stance": "recommend", "quote": "I use Litestream for offsite backups.", "excerpt": "Good call. I use Litestream for offsite backups. SQLite also has a .backup command: sqlite3 /path/to/db '.backup /path/to/backup' or sqlite3 /path/to/db \"VACUUM INTO '/path/to/backup'\"", "context": "", "use_case": "offsite SQLite backups", "switched_from": "", "story": "SQLite Is All You Need"}, {"id": 792026897, "item_id": 49501681, "url": "https://news.ycombinator.com/item?id=49501681", "by": "sighansen", "date": "2026-08-30", "stance": "recommend", "quote": "the pod restores the current litestream backup from object storage. No persistent volumes needed. No issues so far.", "excerpt": "I use the same stack to run my apps! sqlite as Database backen on ephemeral pods. On initialisation, the pod restores the current litestream backup from object storage. No persistent volumes needed. No issues so far.", "context": "", "use_case": "SQLite backup/restore", "switched_from": "", "story": "Running SQLite Apps on Docker and Kubernetes with Litestream"}, {"id": 766681794, "item_id": 47917612, "url": "https://news.ycombinator.com/item?id=47917612", "by": "h14h", "date": "2026-04-26", "stance": "recommend", "quote": "a sketchy single VPS node with a server, a SQLite instance, and a LiteStream hookup has a better recovery story", "excerpt": "Been meaning to check out Railway for a while, but now feeling happy about dragging my feet. As flashy as their DX seems to be, the fact that a sketchy single VPS node with a server, a SQLite instance, and a LiteStream hookup has a better recovery story really makes me not trust their platform.", "context": "", "use_case": "SQLite replication and backup", "switched_from": "", "story": "An AI agent deleted our production database. The agent's confession is below"}]}, {"text": " with point-in-time recovery from WAL chunks,", "cites": [{"id": 787756528, "item_id": 49234783, "url": "https://news.ycombinator.com/item?id=49234783", "by": "simonw", "date": "2026-08-09", "stance": "recommend", "quote": "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.", "excerpt": "https://github.com/nsrht/time-travel-sqlite-debugger/blob/main/watcher.php works by checking the mtime on the database file (and -wal file) once per second and creating a backups/unixtime_database.sqlite file if anything has changed, then keeps the last 50 copies. So OK for smaller database files but not great if you're pushing into a GB+ of data. I'm not convinced by the way it copies the files - I think using a \"va", "context": "", "use_case": "SQLite point-in-time recovery", "switched_from": "", "story": "A zero-dependency, ultra-lightweight database time machine for SQLite"}, {"id": 739775280, "item_id": 46235955, "url": "https://news.ycombinator.com/item?id=46235955", "by": "bencornia", "date": "2025-12-11", "stance": "recommend", "quote": "I love the unix ethos of Litestream's design.", "excerpt": "> What we\u2019re doing here is instantaneous point-in-time recovery (PITR), expressed simply in SQL and SQLite pragmas. > Ever wanted to do a quick query against a prod dataset, but didn\u2019t want to shell into a prod server and fumble with the sqlite3 terminal command like a hacker in an 80s movie? Or needed to do a quick sanity check against yesterday\u2019s data, but without doing a full database restore? Litestream VFS makes", "context": "", "use_case": "SQLite replication and recovery", "switched_from": "", "story": "Litestream VFS"}]}, {"text": " and for pairing well with PocketBase.", "cites": [{"id": 750282976, "item_id": 46892686, "url": "https://news.ycombinator.com/item?id=46892686", "by": "xrd", "date": "2026-02-04", "stance": "recommend", "quote": "I love litestream. I've used it with pocketbase and it works.", "excerpt": "I love litestream. I've used it with pocketbase and it works. sqlite is a great building block for almost everything. Does anyone know whether you could use this to stitch together a bunch of .db files (that share the same schema) in an ad-hoc way? For example, if I decided I wanted to synchronize my friend's .db file, could I enable this using litestream? And, what if my friend wanted to sync two of his friends' .db", "context": "", "use_case": "SQLite replication", "switched_from": "", "story": "Litestream Writable VFS"}, {"id": 747918224, "item_id": 46744889, "url": "https://news.ycombinator.com/item?id=46744889", "by": "dtkav", "date": "2026-01-24", "stance": "recommend", "quote": "sqlite+litestream [1] is fantastic, i highly recommend it.", "excerpt": "sqlite+litestream [1] is fantastic, i highly recommend it. I use it with pocketbase and it is a delightful and very productive setup. This guide [2] is for an older version of pocketbase and litestream, but i can update it if would be helpful/interesting for anyone. [1] https://github.com/benbjohnson/litestream/ [2] https://notes.danielgk.com/Pocketbase/Pocketbase+on+Fly.io", "context": "", "use_case": "SQLite backups and replication", "switched_from": "", "story": "Many Small Queries Are Efficient in SQLite"}]}, {"text": " The main caveats are a few seconds of possible downtime depending on WAL flush timing,", "cites": [{"id": 783138144, "item_id": 48946134, "url": "https://news.ycombinator.com/item?id=48946134", "by": "ndr", "date": "2026-07-17", "stance": "recommend", "quote": "I use it in several projects.", "excerpt": "I use it in several projects. You're still open to a few seconds of possible downtime (depending how often you flush the WAL to your remote location, and how bursty your writes are), and you need to have all of your db on disk on the process doing the reads, but it's been great.", "context": "", "use_case": "SQLite replication", "switched_from": "", "story": "SQLite Is All You Need"}]}, {"text": " and extra setup complexity that some feel erodes SQLite's advantage over Postgres.", "cites": [{"id": 785531858, "item_id": 49095741, "url": "https://news.ycombinator.com/item?id=49095741", "by": "mikeocool", "date": "2026-07-29", "stance": "warn", "quote": "running it on top of LiteFS or LiteStream seems like starts to make the setup a lot less simple and lot less battle tested", "excerpt": "I love SQLite, and I really want to run it in production, but my clients expect minimal data loss and downtime when one of my servers goes down. The answer to that being running it on top of LiteFS or LiteStream seems like starts to make the setup a lot less simple and lot less battle tested, which kind of starts to negate the advantages over just running Postgres.", "context": "has clients expecting minimal data loss and downtime", "use_case": "SQLite replication", "switched_from": "", "story": "SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers"}]}], "praise": [{"label": "Offsite backups", "summary": "Commenters use it to stream SQLite backups to object storage and restore from them.", "quotes": [{"id": 783146368, "item_id": 48946648, "url": "https://news.ycombinator.com/item?id=48946648", "by": "discordance", "date": "2026-07-17", "stance": "recommend", "quote": "I use Litestream for offsite backups.", "excerpt": "Good call. I use Litestream for offsite backups. SQLite also has a .backup command: sqlite3 /path/to/db '.backup /path/to/backup' or sqlite3 /path/to/db \"VACUUM INTO '/path/to/backup'\"", "context": "", "use_case": "offsite SQLite backups", "switched_from": "", "story": "SQLite Is All You Need"}, {"id": 792026897, "item_id": 49501681, "url": "https://news.ycombinator.com/item?id=49501681", "by": "sighansen", "date": "2026-08-30", "stance": "recommend", "quote": "the pod restores the current litestream backup from object storage. No persistent volumes needed. No issues so far.", "excerpt": "I use the same stack to run my apps! sqlite as Database backen on ephemeral pods. On initialisation, the pod restores the current litestream backup from object storage. No persistent volumes needed. No issues so far.", "context": "", "use_case": "SQLite backup/restore", "switched_from": "", "story": "Running SQLite Apps on Docker and Kubernetes with Litestream"}, {"id": 766681794, "item_id": 47917612, "url": "https://news.ycombinator.com/item?id=47917612", "by": "h14h", "date": "2026-04-26", "stance": "recommend", "quote": "a sketchy single VPS node with a server, a SQLite instance, and a LiteStream hookup has a better recovery story", "excerpt": "Been meaning to check out Railway for a while, but now feeling happy about dragging my feet. As flashy as their DX seems to be, the fact that a sketchy single VPS node with a server, a SQLite instance, and a LiteStream hookup has a better recovery story really makes me not trust their platform.", "context": "", "use_case": "SQLite replication and backup", "switched_from": "", "story": "An AI agent deleted our production database. The agent's confession is below"}]}, {"label": "Proven in use", "summary": "Users report running it across projects without problems.", "quotes": [{"id": 792026897, "item_id": 49501681, "url": "https://news.ycombinator.com/item?id=49501681", "by": "sighansen", "date": "2026-08-30", "stance": "recommend", "quote": "the pod restores the current litestream backup from object storage. No persistent volumes needed. No issues so far.", "excerpt": "I use the same stack to run my apps! sqlite as Database backen on ephemeral pods. On initialisation, the pod restores the current litestream backup from object storage. No persistent volumes needed. No issues so far.", "context": "", "use_case": "SQLite backup/restore", "switched_from": "", "story": "Running SQLite Apps on Docker and Kubernetes with Litestream"}, {"id": 783138144, "item_id": 48946134, "url": "https://news.ycombinator.com/item?id=48946134", "by": "ndr", "date": "2026-07-17", "stance": "recommend", "quote": "I use it in several projects.", "excerpt": "I use it in several projects. You're still open to a few seconds of possible downtime (depending how often you flush the WAL to your remote location, and how bursty your writes are), and you need to have all of your db on disk on the process doing the reads, but it's been great.", "context": "", "use_case": "SQLite replication", "switched_from": "", "story": "SQLite Is All You Need"}, {"id": 750282976, "item_id": 46892686, "url": "https://news.ycombinator.com/item?id=46892686", "by": "xrd", "date": "2026-02-04", "stance": "recommend", "quote": "I love litestream. I've used it with pocketbase and it works.", "excerpt": "I love litestream. I've used it with pocketbase and it works. sqlite is a great building block for almost everything. Does anyone know whether you could use this to stitch together a bunch of .db files (that share the same schema) in an ad-hoc way? For example, if I decided I wanted to synchronize my friend's .db file, could I enable this using litestream? And, what if my friend wanted to sync two of his friends' .db", "context": "", "use_case": "SQLite replication", "switched_from": "", "story": "Litestream Writable VFS"}]}, {"label": "Point-in-time recovery", "summary": "It backs up WAL chunks directly, enabling efficient point-in-time restores.", "quotes": [{"id": 787756528, "item_id": 49234783, "url": "https://news.ycombinator.com/item?id=49234783", "by": "simonw", "date": "2026-08-09", "stance": "recommend", "quote": "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.", "excerpt": "https://github.com/nsrht/time-travel-sqlite-debugger/blob/main/watcher.php works by checking the mtime on the database file (and -wal file) once per second and creating a backups/unixtime_database.sqlite file if anything has changed, then keeps the last 50 copies. So OK for smaller database files but not great if you're pushing into a GB+ of data. I'm not convinced by the way it copies the files - I think using a \"va", "context": "", "use_case": "SQLite point-in-time recovery", "switched_from": "", "story": "A zero-dependency, ultra-lightweight database time machine for SQLite"}, {"id": 739775280, "item_id": 46235955, "url": "https://news.ycombinator.com/item?id=46235955", "by": "bencornia", "date": "2025-12-11", "stance": "recommend", "quote": "I love the unix ethos of Litestream's design.", "excerpt": "> What we\u2019re doing here is instantaneous point-in-time recovery (PITR), expressed simply in SQL and SQLite pragmas. > Ever wanted to do a quick query against a prod dataset, but didn\u2019t want to shell into a prod server and fumble with the sqlite3 terminal command like a hacker in an 80s movie? Or needed to do a quick sanity check against yesterday\u2019s data, but without doing a full database restore? Litestream VFS makes", "context": "", "use_case": "SQLite replication and recovery", "switched_from": "", "story": "Litestream VFS"}]}, {"label": "PocketBase pairing", "summary": "Users call SQLite plus Litestream with PocketBase a productive setup.", "quotes": [{"id": 747918224, "item_id": 46744889, "url": "https://news.ycombinator.com/item?id=46744889", "by": "dtkav", "date": "2026-01-24", "stance": "recommend", "quote": "sqlite+litestream [1] is fantastic, i highly recommend it.", "excerpt": "sqlite+litestream [1] is fantastic, i highly recommend it. I use it with pocketbase and it is a delightful and very productive setup. This guide [2] is for an older version of pocketbase and litestream, but i can update it if would be helpful/interesting for anyone. [1] https://github.com/benbjohnson/litestream/ [2] https://notes.danielgk.com/Pocketbase/Pocketbase+on+Fly.io", "context": "", "use_case": "SQLite backups and replication", "switched_from": "", "story": "Many Small Queries Are Efficient in SQLite"}, {"id": 750282976, "item_id": 46892686, "url": "https://news.ycombinator.com/item?id=46892686", "by": "xrd", "date": "2026-02-04", "stance": "recommend", "quote": "I love litestream. I've used it with pocketbase and it works.", "excerpt": "I love litestream. I've used it with pocketbase and it works. sqlite is a great building block for almost everything. Does anyone know whether you could use this to stitch together a bunch of .db files (that share the same schema) in an ad-hoc way? For example, if I decided I wanted to synchronize my friend's .db file, could I enable this using litestream? And, what if my friend wanted to sync two of his friends' .db", "context": "", "use_case": "SQLite replication", "switched_from": "", "story": "Litestream Writable VFS"}]}, {"label": "Transparent design", "summary": "SQLite works as normal while Litestream operates transparently, in a Unix-like way.", "quotes": [{"id": 739775280, "item_id": 46235955, "url": "https://news.ycombinator.com/item?id=46235955", "by": "bencornia", "date": "2025-12-11", "stance": "recommend", "quote": "I love the unix ethos of Litestream's design.", "excerpt": "> What we\u2019re doing here is instantaneous point-in-time recovery (PITR), expressed simply in SQL and SQLite pragmas. > Ever wanted to do a quick query against a prod dataset, but didn\u2019t want to shell into a prod server and fumble with the sqlite3 terminal command like a hacker in an 80s movie? Or needed to do a quick sanity check against yesterday\u2019s data, but without doing a full database restore? Litestream VFS makes", "context": "", "use_case": "SQLite replication and recovery", "switched_from": "", "story": "Litestream VFS"}]}], "caveats": [{"label": "Data-loss window", "summary": "A few seconds of downtime is possible depending on WAL flush frequency and write burstiness.", "quotes": [{"id": 783138144, "item_id": 48946134, "url": "https://news.ycombinator.com/item?id=48946134", "by": "ndr", "date": "2026-07-17", "stance": "recommend", "quote": "I use it in several projects.", "excerpt": "I use it in several projects. You're still open to a few seconds of possible downtime (depending how often you flush the WAL to your remote location, and how bursty your writes are), and you need to have all of your db on disk on the process doing the reads, but it's been great.", "context": "", "use_case": "SQLite replication", "switched_from": "", "story": "SQLite Is All You Need"}]}, {"label": "Full local copy", "summary": "The whole database must be on disk on the process doing the reads.", "quotes": [{"id": 783138144, "item_id": 48946134, "url": "https://news.ycombinator.com/item?id=48946134", "by": "ndr", "date": "2026-07-17", "stance": "recommend", "quote": "I use it in several projects.", "excerpt": "I use it in several projects. You're still open to a few seconds of possible downtime (depending how often you flush the WAL to your remote location, and how bursty your writes are), and you need to have all of your db on disk on the process doing the reads, but it's been great.", "context": "", "use_case": "SQLite replication", "switched_from": "", "story": "SQLite Is All You Need"}]}, {"label": "Added complexity", "summary": "One commenter feels it makes a SQLite setup less simple and less battle-tested than Postgres.", "quotes": [{"id": 785531858, "item_id": 49095741, "url": "https://news.ycombinator.com/item?id=49095741", "by": "mikeocool", "date": "2026-07-29", "stance": "warn", "quote": "running it on top of LiteFS or LiteStream seems like starts to make the setup a lot less simple and lot less battle tested", "excerpt": "I love SQLite, and I really want to run it in production, but my clients expect minimal data loss and downtime when one of my servers goes down. The answer to that being running it on top of LiteFS or LiteStream seems like starts to make the setup a lot less simple and lot less battle tested, which kind of starts to negate the advantages over just running Postgres.", "context": "has clients expecting minimal data loss and downtime", "use_case": "SQLite replication", "switched_from": "", "story": "SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers"}]}], "who": [], "tags": ["for SQLite apps", "for PocketBase users", "for ephemeral containers", "for single-VPS deployments"], "use_cases": ["sqlite replication", "database replication to s3", "sqlite backup/restore", "sqlite point-in-time recovery", "offsite sqlite backups", "sqlite replication and backup"], "compared": [{"slug": "sqlite", "name": "SQLite", "co": 7, "switched_from": 0, "switched_to": 0}, {"slug": "pocketbase", "name": "PocketBase", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [{"id": 750296928, "item_id": 46893558, "url": "https://news.ycombinator.com/item?id=46893558", "by": "benbjohnson", "date": "2026-02-04", "stance": "recommend", "quote": "Litestream author here. You can use the built-in file replication.", "excerpt": "Litestream author here. You can use the built-in file replication. It'll replicate all your database changes to another path on disk. I use it a lot for testing things out: https://litestream.io/guides/file/", "context": "Litestream author", "use_case": "SQLite replication", "switched_from": "", "story": "Litestream Writable VFS"}], "threads": [{"url": "https://news.ycombinator.com/item?id=48905491", "title": "SQLite Is All You Need", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49709381", "title": "Alternatives to MinIO for single-node local S3", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49501147", "title": "Running SQLite Apps on Docker and Kubernetes with Litestream", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49234506", "title": "A zero-dependency, ultra-lightweight database time machine for SQLite", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49094346", "title": "SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47911524", "title": "An AI agent deleted our production database. The agent's confession is below", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {"recommend": 1, "neutral": 1}, "2026-01": {"recommend": 1}, "2026-02": {"recommend": 1}, "2026-03": {"neutral": 1}, "2026-04": {"recommend": 1}, "2026-05": {}, "2026-06": {}, "2026-07": {"recommend": 2, "warn": 1}, "2026-08": {"recommend": 2}, "2026-09": {"neutral": 1}, "2026-10": {}}, "quotes": [{"id": 795438881, "item_id": 49714930, "url": "https://news.ycombinator.com/item?id=49714930", "by": "hedgehog", "date": "2026-09-15", "stance": "neutral", "quote": "celld's Litestream + locking on S3 approach", "excerpt": "Does anyone here have experience using some of the newer S3 family API features like locking with any of the self-hostable options? After reading about celld's Litestream + locking on S3 approach (https://github.com/denoland/celld) I got curious about that style of deployment as a way to consolidate small tools so their state is just centralize S3 buckets, but from a bit of reading support for the features like locki", "context": "", "use_case": "database replication to S3", "switched_from": "", "story": "Alternatives to MinIO for single-node local S3"}, {"id": 792026897, "item_id": 49501681, "url": "https://news.ycombinator.com/item?id=49501681", "by": "sighansen", "date": "2026-08-30", "stance": "recommend", "quote": "the pod restores the current litestream backup from object storage. No persistent volumes needed. No issues so far.", "excerpt": "I use the same stack to run my apps! sqlite as Database backen on ephemeral pods. On initialisation, the pod restores the current litestream backup from object storage. No persistent volumes needed. No issues so far.", "context": "", "use_case": "SQLite backup/restore", "switched_from": "", "story": "Running SQLite Apps on Docker and Kubernetes with Litestream"}, {"id": 787756528, "item_id": 49234783, "url": "https://news.ycombinator.com/item?id=49234783", "by": "simonw", "date": "2026-08-09", "stance": "recommend", "quote": "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.", "excerpt": "https://github.com/nsrht/time-travel-sqlite-debugger/blob/main/watcher.php works by checking the mtime on the database file (and -wal file) once per second and creating a backups/unixtime_database.sqlite file if anything has changed, then keeps the last 50 copies. So OK for smaller database files but not great if you're pushing into a GB+ of data. I'm not convinced by the way it copies the files - I think using a \"va", "context": "", "use_case": "SQLite point-in-time recovery", "switched_from": "", "story": "A zero-dependency, ultra-lightweight database time machine for SQLite"}, {"id": 785531858, "item_id": 49095741, "url": "https://news.ycombinator.com/item?id=49095741", "by": "mikeocool", "date": "2026-07-29", "stance": "warn", "quote": "running it on top of LiteFS or LiteStream seems like starts to make the setup a lot less simple and lot less battle tested", "excerpt": "I love SQLite, and I really want to run it in production, but my clients expect minimal data loss and downtime when one of my servers goes down. The answer to that being running it on top of LiteFS or LiteStream seems like starts to make the setup a lot less simple and lot less battle tested, which kind of starts to negate the advantages over just running Postgres.", "context": "has clients expecting minimal data loss and downtime", "use_case": "SQLite replication", "switched_from": "", "story": "SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers"}, {"id": 783146368, "item_id": 48946648, "url": "https://news.ycombinator.com/item?id=48946648", "by": "discordance", "date": "2026-07-17", "stance": "recommend", "quote": "I use Litestream for offsite backups.", "excerpt": "Good call. I use Litestream for offsite backups. SQLite also has a .backup command: sqlite3 /path/to/db '.backup /path/to/backup' or sqlite3 /path/to/db \"VACUUM INTO '/path/to/backup'\"", "context": "", "use_case": "offsite SQLite backups", "switched_from": "", "story": "SQLite Is All You Need"}, {"id": 783138144, "item_id": 48946134, "url": "https://news.ycombinator.com/item?id=48946134", "by": "ndr", "date": "2026-07-17", "stance": "recommend", "quote": "I use it in several projects.", "excerpt": "I use it in several projects. You're still open to a few seconds of possible downtime (depending how often you flush the WAL to your remote location, and how bursty your writes are), and you need to have all of your db on disk on the process doing the reads, but it's been great.", "context": "", "use_case": "SQLite replication", "switched_from": "", "story": "SQLite Is All You Need"}, {"id": 766681794, "item_id": 47917612, "url": "https://news.ycombinator.com/item?id=47917612", "by": "h14h", "date": "2026-04-26", "stance": "recommend", "quote": "a sketchy single VPS node with a server, a SQLite instance, and a LiteStream hookup has a better recovery story", "excerpt": "Been meaning to check out Railway for a while, but now feeling happy about dragging my feet. As flashy as their DX seems to be, the fact that a sketchy single VPS node with a server, a SQLite instance, and a LiteStream hookup has a better recovery story really makes me not trust their platform.", "context": "", "use_case": "SQLite replication and backup", "switched_from": "", "story": "An AI agent deleted our production database. The agent's confession is below"}, {"id": 760633282, "item_id": 47539580, "url": "https://news.ycombinator.com/item?id=47539580", "by": "wgjordan", "date": "2026-03-26", "stance": "neutral", "quote": "a format like LTX/Litestream uses to provide transaction-aware features like point-in time restore", "excerpt": "Nice set of experiments! I appreciate that you're running benchmarks on real object storage setups to validate rapid design variations. (Meta-note: I love how agents have recently made this kind of experimental-research work possible with much less human time investment.) I've been doing some experiments of my own in a relatively similar space, also focusing on S3/Tigris-backed SQLite on ephemeral compute, also with ", "context": "", "use_case": "SQLite replication", "switched_from": "", "story": "Show HN: Turbolite \u2013 a SQLite VFS serving sub-250ms cold JOIN queries from S3"}, {"id": 750282976, "item_id": 46892686, "url": "https://news.ycombinator.com/item?id=46892686", "by": "xrd", "date": "2026-02-04", "stance": "recommend", "quote": "I love litestream. I've used it with pocketbase and it works.", "excerpt": "I love litestream. I've used it with pocketbase and it works. sqlite is a great building block for almost everything. Does anyone know whether you could use this to stitch together a bunch of .db files (that share the same schema) in an ad-hoc way? For example, if I decided I wanted to synchronize my friend's .db file, could I enable this using litestream? And, what if my friend wanted to sync two of his friends' .db", "context": "", "use_case": "SQLite replication", "switched_from": "", "story": "Litestream Writable VFS"}, {"id": 747918224, "item_id": 46744889, "url": "https://news.ycombinator.com/item?id=46744889", "by": "dtkav", "date": "2026-01-24", "stance": "recommend", "quote": "sqlite+litestream [1] is fantastic, i highly recommend it.", "excerpt": "sqlite+litestream [1] is fantastic, i highly recommend it. I use it with pocketbase and it is a delightful and very productive setup. This guide [2] is for an older version of pocketbase and litestream, but i can update it if would be helpful/interesting for anyone. [1] https://github.com/benbjohnson/litestream/ [2] https://notes.danielgk.com/Pocketbase/Pocketbase+on+Fly.io", "context": "", "use_case": "SQLite backups and replication", "switched_from": "", "story": "Many Small Queries Are Efficient in SQLite"}, {"id": 742256626, "item_id": 46391039, "url": "https://news.ycombinator.com/item?id=46391039", "by": "Horos", "date": "2025-12-26", "stance": "neutral", "quote": "(Litestream replication)", "excerpt": "Thanks for the pointer to asyncmachine! Let me clarify HOROS architecture since there's some confusion. HOROS uses time slots for orchestrator clones on a SINGLE machine by default. Not distributed - 5 Go processes share the same kernel clock: Runner-0: T=0s, 10s, 20s... (slot 0) Runner-1: T=2s, 12s, 22s... (slot 1) Runner-2: T=4s, 14s, 24s... (slot 2) Zero network, zero clock drift. Just local time.Sleep(). Your app", "context": "", "use_case": "SQLite replication", "switched_from": "", "story": "Orchestrating 5000 Workers Without Distributed Locks: Rediscovering TDMA"}, {"id": 739775280, "item_id": 46235955, "url": "https://news.ycombinator.com/item?id=46235955", "by": "bencornia", "date": "2025-12-11", "stance": "recommend", "quote": "I love the unix ethos of Litestream's design.", "excerpt": "> What we\u2019re doing here is instantaneous point-in-time recovery (PITR), expressed simply in SQL and SQLite pragmas. > Ever wanted to do a quick query against a prod dataset, but didn\u2019t want to shell into a prod server and fumble with the sqlite3 terminal command like a hacker in an 80s movie? Or needed to do a quick sanity check against yesterday\u2019s data, but without doing a full database restore? Litestream VFS makes", "context": "", "use_case": "SQLite replication and recovery", "switched_from": "", "story": "Litestream VFS"}]}