Services

Three areas, all scoped to end

The work behind the products is available to other teams. We are a small team, so we take the architecture and the hard problem rather than the large programme — and every engagement has a hand-over or a date on it.

• 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

  We build systems that hold up, and we can show the numbers2,500 concurrent game sessions and 10,000 connected players, zero failures, on four bare-metal desktop-class machines totalling 40 cores that were simultaneously running the load generator, our CI and the rest of our platform. It is the largest run the hardware allowed, not the point where anything broke.

• Platform engineering

  Self-hosted delivery platforms, with DevSecOps built in rather than bolted on

  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

  We run the platform we are describing51 ArgoCD applications and 2 ApplicationSets under GitOps on a self-hosted Talos Kubernetes cluster, carrying platform services, middleware, CI runners and product workloads.

• 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

  We model our own estate, not a worked exampleOur mahjong platform and the Kubernetes cluster it runs on are modelled together as one project — 152 elements and 257 relationships in a single identity space, with written verification notes.