I built the thing I couldn't find.
Real accounting for your own money, one person at a time.
I have a master's in accounting and a career spent building software for other people. WeOS started because my own money got away from me; too many accounts, too many moving pieces, and nothing on the shelf that used any of what I already knew.
So I built it for myself: a personal finance app with real books underneath, where every account, transfer and statement lands in one ledger and the numbers add up.
I only add a feature once I've needed it long enough to know its shape. That is slower than shipping against a roadmap. It also means nothing in here is speculative; every part of it started as something I needed twice.
A finance app for small businesses, on iOS and Android, wired into QuickBooks and Square.
The same accounting, pointed at personal money, because I couldn't find a personal finance app that had it.
I spent years building the foundation before I knew what it was for.
WeOS started as an attempt to rethink how business applications work. It became a framework, then a finance app for business, now a finance app for personal use. This is the honest version of that path, including the turns.
Business software you could own.
The first version of WeOS wasn't a framework at all. It was an argument. The common business applications (the books, the inventory, the customer records) shouldn't be a monthly rental you can never leave. I wanted to rebuild them as open-source apps and distribute them, so a small business could run on software it actually owned.
To build many apps, I had to make apps easier to build.
A catalogue of applications is a lot of applications. So I built a framework to carry the parts they all share: data, history, permissions, APIs. I named it WeOS too, which I was quite pleased with at the time and have been explaining ever since.
It's written in Go: small binaries, no runtime to babysit, fast enough that a personal instance costs almost nothing to run. That decision is why one developer can stand up a separate database per user without it becoming a second job.
The first thing I shipped on it was a finance app for businesses, on iOS and Android, wired into QuickBooks and Square. That's where the accounting rigor here was earned: on real ledgers, with real reconciliation, for people whose month-end depended on it.
From a company's books to yours.
The core never cared whose ledger it was. The accounting built to close a company's month worked exactly as well for a household's. And a household was the customer I actually had, sitting right there, with too many accounts and no clear picture of where the money went.
AI made the books easier to reach. Instead of learning another set of screens, you can ask your own assistant about your money, and the answer comes from the ledger rather than the model.
This is that same finance engine, pointed at one person's money instead of one company's.
Accounting you don't have to operate.
Years of business ledgers are why the numbers here reconcile: transfers between your own accounts count once, statements tie out, and a report means the same thing every time you open it. You don't need to know any of that to use it. It is why the answers are right.
One instance per person, and a way out of it.
Your instance runs on its own database (a couple, actually). Your data isn't sharing a table with anyone else's. Everything exports in open formats you can read without me.
Your books are yours. If you leave, they leave with you.