Working with us: three ways to engage
We are a platform engineering practice with six years of continuous enterprise engagements across energy, government transport, government insurance, and financial services. The pattern across all of them: developer platforms on AWS EKS, GitOps with Argo CD, Terraform, Backstage service catalogs, Kafka event backbones, and, since 2025, AI-native delivery tooling built on the Model Context Protocol.
1. Platform Assessment
Fixed price, 2 weeks.
A structured audit of your internal developer platform, CI/CD, and cloud posture. You get a written report and a prioritised roadmap, not a slide deck.
What gets assessed:
- Developer self-service: what still needs a ticket to a platform team, and what it costs you.
- CI/CD health: pipeline security (OIDC versus long-lived credentials), runner architecture, drift across repositories.
- Kubernetes and IaC posture: upgrade debt, module hygiene, blast radius of change.
- Catalog and discoverability: can an engineer find who owns a service, where it runs, and how to change it.
Proof this is a practiced playbook, not a template: the assessments embedded in the transport agency and government insurer engagements, where audit findings became the delivery backlog.
2. IDP Accelerator
6 to 12 weeks.
Hands-on build-out of an internal developer platform: Backstage service catalog, self-service provisioning (repositories, databases, environments), GitOps deployment (Argo CD), and preview or sandbox environments, delivered inside your repos with your team.
This is the playbook run at four organisations:
- A cryptocurrency exchange: isolated sandbox tenancy with ephemeral nightly-destroyed EKS clusters, Backstage catalog, Terragrunt module library.
- A government insurer: self-service repos and dev databases behind PR approval, Terraform plan and kubectl diff as PR commentary, ARC runner migration.
- A state transport agency: EKS upgrade automation, Backstage IDP proof of concept, CI modernisation.
- An energy utility: a standardised Terraform EKS blueprint bootstrapping Argo CD via GitOps Bridge, a governed add-on stack, and Confluent Kafka on Kubernetes.
You get working software, handover tooling (every engagement above ended with a documented CLI or runbook), and your engineers trained on the result.
3. AI-Native Delivery Enablement
4 weeks.
Make AI coding agents productive and safe inside your engineering organisation: MCP servers over your internal systems, guardrailed natural-language interfaces to your catalog and knowledge base, and CI that can verify agent-written code.
Grounded in shipped work, not demos:
- An MCP reference architecture (TypeScript, stdio and HTTP transports) built for a financial services client.
- A read-only, guardrailed natural-language interface over a Backstage catalog.
- A knowledge service indexing Confluence, Jira, and GitHub, linked to the service catalog, exposed via MCP and an AWS Bedrock chatbot.
- A continuously exercised personal harness of 75+ experiments in agentic delivery.
Get in touch
Use the contact form or find us on LinkedIn.