01
Identify developer journeys, friction points and target personas
Apply this point to a real FinOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
FinOps Academy · Architecture Explorer
Platform Engineering Reference Architecture
Create an internal developer platform with paved roads, self-service workflows and measurable platform outcomes.
Objective: Reduce cognitive load while retaining security, governance, reliability and cost controls.
Practical guidance
Business context and requirements
02
Define platform products, service levels and adoption outcomes
Apply this point to a real FinOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
03
Prioritise reusable capabilities instead of one-off automation
Apply this point to a real FinOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
Practical guidance
Architecture and design decisions
01
Design the portal, service catalogue and workflow orchestration
Apply this point to a real FinOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
02
Create golden paths for code, infrastructure, deployment and operations
Apply this point to a real FinOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
03
Integrate identity, policy, secrets, observability and documentation
Apply this point to a real FinOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
Practical guidance
Security, cost and operating model
01
Apply secure defaults and auditable exception handling
Apply this point to a real FinOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
02
Define showback, platform capacity and product funding models
Apply this point to a real FinOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
03
Operate the platform through product management and reliability practices
Apply this point to a real FinOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
Practical guidance
Validation, resilience and evolution
01
Measure lead time, adoption, failure rate and developer satisfaction
Apply this point to a real FinOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
02
Validate escape hatches, rollback and support pathways
Apply this point to a real FinOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
03
Retire low-value capabilities and evolve golden paths from evidence
Apply this point to a real FinOps Academy design, delivery or operational scenario and record the evidence used to validate the outcome.