№ 001HomeRev. 26.08

Cloud and AI architecturesthat survive reality.

Architect-led engagements for enterprises navigating the gap between what AI vendors promise and what production demands. No decks without diagrams. No roadmaps without trade-offs.

Availability Q3 2026 · 2 slots
Local time--:--:--
OfficeCovent Garden · London
02 — Practice

Three areas, one architect.

Every engagement is led by the same senior architect who scoped it. Nothing is delegated down.

Plate 01Structure before surface. Form follows constraint.London · 2026
03 — Field Notes

Working notes from the practice.

Full archive · 5 notes →
  1. № 00526.08.05
    Multi-Cloud Architecture

    Multi-region does not mean redundancy

    A BigQuery dataset in the US multi-region lives in one of Iowa or Oregon. Not both. You bought quota, not resilience.

    2 min
  2. № 00426.08.05
    Security Architecture

    Private endpoints are not an exfiltration control

    Private connectivity controls where a caller can reach the API from. It says nothing about what they can do once connected.

    2 min
  3. № 00326.07.31
    Multi-Cloud Architecture

    Your data pilot is not temporary

    The word temporary, in an enterprise data platform, usually means permanent — but without the controls.

    3 min
  4. № 00226.07.22
    AI & GenAI Enablement

    Private cloud for AI is a data gravity decision

    The business case says security and compliance. The actual driver is usually that the data is already somewhere, and moving it is expensive.

    3 min
04 — Engagements

Three ways to work together.

Every engagement starts with a conversation about what is actually breaking. Scope follows from that, not the other way round.

AOngoing · 1–2 days per week

Fractional Enterprise Architect

Embedded architectural leadership without the headcount. Design authority, review gates, and the decisions that need someone senior in the room.

Best when architecture keeps getting deferred because nobody owns it.

BDefined scope · 8–12 weeks

Project-Based Consulting

A specific problem with a specific deliverable. Reference architecture, security patterns, IaC templates, runbooks, and the documentation to operate them.

Best when the destination is clear and the route is not.

CLight-touch · On call

Advisory Retainer

A second opinion on tap. Design reviews, vendor evaluations, and the calls you would rather not make alone.

Best when the team is capable and needs a sounding board.

Not sure which fits? That is usually the right place to start.

Currently taking on 2 engagements for Q3 2026