Skip to content
Build

Platform engineering

A path to production your developers will actually use — templates, environments and guardrails built on what you already run, not a platform you must migrate onto.

Every team invented their own way to ship

Three services, three pipelines, three opinions about secrets. Onboarding takes a fortnight because the knowledge is in people rather than in templates. Someone proposes an internal developer platform, and the proposal quietly becomes a migration project that competes with the roadmap.

What the work involves

  • A golden path for the common case — new service, new environment, new deploy — built from the tools you already run.
  • Environment strategy that survives contact with reality: what is ephemeral, what is shared, what the cost of each actually is.
  • Guardrails as defaults rather than policy documents: sensible resource requests, required probes, image provenance, secret handling. a build output mounted from EFS instead of shipped in the image →
  • Self-service where it pays for itself, and deliberately not where the ceremony would cost more than the request.
  • Documentation a new engineer can follow alone, which is the only honest test of a platform.

How the work goes

  1. Listen

    Interviews with the people who ship, plus a look at what actually happens between commit and production today — including the manual steps nobody mentions.

  2. One path

    We build a single service end to end on the new path, with a real team, and fix what that exposes before anything is generalised.

  3. Generalise

    Templates, docs and defaults extracted from the working example. Adoption stays voluntary: a golden path that needs enforcement is not golden.

Is this the right call?

A good fit when

  • Engineering teams past the point where everyone knows how everything works
  • Organisations that want a platform without a platform migration

Not us when

  • Buying a ready-made internal developer platform — that is a product purchase, and we will say so
  • Teams of three, where a shared README beats a platform