Product Center

We build on our own systems before we sell the approach

Everything listed here runs in production with real users and real failure modes. That is deliberate. It is easy to describe an architecture on a slide and much harder to keep one running for a year, and the second is the only version worth listening to. When we recommend an approach to a client, it is usually one we have already had to operate ourselves, including the parts that went wrong.

Each product is a different kind of problem

They are not variations on one platform. A trading analysis engine, a medical records system, an education platform and a learning academy have almost nothing in common technically, which is the point: the discipline that carries across is the engineering practice, not a reusable codebase. Building in four regulated or semi-regulated domains is also how we learned that compliance is an architecture constraint and not a documentation exercise.

What you can check for yourself

Each product page states what the system does, what it runs on, and what state it is in. Where a product is live you can go and use it. Where something is early we say so rather than describing an intention in the present tense. If a claim here matters to a decision you are making, ask us for the detail behind it and we will send it.