01
Every environment and deploy request still requires platform translation — no paved golden paths.
Case 20
Developer Platform Interface
A golden-path door teams walk through: catalog, templates, and requests in front — GitOps, policy, and ownership kept behind the door.
01
How it works
Open the golden path — keep the basement.
Developer Platform Interface by Andrey Lesnikov — self-service that ships without surrendering platform control.
-
01
Show what exists
A service catalog beats tribal knowledge — teams see the paved options first.
-
02
Start from templates
Scaffolds encode the golden path so the default is the safe path.
-
03
Request without ticket archaeology
Clear request paths — IDP or structured tickets — replace hallway provisioning.
-
04
Ship through the door
Behind it: GitOps, policy, observability — platform ownership stays intact.
02
Evidence
From problem to proof.
How the system is framed, operated, and proven — not a slide deck summary.
02
The blocker is cluster foundations or GitOps topology, not the developer-facing interface.
03
EKS Platform Foundation and Argo CD App of Apps underpin paved paths. Terraform Platform Modules keep the underlying product consistent.
Constraints
Self-service boundaries, golden paths, ownership, auditability, and avoiding an unmaintainable portal.
03
Related
Nearby systems.
EKS Platform Foundation
Kubernetes clusters become inconsistent when networking, identity, ingress, storage, and observability are assembled per project
Clusters as a repeatable product
Argo CD App of Apps
As platforms grow, application onboarding, add-ons, and environment drift become hard to reason about
Platform bootstrapable from Git
Terraform Platform Modules
Cloud platforms drift when teams copy infrastructure snippets and adjust them under delivery pressure
Infra changes as reviewable product PRs
Available for meaningful infrastructure conversations