// the take
A commercial double-entry accounting product (hosted SaaS plus self-host option) wrapped around the open-source Beancount/Fava stack, adding native iOS/Android apps, a `bea` CLI, and an MCP server plus thirteen agent skills for Claude Code/Codex. Aimed at developers who already like plain-text accounting and want a phone app and agent workflows on top of the same .bean files, not people new to double-entry bookkeeping.
It actually builds on Beancount and Fava instead of reinventing the ledger format, so your .bean files stay portable and readable by other tools — no new lock-in. The MCP design shows real thought for handing an LLM write access to your finances: dry-run previews on writes, confirm-gating, per-call reauth, and machine-readable error codes with a suggested next call. It ships genuinely native iOS/Android apps (Expo + RN + Apollo, both on the app stores) and a CLI that provisions its own Beancount/Fava engine on install, which is unusually complete platform coverage for a 309-star project. Self-hosting (single-server Docker, or a local macOS compose setup) is a real path, not just a token gesture.
The README is written to grow the GitHub page, not to document the project — three separate 'star this repo' asks, UTM-tagged links on nearly every URL, and a comparison table that happens to score the author's own product best on every row. That's worth discounting before trusting the other numbers (43 MCP tools, 64 resources, thirteen skills). The repo structure shown is dominated by process scaffolding (.pm/w0 and w1 directories with 180+ task files) rather than visible product code, a pattern more consistent with heavy AI-agent-driven scaffolding than organic multi-year adoption for a repo this size. The actual differentiator over plain Beancount+Fava is thin — a mobile wrapper and a CLI installer — and both nudge you toward the hosted beancount.io product, with self-hosting clearly the secondary path. Nothing in the docs addresses concurrent-edit safety when a phone app, a web client, and an agent via MCP can all write to the same plain-text file at once.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →