Hi everyone,

I wanted to share the 0.2.0 release of Cashdera, a local Windows desktop analytics companion for GnuCash.

Cashdera opens a local GnuCash book and builds a local SQLite cache for analytics. The original |.gnucash|file is not modified. There is no account, no server sync, no cloud upload, and no telemetry.

The goal is not to replace GnuCash. The goal is to provide a modern local analytics layer on top of existing GnuCash data.

What Cashdera currently focuses on:

 * Cashflow overview
 * Income and expense trends
 * Sankey-style money flow visualization
 * Transaction search and filtering
 * Net worth / balance sheet view
 * Year-over-year comparison
 * Basic anomaly alerts
 * Dark mode

The main architectural idea is cache-first analytics. Heavy parsing and aggregation happen during import/reimport. After that, dashboard pages read from precomputed local SQLite tables instead of repeatedly scanning the original book. This is meant to keep navigation and reporting fast, especially on larger books.

This is still an early beta, so I would be especially interested in feedback from people who use GnuCash with real-world books and care about local-first workflows.

Useful feedback would include:

 * Does the import work correctly with your book structure?
 * Are income/expense/category views accurate?
 * Are the reports useful compared with the built-in GnuCash reports?
 * Does the app remain responsive on larger books?
 * What analytics view is missing for your workflow?

GitHub release: https://github.com/proars/Cashdera/releases/tag/v0.2.0

Project page / screenshots: https://github.com/proars/Cashdera/releases/tag/v0.2.0

If you test it, I strongly recommend using a copy of your book first, as with any early beta software.

Thanks,
Ars

_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to