Resources
Guides written by the people who do the work.
How we approach real problems, in enough detail to use without us. 9 guides across 10 topics.
Start here
Four guides, in the order a platform gets built.
The ground first, then the code that shapes it, then the path that ships to it, then how you know it is working. About half an hour end to end.
- 01
Cloud architecture · Security · 7 min
Landing zones before the first workload
The account structure, identity, network and guardrails that every later decision rests on. What a landing zone has to settle, what it can leave open, and the order that avoids rebuilding it in year two.
- 02
Terraform · Cloud architecture · 9 min
Adopting Terraform on a brownfield estate without breaking production
Importing an existing cloud estate into Terraform is a sequencing problem. The order that keeps production safe, and the mistakes that make people give up halfway.
- 03
CI/CD · Security · GitOps · 8 min
A pipeline that proves what it ships
Scanning, software bills of materials, signatures and admission control are four separate controls that only mean something together. How to build a delivery path where the cluster refuses anything the pipeline did not vouch for.
- 04
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.
Cloud architecture
Account structure, identity, networking and the guardrails every later decision rests on.
Migration · Cloud architecture · 7 min
Migration by disposition, not by lift
A cloud migration that treats every workload the same ends up moving the problems with the servers. How to classify an estate into dispositions, plan the waves, and keep the business running while the ground moves.
Cloud architecture · Security · 7 min
Landing zones before the first workload
The account structure, identity, network and guardrails that every later decision rests on. What a landing zone has to settle, what it can leave open, and the order that avoids rebuilding it in year two.
Terraform · Cloud architecture · 9 min
Adopting Terraform on a brownfield estate without breaking production
Importing an existing cloud estate into Terraform is a sequencing problem. The order that keeps production safe, and the mistakes that make people give up halfway.
Kubernetes
Running clusters that several teams or several customers share, and knowing what is actually running on them.
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.
Kubernetes · Cloud cost · 8 min
Kubernetes rightsizing: where the money actually goes
Most Kubernetes clusters are paid for twice: once for the nodes and once for the requests that keep them half empty. A practical order for finding and fixing it.
CI/CD
Delivery paths that build, prove and promote a change without a person copying anything by hand.
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.
CI/CD · Security · GitOps · 8 min
A pipeline that proves what it ships
Scanning, software bills of materials, signatures and admission control are four separate controls that only mean something together. How to build a delivery path where the cluster refuses anything the pipeline did not vouch for.
GitOps · Platform engineering · CI/CD · 7 min
GitOps promotion without copying YAML between environments
Argo CD and Flux make deployments declarative; they do not by themselves solve promotion. How to move a change from dev to production with a record, a gate and no hand edits.
Terraform
Infrastructure as code on estates that already exist, with state, modules and pipelines that survive the team changing.
Cloud cost
Where the money goes in a cloud estate and the changes that reduce it without changing what the applications do.
GitOps
Git as the record of what runs where, and promotion as a change to that record rather than a hand edit.
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.
CI/CD · Security · GitOps · 8 min
A pipeline that proves what it ships
Scanning, software bills of materials, signatures and admission control are four separate controls that only mean something together. How to build a delivery path where the cluster refuses anything the pipeline did not vouch for.
GitOps · Platform engineering · CI/CD · 7 min
GitOps promotion without copying YAML between environments
Argo CD and Flux make deployments declarative; they do not by themselves solve promotion. How to move a change from dev to production with a record, a gate and no hand edits.
Platform engineering
Paved roads that product teams take by choice, maintained as products with users.
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.
GitOps · Platform engineering · CI/CD · 7 min
GitOps promotion without copying YAML between environments
Argo CD and Flux make deployments declarative; they do not by themselves solve promotion. How to move a change from dev to production with a record, a gate and no hand edits.
Migration
Classifying an estate, planning the waves and keeping the business running while the ground moves.
Observability
Objectives measured from the user's side, alerts that follow from them, and dashboards that come last.
Security
Controls that are enforced where they can be, proven continuously, and invisible when nothing is wrong.
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.
CI/CD · Security · GitOps · 8 min
A pipeline that proves what it ships
Scanning, software bills of materials, signatures and admission control are four separate controls that only mean something together. How to build a delivery path where the cluster refuses anything the pipeline did not vouch for.
Cloud architecture · Security · 7 min
Landing zones before the first workload
The account structure, identity, network and guardrails that every later decision rests on. What a landing zone has to settle, what it can leave open, and the order that avoids rebuilding it in year two.
SignalForge product updates are in the release notes and the roadmap.