On-device by default
If a feature can run on the phone, it runs on the phone. The network is a privilege we ask permission for, never an assumption we design around. This is why there is no sync — a copy you cannot see is still a copy.
Lab
The LabWhat we build, and the rule we build to The DoctrineFour commitments, stated as constraints Engineering StandardHow the work is held to account What We ShipEverything currently in the world Contactsupport@thebrinklabs.comInstruments
Zero-Based BudgetGive every unit of income a job before you spend it. Subscription AuditWhat renting software really costs, per use and per decade. Emergency FundSavings divided by the month you cannot avoid. Debt PayoffAvalanche or snowball, priced to the month and the cent. True Hourly WageWhat an hour of your life actually pays, after the job takes its cut. Net WorthEverything you own against everything you owe.MyneWallet
OverviewThe app, and what it refuses to do How It WorksEnvelopes, capture, analysis What It CostsFree tier and the one-time unlock QuestionsFourteen answers, no marketing Privacy PolicyFourteen sections, plainly written Get it on Google PlayAndroid · the only official listingIndependent Software Lab
The Brink Labs is an independent software lab. We build tools that run on your own device, keep your data where you put it, and are bought once rather than rented forever. Everything below is either shipped or not mentioned.
The Doctrine
A principle you can break at will is a preference. These four are written into the architecture, which is what makes them checkable rather than reassuring.
If a feature can run on the phone, it runs on the phone. The network is a privilege we ask permission for, never an assumption we design around. This is why there is no sync — a copy you cannot see is still a copy.
A tool you open daily makes an excellent subscription and a poor deal. We charge once. If the company disappears tomorrow the software keeps working, because nothing about it depends on us still being here.
There is no analytics SDK, no attribution SDK and no crash reporter phoning home. We do not know how many screens you opened today, and we have built ourselves no way of finding out.
Arithmetic about somebody’s money is not a place for approximately. Every figure is checked against an independent implementation before it ships, and a feature waits if the maths is not settled.
A privacy policy is a promise about what a company will choose to do.
An architecture is a statement about what is possible.
What We Ship
A small catalogue, deliberately. We would rather be answerable for a few things that are finished than for a shelf of things that are nearly working.
A budget planner and expense tracker that never asks for a bank login, never sends your ledger anywhere, and keeps working in airplane mode — because there is nowhere for it to phone.
Free to use. One-time unlock for the full engine. · Read what it refuses to do →
Small, exact tools for the questions money raises. Each runs entirely inside your browser, boots on a worked example, and is checked against a second implementation before it ships.
No account, no cookies, nothing uploaded. · Open the index →
Engineering Standard
Personal finance software fails quietly. A wrong figure looks exactly like a right one, so the only defence is refusing to trust the first implementation of anything.
We publish the failures too. The build report for this site lists eight defects found and fixed in the last pass, including two that had been live for weeks — because a standard nobody can audit is a slogan.
Where To Start
If you want to see how we build before you install anything, the instruments are the honest preview: same architecture, same refusal to phone home, no sign-up to find out.