Platform engineering knowledge graph

Platform engineering, mapped.

Explore the systems, practices, and tools that turn infrastructure into a dependable product.

Explore the graphRead technical guides

GRAPH SCOPE

95 nodes

7 operating clusters, from developer experience to AI governance. Curated for production teams, not alphabetical completeness.

How to use this graph

Find a signal

Search aliases, sources, tools, or practices. Filters and production journeys narrow the graph and index together.

Inspect the node

Select any node for a practical definition, operating context, adoption signal, and deeper explanation.

Trace relationships

Arrowed, typed lines explain what enables, governs, secures, observes, or measures the selected node.

95 of 95 nodes

Trace a production journey

All platform capabilities and controls.

Relationship map

Follow the operating system

Use Tab to focus nodes, then Enter or Space to inspect one. Drag to pan and use the zoom controls to change scale. Edges point from the selected node toward related capabilities and use line style to identify the relation type.

Internal developer pla...Platform as a productGolden pathsPaved roadsDeveloper portalBackstageSelf-serviceCognitive loadTeam TopologiesService catalogTerraform and OpenTofu...PulumiCrossplaneLanding zonesPolicy as codeImmutable infrastructureDrift detectionSecrets managementInfracostGitOpsArgo CDFlux CDProgressive deliveryCanary releaseRollbackSoftware supply-chain ...Software bill of mater...KubernetesContainer Network Inte...Service meshKubernetes operatorsAutoscalingGPU schedulingKServeWorkload identityObservabilityOpenTelemetrySLI and SLOError budgetDistributed tracingIncident responseToilModel registryMLflowFeature storeEvaluation gatesLLM gatewayRetrieval-augmented ge...LLM guardrailsVector storevLLMFinOpsCost attributionFOCUSIdentity and access ma...EU AI Act evidencePII redactionData lineageGovernance as codePlatform capabilityPlatform metricsTeam APIPlatform APIProduction readiness s...Environment as a serviceCloud account vendingContinuous integrationArtifact provenanceArtifact signingArtifact attestationDependency healthFeature flagsKubernetes Gateway APIDynamic Resource Alloc...KueueeBPF networkingCluster multi-tenancyBurn-rate alertingTelemetry pipelineTail samplingChaos engineeringDisaster recoveryPrompt registryInference gatewayModel monitoringData quality gatesAgent harnessUnit economicsAI system inventoryHuman oversightPost-market monitoringMCP governanceCost anomaly managementSoftware Carbon Intens...OpenLineage
How to read the relation lines
EnablesImplementsDepends onGovernsObservesSecuresMeasuresAlternative toPart ofOften confused with

Searchable index

Every node, readable without the map

Internal developer platform

A curated self-service layer that lets product teams build and operate software without mastering every infrastructure subsystem.

ConceptAdopt

Platform as a product

Operating an internal platform with defined users, outcomes, discovery, roadmap, and adoption metrics.

PracticeAdopt

Golden paths

Supported, opinionated routes for common tasks such as creating, deploying, and observing a service.

PatternAdopt

Paved roads

Well-supported technology choices that teams are encouraged, but not always forced, to use.

ConceptAdopt

Developer portal

A searchable interface for ownership, documentation, templates, dependencies, and operational actions.

PatternTrial

Backstage

An open-source framework for developer portals, software catalogs, documentation, and templates.

ToolTrial

Self-service

Letting engineers complete approved platform actions on demand through automated interfaces.

PracticeAdopt

Cognitive load

The information and decision-making capacity engineers must hold to deliver and operate a system.

ConceptAdopt

Team Topologies

A model for organizing stream-aligned, platform, enabling, and complicated-subsystem teams around fast flow.

ConceptAdopt

Service catalog

A structured inventory of software components, owners, dependencies, lifecycle state, and operational metadata.

PatternAdopt

Terraform and OpenTofu ecosystem

Two distinct declarative infrastructure-as-code projects that share HCL workflows and much of the provider ecosystem.

ToolAdopt

Pulumi

Infrastructure as code using TypeScript, Python, Go, C#, and other general-purpose languages.

ToolAssess

Crossplane

A Kubernetes control-plane framework for composing and continuously reconciling cloud resources.

ToolAssess

Landing zones

Preconfigured cloud foundations for identity, networking, logging, policy, account structure, and cost controls.

PatternAdopt

Policy as code

Expressing and testing governance rules in versioned, executable policy.

PracticeAdopt

Immutable infrastructure

Replacing deployed infrastructure artifacts instead of modifying them in place.

PatternAdopt

Drift detection

Finding differences between declared infrastructure or configuration and actual running state.

PracticeAdopt

Secrets management

Controlling the creation, storage, distribution, rotation, and revocation of credentials.

PracticeAdopt

The map is a system, not a stack ranking.

Adoption signals show a sensible default for mid-market production teams. Your constraints, workload, and operating capacity still determine the right route.

Platform foundations

16 nodes. Product, team, and experience principles that make a platform useful.

Infrastructure and IaC

10 nodes. Repeatable environments, policy boundaries, identity, and infrastructure lifecycle.

Delivery and GitOps

14 nodes. Safe, observable paths from source control to production.

Kubernetes and runtime

13 nodes. Workload scheduling, networking, scaling, and production execution.

Observability and SRE

12 nodes. Signals, objectives, and operating practices for dependable systems.

MLOps and LLMOps

14 nodes. Release, evaluate, serve, and govern models and AI applications.

FinOps, security, and governance

16 nodes. Cost, access, evidence, and controls that keep platforms accountable.