LiteFS
Fly.io (superfly) · databases · reviewed by Stan K. · Source: data snapshot · data as of 2026-11-12
SQLite replication on Fly.io that lost its paid tier — LiteFS Cloud retired 15.10.2024 and support formally “outside our scope” — a cautionary tale, not a bet for new production.
#9 of 9 in Databases
ToolScore breakdown — why 22/100
10 criteria × 10 points. Low pillars are visible on purpose — that's the point of a score you can audit. Methodology →
What it does well
- ▸The repo lives on at superfly/litefs — “actively maintained but beta”
- ▸It is still SQLite underneath: the file format remains yours
- ▸The retirement is documented, not rumor — Cloud’s 15.10.2024 shutdown and the support withdrawal are on public record
Where it costs you
- ▸LiteFS Cloud retired 15.10.2024 — the backups product is dead
- ▸Fly support formally withdrawn: “outside our scope of support” (docs, 10.2026)
- ▸“Actively maintained but beta”, pre-1.0 APIs — the repo’s own status line
- ▸Not a bet for new production
Hidden traps — the stuff the pricing page doesn't say
LiteFS Cloud — the managed backups product that made the edge-SQLite story complete — was retired on 15.10.2024. The price of the product you would have bought no longer exists, and neither does the product.
Fly’s own docs (10.2026) put LiteFS “outside our scope of support”. When replication breaks at 2 a.m., the vendor has pre-announced that it is not coming.
The repo describes itself as “actively maintained but beta” with pre-1.0 APIs — the interfaces you build against can still change under you.
Know the limits before you pay: read the traps above, then decide with eyes open.
Visit official siteAffiliate link where available — never affects the score.
- official superfly/litefs repo — “actively maintained but beta”, pre-1.0 APIs (status via repo/docs, 10.2026) verified
Data as of 2026-11-12. Prices and limits change monthly — report anything stale. How we verify: methodology.
Closest alternatives
Per-document pricing where the free tier caps by the DAY (50K reads/DAY) and Blaze has no hard spend
No free tier and no $0 ramp — day one is PS-5 at $5/mo ($15 HA 3-node) — and the engine is Postgres
Hourly cluster tiers with a rare honest cap — Flex ($8–30/mo, 5GB) publishes its monthly ceiling — b
LiteFS review
In-depth analysis · last updated 2026-11-12
The edge-SQLite answer that lost its answer
LiteFS was the edge-SQLite play: SQLite replication on Fly.io, reads everywhere, writes coordinated. The hub now lists it as “was the edge-SQLite answer — now a cautionary tale”, and the dates explain the rewrite. LiteFS Cloud — the managed backups product, the part you could pay for — was retired on 15.10.2024. Fly’s support is formally withdrawn: the docs (10.2026) put it “outside our scope of support”.
What actually remains
A repo at superfly/litefs, self-described as “actively maintained but beta” with pre-1.0 APIs. That is not nothing — the code exists, and underneath it is still SQLite, so the file format remains yours. But everything that made it a product rather than a project is gone: no paid tier, no vendor support, no stable API promise. The hub’s verdict is blunt: not a bet for new production.
How the pillars land
This is the one review in this batch where the neutral band sits low, and the reason is structural: the product you would score no longer exists commercially, and the hub carries the whole row under a “bad” flag. Price/Value 2.5, Real limits 2.5, Latency & cold starts 2.5, Data handling 2.5, Feature set 2.5: no live facts to score higher — held at the low neutral for a product whose paid tier is retired. Portability & export 3: it is still SQLite underneath, the one surviving strength. Track record 1: Cloud retired 15.10.2024 — the track on record is a shutdown. Ease of use 2: pre-1.0 APIs under a “beta” label. Pricing transparency 2.5: the retirement and withdrawal are honestly documented, which is the best that can be said. Support & docs 1: “outside our scope of support” — the vendor’s own words.
Verdict — CAUTIONARY TALE, 22/100
Read LiteFS as the industry lesson, not the product: an edge-database architecture whose commercial backing evaporated while the code lived on. If you are already running it, the SQLite files are yours and the exit is a file copy. If you are starting something new, the local-first pattern is served today by Turso embedded replicas — scored 72 in our hub, and still a supported product.