Platform Engineering
Internal developer platforms, golden paths and self-service, so the platform team stops being a ticket queue.
The problem
Onboarding a new service takes days of tickets, every team has re-solved the same infrastructure questions differently, and the platform team is the bottleneck for anything that touches a cluster, a pipeline or a cloud account. The organisation has the people to build a platform but not the shape of one.
What you receive
- A platform architecture and roadmap matched to the team that has to run it
- Working golden paths with a service template that produces a deployable repository
- Self-service onboarding with the guardrails written down
- A measurable before-and-after for onboarding time and deployment frequency
Capabilities
- Internal developer platform design sized to the organisation, not to a vendor's reference architecture
- Reusable platform patterns and infrastructure abstractions teams can adopt without understanding every layer
- Golden paths: repository to production for a standard service without a ticket
- Developer self-service and workload onboarding flows
- Standardized deployments and environment management
- Platform APIs and portals (Backstage, Port, or a lighter approach) where they earn their keep
- Operating model: what the platform team owns, what product teams own
Example engagement
Internal developer platform for a product company with eight teams
Started from the three questions every team asked the platform group most, built a service template and an onboarding flow that answered them without a ticket, added a lightweight catalogue, and moved teams over one at a time while measuring onboarding time drop from days to under an hour.
Representative of the work; client details are not published.
Technologies
- Backstage
- Port
- Crossplane
- Argo CD
- Helm
- Terraform
- GitHub Actions
- Azure DevOps
How we think about it
Platform engineering · GitOps · CI/CD · 7 min
Golden paths that engineers actually take
A platform team's output is not the platform; it is the paths other teams take through it. How to build paved roads that are faster than the alternative, keep them honest with the people who use them, and avoid turning them into mandates.
Kubernetes · Security · Platform engineering · 8 min
Isolating tenants on a shared Kubernetes cluster
A namespace is not a security boundary, but a namespace plus five other controls is a usable one. What separates tenants on a shared cluster, what still needs a cluster of its own, and how to decide which customer gets which.
Observability · Platform engineering · 7 min
SLOs before dashboards
Observability tooling is easy to buy and hard to make useful. Start from what the service promises, measure it from the user's side, and let the alerts, the dashboards and the on-call rota follow from the promise rather than from what the tools export.
Before you write to us
The questions we get asked first.
Answered the way we would on a call. The consulting FAQ covers how engagements work in general.
- What is the first thing a platform team should build?
- One path, for the thing most teams need most often: a new service from repository to a running, observed, secured workload. Measured end to end, made faster than the alternative, and maintained as a product with users. A second path is justified when the first is quiet.
- How do you stop the platform becoming a mandate teams route around?
- Dogfood it, publish its service level, and keep the escape hatch visible rather than forbidden. The reasons teams step off the path are the roadmap; a path that cannot be left is a mandate, and mandates get routed around in ways you only see at the audit.
- What access do you need?
- Read access to the current delivery path end to end: repositories, pipelines, deployment tooling and the cluster, and a few hours of the team's time. Nothing is run under your production credentials from outside your own tooling, and write access only arrives with an implementation phase, through your pipeline and your review.
- Who does the work?
- Senior engineers who have run this kind of estate, working in your repositories, pipelines and rituals. There is no hand-off from a sales team to a delivery team: the people on the first call are the people on the engagement.