Tomko & Company
Software is being reinvented.
The tools available today give us a rare opportunity to rethink software from first principles: what we use it for, how we build it, how we interact with it, or how we stay away from it.
We exist to help define what good software looks like in this new era, how it is built, and to build it ourselves.
Work
Civil
Civil takes engineering drawings and turns them into information an engineer can work with. We’re starting with utility engineering and building its capabilities one at a time. Civil 0.5 is a bounded customer-validation build: exhaustive independent competence validation has not been performed, and its evidence covers three drawings from two projects.
We want to see whether we can build a junior civil engineer through software. That means teaching Civil individual competencies, testing them against real work, and making sure an engineer can understand and check what it produces.
Mila
We are developing Mila for our own family photographs, with the aim of organizing a locally stored archive into a chronology we can browse. We are working toward retrieval through the people and places in our memories; reliable retrieval across them is not something we have demonstrated.
We’re rethinking how people interact with their memories. Instead of opening an app and searching through thousands of photographs, we want families to experience their memories naturally through the devices already in their homes. We’re starting with photographs and building toward something much bigger.
Penny
Penny brings financial records from different institutions together so you can understand your finances in one place. It starts with investment statements, keeps track of where every number comes from, and helps you see your financial position across accounts and currencies.
We’re building toward a system that understands a household’s finances over time. We want people to be able to ask what changed, understand why, and trust that every answer can be traced back to their own records.
Alfred
Alfred runs locally in the home and keeps track of the devices its network observations reach. It reports which devices it has observed and what has changed between observations. Detecting when a device has left the network has not passed live-network validation. Right now, it observes and reports. It doesn’t control anything.
We’re building toward a home assistant that understands its environment and can eventually take action on your behalf, with your permission. We want software that helps run the home without requiring you to constantly open an app or give it instructions.
Roger
Roger is the engineering system we use to build our products. It helps us turn ideas into specifications, delegate work to AI agents, review what they produce, and keep track of decisions and progress across releases.
We’re rethinking how software is built. As frontier models improve, we want to take advantage of what they can do without losing control of the engineering process. Roger helps us keep the work organized, tested, and available to the next agent or model that picks it up.
HavenOS is the local platform we’re building to bring this work together. We want our products to remember what happened, work together when it makes sense, and give people control over their own data and devices.
Selected releases
Civil
Civil learned to treat notes and standards citations as records of their own, and to show what it could not resolve.
Alfred
Alfred learned to build an inventory of the devices its network observations reach, and to report what appeared or changed between them.
Penny
Penny learned to reconcile investment records across institutions and currencies into one household view, while preserving the source of every converted value.
How we build
Competence
We build with people who know the work. We teach the system one part at a time, test it against the real job, and improve it.
Continuity
Software should remember what happened, where information came from, and what changed. That is what HavenOS is for.
Sovereignty
Good software should work for the people using it. We prefer private and local systems when they make sense, and we want people to stay in control of their data and tools.