Four services, one lifecycle
We help you decide what to build, we build it fast, we prove it's correct, and we keep it running.
Most consultancies sell you one of those and leave you to find the other three. We do all four, and the reason they belong together is the third one: proving software is correct is what makes building it fast safe to buy, and what makes running it a promise rather than a hope.
Advise — decide what to build
Most costly technical decisions are not made badly. They are made early, with incomplete information, by people who will not find out for eighteen months whether they were right. We work with founders and engineering leaders on the decisions that are expensive to reverse: what to build first, what can wait, what to build versus buy, and which technical risks actually deserve the attention they are getting. That extends past architecture — into the material you need to raise money, into product research, and into training your team rather than replacing it.
Build — get it built, fast
Building software has genuinely got faster, and we use the tools that made it faster. What has not changed is that generated code is plausible before it is correct: it compiles, it reads well, and it can be wrong in ways review does not catch. We build at the speed the tools allow and then hold the result to the standard the tools do not — which is the same standard we apply to code written by hand.
Prove — show that it’s correct
Most testing tells you the cases you thought of still pass. We work on the ones you didn’t think of: what the system is supposed to do, written down precisely, and then checked against what it actually does. Test suite review, property-based testing, specification, and — for the parts of a system where being wrong is unrecoverable — formal proof. On any stack, in any language.
Run — keep it running
Identity, secrets and certificates are the three things that take a system down when nobody is watching them, and they are the three things no one owns until they fail. We run them as a service: managed Keycloak, Vault and certificate lifecycle, with an assessment first so you know what you are actually running before you decide what to change.
Our work in the Cardano Ecosystem
We are a multi-language engineering consultancy — Rust, Haskell and whatever the problem is actually written in — with a formal-methods practice behind it. A large part of that work has been on Cardano: we maintain Plutarch, Lambda Buffers and CTL, which other teams across the ecosystem build on.
If you are shipping Cardano smart contracts, two of the pages above have a Cardano-specific form. Cardano smart contract audits → covers Aiken, Plutarch and Plinth pre-launch. The health check → is the small, fixed-price end of the same offer, for teams testing the water.
If you are not on Cardano, none of that changes what we can do for you. The methods are the same; the ecosystem is not the point.
How this starts
A conversation first. Tell us what you are building and what it would cost you to be wrong. That call is free, and if it turns out we are not the right help we will say so.
A mutual NDA before we read anything that isn’t already public. We do not ask for access to your code to decide whether we can help you.
Then a scope and a fixed price, for the work that is actually warranted. We would rather tell you a two-week review is enough than sell you a proof you don’t need.
Not sure which one you need?
Most people arrive needing two of these and knowing about one. Tell us what you’re building and where it hurts, and we’ll tell you which part of this is worth buying — and which part isn’t.
