Small apps.
Serious craft.

The most useful software tends to be narrow. It does one thing, does it reliably, and stays out of the way. We build in that direction — not because it is easier, but because restraint is a discipline that produces better outcomes for the people using the tool.

Longevity matters more than novelty. An app that works correctly two years after release is worth more than one that ships with fanfare and degrades quietly. We aim to write code that ages well and maintain it accordingly.

Data ownership is not a feature — it is a baseline. The utilities we build are designed so that the person using them retains control of their information. That shapes decisions at every level of the stack, from architecture to the permissions we request.

We are a small operation by choice. Staying small means we can be careful, stay close to the work, and avoid the drift that comes with scale for its own sake.

We work remotely and have done so from the start. There is no office to visit, no timezone we insist on, and no preference for synchronous calls over written communication. Most decisions are made in writing, which keeps a record and gives everyone time to think before responding.

Async-first does not mean slow. It means we are deliberate. Milestones are agreed in advance, progress is shared regularly, and questions get answered — just not necessarily in real time. If that cadence suits how you work, we are likely a good fit.