Having said that, the thing I care about the most in YNAB is importing expenses from my bank accounts. My thought on replacing this was to be able to add download URLs to my spreadsheet and kick off a script which would prompt for manual username and password entry (so that the credentials aren't saved) before downloading and parsing the exports. I haven't gotten around to creating this yet - if you added it to your project, I would seriously consider using it!
I've also used YNAB and loved how it could categorize spending. So a part of my project is that it lets you use udev-inspired matching rules to assign categories or other properties to transactions.
You can also put credentials for each bank in an encrypted file behind a master password. I can't promise it's secure but it's enough for me to not worry about saving the info to disk.
There's still work to do: I've only implemented a couple bank backends and some core logic, and haven't got around to adding anything for analysis, or a real setup.py, or a readme. Still working on it a bit every day. Fidelity is next. Would love it if anyone was interested and wanted to add their own equally jank bank backend.
If you like a command line based approach I'd recommend you to have a look.
Well, it uses Google sheets to store the data. So I don't agree with this 'benefit'.
"Tacking Numbers" is the name I came up with when I was trying to setup Sheets API with Google API Console. I am not able to change it now.
