Neiliro Is a Family Hub in One SQLite File (No Subscription)
· Tutorials
Tasks, notes, calendar and a full money section for one household: one Docker container, one SQLite file, offline PWA. The series' rarest find at 43 stars.
Last updated: September 6, 2026 · 7-minute read
Forty-three stars is the smallest number any Buried Treasure pick has opened with, and this one earns it. Neiliro is a self-hosted household hub — tasks, notes, calendar, shared lists and a genuinely complete money section — that runs as one Docker container backed by one SQLite file, with no external services and a read-only offline mode when the home Wi-Fi drops. Created August 11, 2026, it is three and a half weeks old as of verification and already on its eighth minor release.
Buried Treasure №16 closes this eight-article batch with the purest expression of the series thesis: a project whose star count says "invisible" and whose feature depth says "maintained with love by someone who uses it daily". Every fact below comes from the repository and README, verified September 6, 2026.
What the repo actually shows
The vitals: AGPL-3.0, TypeScript on Fastify and React, 7 forks, 29 open issues against a CI workflow badge, pushed to on the day of writing. The release train is the telling part — v1.6.0 on August 25, v1.7.0 the next day, v1.8.0 August 26 week and v1.8.2 by September 3. Eight releases in under a month is a maintainer shipping against their own family's bug reports, and the README says exactly that: the core is complete and battle-tested by daily family use.
That phrase — built for a household, not a corporation — is the positioning line, and the architecture matches it. One container, one SQLite file, no message queue, no Redis, no external auth provider required. It runs on a home machine over LAN or on the same cheap-VPS tier as SwiftWave, and the ghcr image means the install is a compose file away.
The feature set that should not fit in one file
The completeness is the shock. Tasks arrive with projects and a kanban board. Notes carry attachments and wiki-links, so recipes link to shopping lists. The calendar handles recurring events for shared and personal lanes. There is a shared family mailbox that converts an emailed letter — school notice, utility bill — into a task with one click, which is the kind of workflow detail only a household operator thinks to build.
The money section alone outclasses most standalone budgeting apps: accounts with balances, expenses and income, transfers, bank reconciliation, categories, budgets, recurring transactions and receipts. Sign-in supports passwords and Google with optional two-factor codes. The app installs to the phone's home screen as a PWA and keeps working read-only when the network does not — the honest failure mode for a family tool, where viewing the shopping list in a basement matters more than syncing it.
The anti-Notion argument, made well
The README's best section is the one most projects skip: an honest answer to "why not Notion, Obsidian or Nextcloud?" The framing is a trade, stated without disparagement — Notion and Obsidian are builders, blank canvases where the family system is yours to design, maintain and teach to a spouse who never asked for a database course. Neiliro is the opposite: an opinionated finished product where the decisions are already made and the widgets work on day one.
That is also the honest dividing line for readers. If configuring the system is the hobby, the builders win. If the goal is a shared household brain that a technophobe partner will actually open, the finished product wins — and the market has almost nothing open source between those poles. It is the same gap analysis that made the SaaS alternatives guide one of this site's most-referenced pieces, applied to the room where the family's actual life happens.
The honest caveats
Four, because the stakes are personal data. First, 43 stars and one visible maintainer is the earliest-stage project this series has covered — bus factor is real, and anyone adopting it should accept that the project could stall. Second, being the household's money ledger means the SQLite file becomes precious infrastructure; the no-external-services design keeps it private, and simultaneously makes your backup discipline the only thing between the family budget and a dead disk.
Third, age: v1.8 after three weeks means the schema may still move, and upgrades early in a project's life deserve a file copy before each pull. Fourth, the series-standard note — repository-verified, not deployed in this site's household, so the "battle-tested" claim is the maintainer's and one family's, not this review's.
Who it is for, who should skip
Strong fit: households that want the family brain off Big Tech's servers — the same instinct behind the privacy stack — plus anyone who has bounced off Nextcloud's family-use setup cost, and couples who want one money ledger with receipts instead of three apps and a spreadsheet.
Skip it if you need multi-family federation, bank API auto-import, or a mobile app store presence — the PWA is good, but it is a PWA. And if you are reading this series for infrastructure rather than home use, star the repo anyway: this is exactly the project that deserves the discovery bump the star count exists to provide.
Verdict
Buried Treasure started with privileged Android access and, sixteen picks later, landed on a family's shared brain in one SQLite file — and the through-line held: small teams and solo maintainers shipping infrastructure-grade care the big platforms stopped offering. Neiliro is the series' rarest find by every measure except usefulness per megabyte. Back up the file, share the login, and let the family mailbox turn its first bill into a task.
That closes the eight-article batch — №9 through №16. The series continues; the next pick is already shortlisted. Start from the first Buried Treasure if the streak is new to you.
---
Not affiliated with the Neiliro project. Facts verified from the GitHub repository, README and releases on September 6, 2026. More open-source discoveries in the Buried Treasure series.