Khushin Patel
Garden / release candidate / ongoing

Personal finance with the ledger in view.

Garden is a privacy-minded personal finance product built around inspectable records, deliberate review, and useful local workflows.

Current / why

A workspace, not a decorative dashboard.

Garden keeps position, transactions, planning, accounts, insight, review, import, and privacy controls within a system that can be inspected rather than merely admired.

It exists because important financial work should remain legible as it grows more complex.

Garden desktop Overview showing the current financial workspace.
Evolution

Every version uncovered the next problem.

The historical image record is incomplete, so early phases are deliberately left unillustrated.

Archive image needed
First iteration

First iteration

Visual archive not verified.

Archive image needed
Second iteration

Second iteration

Visual archive not verified.

Archive image needed
Third iteration

Third iteration

Visual archive not verified.

Current Garden Transactions with Inspector open.

Desktop ledger

Context enters beside the ledger instead of replacing it.

Garden mobile Review.

Mobile direction

Daily work stays focused while review remains available.

Desktop ledger

The whole system, with context.

Financial administration needs density, but the next piece of context should arrive without throwing away the current view.

Mobile direction

Focused, not compressed.

The phone is a daily instrument for position, activity, capture, and review—not a shrunken administration panel.

Privacy / local and connected

The network boundary is named.

Local mode: no ledger data leaves the device. Manual accounts, transactions, imports, budgets, goals, review, and encrypted backup remain useful without a connected account.

Connected mode: selected data passes through Plaid and a stateless Garden relay. No decrypted server-side copy is retained. Connected mode is not described as though nothing leaves the device.

Selected decisions

Trust has to be visible.

Meaningful changes should have a readable path from input to review to result.

Import

Recognition, mapping, duplicate checks, preview, commit, and Undo form one sequence.

Ledger

Recorded facts stay distinct from projections, and inspection does not obscure the table underneath.

Mobile

Daily use favors short, designed paths over a smaller copy of desktop.

Current state

Release candidate, still being refined.

Garden is serious ongoing product work. The current desktop and mobile captures show the direction now; the early visual archive still needs verified source images.

Back to the work ledger