01 / ABOUT

I built the thing I couldn't find.

One person, one instance at a time, in the open.

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 the first section for myself. Then I kept going, because the same thing kept happening elsewhere: the tracking outgrew my head, and the tool I wanted still didn't exist.

I only add a section once I've been asking Claude for 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.

02 / HOW IT GOT HERE

FIRST

Money

Real accounting under a personal finance app, because I couldn't find one that had it.

Upcoming

Food

Currently working on this. It saves recipes I'm interested in, I use Claude Chrome to keep my pantry up to date, and I pull up recipes based on what is in my pantry

03 / THE ENGINE UNDERNEATH

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, then an MCP server and knowledge graph. One person's assistant is what it turned out to be for. This is the honest version of that path, including the turns.

Open-source business apps / Go framework / AI assistants / Finance app (iOS & Android) / MCP + knowledge graph / One person, one instance

The original idea

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.

The framework

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.

The turn

Assistants instead of screens.

When AI became generally available, the catalogue idea changed shape: rather than dozens of applications with dozens of interfaces, each part of a business could have an assistant. Same data underneath, far less software to design. So I went back to the core and rebuilt it around what that needed: an MCP server for Claude to talk through, a knowledge graph that keeps your information connected and keeps every change as history, and a framework that turns a proven pattern into real interface in a day rather than a quarter.

Then the obvious thing. The core never cared whose ledger it was. Everything built to give a company a private, connected, conversational system worked exactly as well for a household. And a household was the customer I actually had, sitting right there, with too many accounts and no idea what to make for dinner.

This is that same engine, pointed at one person instead of one company.

Why it matters to you

The core is open, and it outlives the product.

The WeOS core is open source under the AGPL. It is older than this product by years, and it doesn't depend on this product succeeding. If I stopped tomorrow, the core your instance runs on would still be there, still readable, still buildable by someone else.

That's the whole reason I can say you're never locked in and mean something by it.

License

AGPL

Written in

Interface

MCP + knowledge graph

Your instance

Its own database

05 / Built to outlive itself

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 is stored in open formats you can export and read without me. The engine underneath is open source: the WeOS core, licensed AGPL.

If I disappeared tomorrow, your data would still be readable and the core would still exist. I can't promise you forever. I can promise you're never locked in.