An editorial ledger, not a feed.
Manual entries, imported rows, recurring charge clarity, debt planning, and a record built for checking instead of scrolling.
Kapers · software kept in hand · est. 2026
Studio home
Software you own. Software that stays yours.
Built slowly. Kept honest. Useful after the novelty burns off.
Kapers is a small studio for private tools. The standard is plain. A product should tell you where the data lives, what survives airplane mode, how to leave with your records, and what the company is unable to do. If those answers are foggy, the product is not ready.
1Flagship product in market
582Tests behind the finance engine
0Decrypted ledgers held on servers
Flagship product
Garden is the first proof of the studio thesis.
Garden is local-first personal finance. Statements import on-device. The vault stays encrypted on-device. The product remains useful offline after first load. Privacy is not a tone of voice here. It is a limit enforced by the structure of the product.
That matters because money records do not belong in an attention machine. They need to stay readable in a hard week, on a bad connection, and under the kind of scrutiny that comes when trust is earned slowly.
The server never gets the first look.
CSV, OFX/QFX, and PDF import run locally. The first useful moment happens on your device, not in someone else’s pipeline.
Studio principles
Local-first, private by limit, durable by design.
Local-first
The default home for important records is the device in your hand. The network is invited in only where it is plainly needed.
Privacy by architecture
A company should not need good intentions to avoid abuse. The system should make bad behavior structurally difficult or impossible.
Durable tools
Interfaces should keep their shape when real life interrupts them. Less theater. More legibility. Better recall months later.
User ownership
Exports, backups, offline use, plain language, and clear deletion are not polish. They are the mechanics of ownership.
Proof
Numbers and claims that can survive inspection.
582
Passing tests gate the Garden financial engine.
0
Servers hold decrypted Garden ledger data.
3
Platforms ship the same product model: web, iOS, Android.
Local
Statement import, categorization, and encrypted vault behavior happen on-device.
Offline
Garden and this site keep working after first load without a live connection.
Founder
Khushin Patel builds from the premise that calm is a discipline.
The founder note is not a bio page. It is the longer argument for why local-first matters, why trust has to be mechanical, and what standard the work is meant to hold when money, records, and recovery are involved.
Field notes
Working notes from the studio floor.
Renaming the studio from a person to a place.
The shift from `khushin` to `kapers` was a small naming change with a larger effect. The work needed a studio name, not a personal domain in disguise.
Import as the first proof surface.
Garden’s import engine matters because it proves the architecture at the first useful moment. The statement gets read before the server gets a vote.
Delegation is part of the craft.
Old orchestration was removed so the studio could hold a cleaner line: fewer moving parts, clearer judgment, and no machinery that outgrows the work.