I posted this a few days ago and got some quiet but positive interest. I've spent the weekend hardening the "Sovereign" aspects of the app.
The Architecture:
React 19 + Vite: Using the latest React features for a high-performance IDE feel.
Immutable Ledger: Every transaction is a state transition in a double-entry system. No "editing" history—only reversals and corrections, just like real accounting.
Local-First (IndexedDB/LocalStorage): Your financial data never touches my server. The app is a static client.
Stateless AI Proxy: We use Gemini to parse "Paid $50 for AWS" into structured journal entries, but the proxy is stateless—it doesn't store the prompt or the result.
Why?
I wanted a tool where I could work on my runway in a coffee shop without worrying about the person behind me (hence the Privacy Shield blur mode) or my data being sold to advertisers.
I'm auvira_systems and I'd love to discuss the trade-offs of building complex stateful apps entirely in the browser.
auvira_systems•1h ago
I posted this a few days ago and got some quiet but positive interest. I've spent the weekend hardening the "Sovereign" aspects of the app.
The Architecture:
React 19 + Vite: Using the latest React features for a high-performance IDE feel.
Immutable Ledger: Every transaction is a state transition in a double-entry system. No "editing" history—only reversals and corrections, just like real accounting.Local-First (IndexedDB/LocalStorage): Your financial data never touches my server. The app is a static client.
Stateless AI Proxy: We use Gemini to parse "Paid $50 for AWS" into structured journal entries, but the proxy is stateless—it doesn't store the prompt or the result.Why?
I wanted a tool where I could work on my runway in a coffee shop without worrying about the person behind me (hence the Privacy Shield blur mode) or my data being sold to advertisers.
I'm auvira_systems and I'd love to discuss the trade-offs of building complex stateful apps entirely in the browser.