Skip to content
Build

Infrastructure design

Networks, accounts, identity and data paths designed to be auditable later — including the question most designs postpone: what this will cost at three times the traffic.

The design that was right for ten people

Account structure, network layout and identity are decided once, early, by whoever was there — and then everything is built on top of them. By the time the shape is wrong, changing it means touching everything, so instead it gets worked around, and each workaround becomes another thing to explain to an auditor.

What the work involves

  • Account and environment structure that matches how the organisation actually works, including who is allowed to spend money. an illustrative upgrade programme across several clusters →
  • Network design with the data paths drawn explicitly — cross-zone, egress and inter-service traffic are a cost and a risk, not an implementation detail.
  • Identity and access designed to be reviewable: roles that a person can explain, and no long-lived keys where a role would do.
  • Cost at scale as a design input: what this shape costs at three times the traffic, computed during design rather than discovered later.
  • Auditability built in from the start — control-plane logging, retention, and evidence that can be produced without an archaeology project.

How the work goes

  1. Constraints

    Regulatory obligations, data residency, team topology, budget. The design is a response to these, and writing them down first prevents the usual argument later.

  2. Design

    Diagrams plus the decisions behind them, including the options rejected and why — the part that is worth the most in two years.

  3. Land it

    Infrastructure as code in your repository, applied in stages, with the first environment built together so your team owns it afterwards.

Is this the right call?

A good fit when

  • Greenfield estates, or a re-platform where the old shape has run out
  • Companies about to enter a regulated market or a first enterprise deal

Not us when

  • A diagram for a slide deck with no intention to build it