Skip to content

Production engineering, written down.

What production-ready actually means, and what it takes to get there. Specific, technical, and honest about the trade-offs — including the ones that make our own work harder.

Recent posts

CMMC 2.0 for defense suppliers

CMMC Level 1 and Level 2 decide whether a supplier can hold the contract. Here is what infrastructure covers, what it cannot, and where it gets hard.

Zero trust access for engineers

How people should reach production: federated sessions instead of users, no long-lived keys anywhere, and access that ends the day someone leaves.

Every post, by year →

Subject areas

These are the subject areas we write about most.

  • Compliance

    Controls, evidence and audits, treated as an output of infrastructure rather than a project.

    8 posts

  • Architecture

    Account boundaries, networks and topology: the decisions that are expensive to change later.

    7 posts

  • Security

    Identity, credentials, guardrails and the boundaries that hold when something goes wrong.

    6 posts

  • Cost

    What production engineering costs, what skipping it costs, and how to argue either case.

    1 post

  • Delivery

    Pipelines, review gates and promotion: how a change reaches production without a hero.

    1 post

  • Operations

    Day 2: running a system, handing it over, and being woken by it without dreading the call.

    1 post

  • Platform

    Infrastructure as code, drift, state and the repositories an engineering team actually lives in.

    1 post

  • Reliability

    Failure you planned for, recovery you have rehearsed, and the difference between the two.

    1 post

What this blog is

BuiltForProd builds production-grade cloud foundations and the reference architectures that run on them. This blog is where the thinking behind that work is published: the account boundaries, the credential model, the restore drill, the review gate, the evidence an auditor asks for. Every post is written so an engineer can act on it without buying anything.

Where a post uses concrete numbers, they describe a real system — usually the AWS Enterprise Baseline — and they are labeled as such. Where something is a judgment call, it says so. Where we would tell a customer not to do the work yet, we say that too.

When a post describes a gap you recognize, the BuiltForProd Assessment is the paid, evidence-based version of the same question: findings, priorities, a future-state architecture and a migration plan, in about two weeks, with up to 50% of the fee credited toward a Baseline.

What we write about, and how to pitch a topic →

Find out what production would take.

A 30 minutes call with an engineer who scopes engagements, not a salesperson. Tell us what you run and what is coming: a funding round, an audit, a first enterprise customer, a migration. You leave with a next step, a fixed fee, or an honest no.

The invite goes to this address. Prefer to write? Send a message.