FLOKUS FINANCIALS
IN PRODUCTION — SINGLE USER
Every account and asset, on one page.
Answering one question — where do we actually stand? — used to mean a handful of logins and a spreadsheet I kept forgetting to update. Financials answers it on one screen: every account, every asset, and what the whole thing adds up to. It runs for a single user by design, and right now that user is me.
01 — WHAT IT DOES
One screen, whole picture
It's a dashboard, not a budgeting app. The job is showing me where things stand without making me go find out.
- ACCOUNTS AND ASSETS
- Everything in one list instead of one login per institution.
- NET WORTH
- What it all adds up to, and how that number has moved.
- THE OVERVIEW IS THE POINT
- If I have to click three times to see where we stand, it hasn't done its job.
02 — WHAT IT DOESN'T DO
Deliberate limits
- ONE USER
- It serves a single person, and that isn't a limitation I'm in a hurry to remove. It keeps financial data scoped to exactly the one person who needs it.
- NO ADVICE
- It reports what's there. It doesn't recommend, rebalance, or predict, and I'm not qualified to build something that does.
03 — HOW IT'S BUILT
Boring on purpose
This one holds the numbers that matter most, so it gets the least adventurous engineering I know how to do.
- STACK
- Python and PostgreSQL, containerized with Docker.
- BACKUPS
- Nightly and off-host, and I've restored from them on purpose — an untested backup isn't a backup.
- DEPLOYS
- Every push runs tests before it can reach production.
- WHEN IT BREAKS
- I write down what happened and what changed so it can't recur.
IF YOU WANT ONE
This is built for one household right now.
Financials runs for exactly one person — me. If you'd want it for your household, leave an email and I'll tell you when it's ready for other people. That's the only thing I'll ever use it for.
No list, no newsletter, no sharing. One email, when there's news.