superfly/litefs resource
FUSE-based file system for replicating SQLite databases across a cluster of machines observed · 2026-08-28
Health v2 · maintenance only
70/100
- Activity 81
- Release rhythm 40
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 0.0
- age_days: 1595
- days_rel: 498
- days_push: 114
- n_releases_24m: 3
Adoption not part of the score
4868 stars · 127 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
LiteFS is a FUSE-based passthrough file system that replicates SQLite databases across a cluster of machines by intercepting writes and recording per-transaction changes in LTX files. It is written in Go, actively maintained by Fly.io, and currently in a beta state.
Use cases
- replicate sqlite databases across multiple servers
- run a read-replica fleet for a sqlite-backed app
- distribute a local sqlite database to a cluster of machines
- add high availability to sqlite without switching to postgres
- stream sqlite transaction changes to follower nodes
When to choose
- you want sqlite replication with minimal application changes
- you run many read replicas with a single primary write node
- you deploy on fly.io or similar multi-machine environments
When to avoid
- you need multi-node write support or full SQL replication semantics
- you require production-grade stability today since it is beta
- your workload depends on database deletion, which is not yet implemented
Facets
infra-config · maturity active
database file-system caching databases microservices infrastructure-as-code self-hosted go self-hosted sqlite fuse replication distributed-database ltx fly-io linux docker
1 source
- readme: https://github.com/superfly/litefs · fetched 2026-08-28 · b4341ad17538
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| superfly/litefs | main | 70 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem