About
We build software, servers and control systems from Orange, California. Most of our work is the kind that has to keep running after everyone has gone home.
We would rather tell you it is not built
A feature is not done because the code compiles. It is done because it was run against a real system, checked, and the check written down. When something is incomplete we say so plainly — including when saying so is inconvenient, and including when nobody would have noticed. A gap you know about is a decision; a gap hidden behind a confident paragraph is a problem you inherit later.
The reasoning is part of the work
Every decision worth making is worth writing down with its alternatives attached — what we chose, what we rejected, and what would have to change for the answer to be different. It means the next person to open the system, including a future version of us, does not have to reverse-engineer intent from code. It also means we can be argued with, which is the point.
Built for the day nobody is watching
Queries that cannot accidentally return everything. Credentials that can be rotated without a rewrite. Errors that say what actually happened instead of apologising. None of it demonstrates well, and all of it decides whether an ordinary Tuesday stays ordinary.
Clear is not the same as cold
An interface can be precise and still have some warmth to it. But the moment something breaks, personality gets out of the way — error messages and documentation should be plain, direct and easy to search. Those are two different jobs and we try not to confuse them.
Working together
If that sounds like the way you would want a system built, tell us what you are trying to do. We will tell you honestly whether we are the right people for it.