Connection health
4 accountsFidelity · 09:14
autoFeed uptime
30 daysYour rules
2 lockedBuilt against the complaints
Each screen below exists because a specific failure showed up repeatedly in the reviews. Where a screen answers a quotable complaint, the quote is named.
Connection health
Every account, its real status, and the timestamp of the last successful pull — on the first screen rather than three levels down.
Answers: 113 reviews describing feeds that silently stopped, discovered only when the budget stopped being true.
Connection health
4 accountsProvider failover
When one aggregator can't reach the institution, the next one is tried before you are told anything is wrong. The trace is visible, so the subcontractor stops being invisible.
Answers: “Plaid is apparently to blame but no solution.” — Monarch, 1★, 76 votes.
Fidelity · 09:14
autoFeed uptime
Thirty days of connection history per account. A degrading feed is visible as a trend before it becomes an outage you notice at month end.
Answers: reviews describing repeat breakage that support fixes once, then lets recur.
Feed uptime
30 daysRules that stick
Categorise once and it is locked. Auto-detection can be switched off entirely instead of quietly overruling you every statement cycle.
Answers: “no way to stop their auto subscription detection” — Rocket Money, 1★, 111 votes.
Your rules
2 lockedThese screens actually run.
There is a working demo at /app, filled with synthetic accounts and transactions — no real bank, no sign-up, nothing to install. Connections genuinely sync, a failed provider genuinely falls over to the second one, uptime is computed from the attempts that actually happened, and a category rule you add really does rewrite past transactions.
The product itself is still in development. If something in the demo is wrong for how you actually manage money, that is worth telling us before the rest gets built.