Built with Konomi.

Konomi is a living-system architecture created by Thomas Frumkin. Everything on this estate is what we've built with it — sovereign software you own, running on your own machines. What I have built is one small part of what Konomi can do — a fork, downstream of Thomas. Konomi itself lives at its own home; this is just the proof of what one person made on a corner of it.

What every build here keeps

1 · You own it

Every build on this estate is a file, not a subscription. The source is in your hands under a licence nobody can revoke. There is no vendor who can raise the price, discontinue the product, or switch it off — because there is no vendor between you and your software.

Proof: the estate — hundreds of live builds, every one open-source, every one a page that keeps working if we disappear tomorrow.

2 · It runs on your machines

These builds run in your browser and work offline. Your client records, case files, and numbers stay on your device — they never travel to a server, because there is no server. For firms whose regulators expect them to control client data, this isn't a preference; it's the point.

Proof: the regulated shelf — working tools for claims firms, accountants, brokers, and agents, each one running entirely on the machine that opens it.

3 · The maths is proven before it ships

The engines that compute deadlines, totals, and money are tested by deliberately breaking them — mutation testing — which checks not just that the code passes its tests, but that the tests would catch the code if it were wrong. A total that can't reconcile refuses the document instead of being silently absorbed. And where an engine has a limit, the limit is printed on the page.

Proof: Northgate Claims — a fictional firm running a live working day on those engines, with its own limitations stated on screen.

4 · Machines never cross the human doors

In the systems I build on Konomi, automated agents run the routine work — but four kinds of action always stop and wait for a named person: moving money, signing anything legal, judgment calls, and moments of client trust. This is enforced in the software itself, not written in a policy. Nothing signs itself.

Proof: the konomified company — a 100-person firm designed seat by seat, where the org chart is validated by code that refuses any structure breaking that rule.

What these builds don't do — yet

Said plainly, because trust is the product:

These builds today are single-device by design — there is no shared multi-user layer, so a team working one caseload together needs that layer built as part of their deployment. There is no cloud scale-out, because there is no cloud. And a build here will not pretend to be finished: every demo prints its current limits, and this page keeps this section for as long as it stays true. A vendor that hides where it's weak shouldn't be trusted where it's strong — that rule applies to us first.

Where Konomi comes from

Konomi is the creation of Thomas Frumkin. We learned it and build on it — the estate you can walk here is our application of Konomi, not its origin. For what Konomi is in its own words, go to its home: konomi-systems.com.

See it, then talk to us

Walk the builds first — they're the argument. Then bring us your firm.

Watch a company run on Konomi →