Service 01 · Cloud Architecture

A cloud that is drawn before it is built.

We design AWS accounts, networks and landing zones around how your team works, then write the decisions down so audits and new hires are easy.

  1. Accountsprod apart from test
  2. Networksubnets across AZs
  3. Workloadscompute and data
  4. Guardrailspolicies, budgets
What you get

What lands on your desk.

Landing zone

A multi-account layout with sensible separation between production, test and shared tooling.

Network plan

Address ranges, subnets and routing that leave room to grow.

Security baseline

Identity, logging and guardrails switched on from day one.

Decision log

Every trade-off written down, so the reasons outlast the people.

How it works

Four steps, drawn as we go.

  1. 1

    Review

    We read what exists and talk to the people who run it.

  2. 2

    Draw

    A target architecture, on one page, in plain language.

  3. 3

    Agree

    We walk through the trade-offs and settle them together.

  4. 4

    Hand over

    Diagrams, code and a decision log you keep.

Tools we use

What is on the bench.

Engagement types

Three ways to work together.

We agree scope and price after a conversation, so there are no numbers on this page.

One-off

A defined piece of work with a clear end: a design, a build or a review.

Retainer

A set amount of senior time each month for changes, advice and reviews.

Managed

We run it day to day, with monitoring, alerts and support included.

Related blueprint 01

Serverless contact pipeline

How this site takes a message from a visitor to our inbox, logs it, and tells us if that ever stops working.

Read the blueprint →
Sheet 06 · Start here

Got a messy cloud? Let's draw it out.

Tell us what's broken or what you're planning. We reply within 48 hours.

no sales script, just a drawing

What do you need?

We reply within 48 hours.

FILED

Thanks. Your note is on the sheet and we will be in touch.