Know the
History

AccountHouse began as a frustration you could feel at the dinner table — rent, groceries, and bills living in chat threads and fragile spreadsheets, while nobody quite trusted the total.

January was the vow. One engineer. Every layer. No company theater. The brief was intimate: make household finance honest enough for the people who actually live it.

Accessibility meant something concrete: one machine became the spine, exposing API endpoints across the home network so every seat at the table could reach the same ledger.

A plain webpage stood in front — fixed token, fixed circle. Not the public internet. Just the LAN, the family, and a door that only known keys could open.

The ask sharpened: not another desktop launch, but a phone-native way to catch spending while the day was still happening.

Nearly a month of learning from zero — AI as co-pilot for velocity — produced a modular backend and a dynamic schema so friends and relatives could inhabit the same system without hard-coded assumptions.

Payables arrived so recurring bills could behave like executable settlements — not sticky notes dying in a chat.

With weight in the data, linear models could be tested for analytics and forecast. Users gained spending insight and recommender signals grounded in projections and variance — foresight with receipts.

With the product stable on servers, the house gained rooms: Split groups, document vaults, goals, net-worth tracking. Android push via Firebase made the app present — not passive.

Security hardened in parallel. The backbone stayed the same: one person building and shipping, while parents, relatives, and friends stress-tested reality in production.