Services
Three lines, all scoped to end
We are a small team, so we work where a small team is an advantage: the architecture and the hard problem, on engagements with a hand-over or a date on them. What we decline is listed alongside what we take on.
Software engineering
Architecture and delivery for systems that have to hold up under load
A bounded project, with a dated end
Architecture-led work on distributed, event-driven and legacy-modernisation problems on the JVM, sold as bounded projects.
- Architecture and design
- Diagnosis under load
- Building the system
- Legacy modernisation
DevSecOps environments
A complete, self-hosted delivery platform — set up, proven, and handed over
Set up and hand over
We build the whole automated environment a team needs to ship software safely on infrastructure it controls, then hand it over.
- A full SDLC environment from scratch
- Cloud repatriation
- An application-security toolchain
Architecture modelling
Models that a machine can check, instead of diagrams that quietly go stale
A bounded engagement, or a method your team keeps
Enterprise and solution architecture modelling governed by a meta-model, so a model cannot drift into meaning whatever its author wanted.
- Modelling an existing estate
- A meta-model your models are checked against
- Solution design that stays connected
- Getting the practice to stick
The rule behind all three
Every capability claim on these pages names the thing that demonstrates it. Where we have not done something, it is not listed — and where a line has a limit worth knowing before you call us, the limit is on the page.
Consulting funds the product work, and is meant to shrink as the products earn. That shapes what we take on: engagements that finish.