Compliance
Controls, evidence and audits, treated as an output of infrastructure rather than a project.
This blog exists to make one phrase mean something concrete: production-ready. Every post takes one property of a production system and shows what it costs to have it, and what it costs not to.
Software got easy to build and hard to run. Most teams reach production by accident: the prototype works, the MVP ships, and security, observability, recovery and compliance are added later, each one after it was already needed. BuiltForProd treats production as a standard instead of a phase — eight properties designed in from the start.
That standard is public, and so is the reasoning behind it. This blog is where the reasoning gets written down: the account boundaries, the credential model, the restore drill, the review gate, the evidence an auditor asks for. If a post cannot be acted on by someone who will never be our customer, it is not finished.
Every post maps to at least one of these. They are the same eight the Standard defines, and the same eight our own work is reviewed against.
| Property | What it means | The test |
|---|---|---|
| Secure | It protects identities, data, workloads and supply chains. | Is it secure by default? |
| Reliable | It keeps operating through expected failures. | What happens when something fails? |
| Observable | Its state and behavior are visible to operators. | Can operators see what is happening? |
| Scalable | It grows predictably without architectural failure. | What happens when demand grows 10x? |
| Automated | Provisioning, deployment and validation repeat without heroics. | How much depends on manual intervention? |
| Recoverable | Recovery is engineered and tested, not assumed. | Can the system actually be restored? |
| Compliant | Controls and evidence can be demonstrated on demand. | Can controls and evidence be demonstrated? |
| Operable | A second engineer can run it, safely, at 3 AM. | Can another engineer operate it safely? |
Controls, evidence and audits, treated as an output of infrastructure rather than a project.
Account boundaries, networks and topology: the decisions that are expensive to change later.
Identity, credentials, guardrails and the boundaries that hold when something goes wrong.
Infrastructure as code, drift, state and the repositories an engineering team actually lives in.
Pipelines, review gates and promotion: how a change reaches production without a hero.
What production engineering costs, what skipping it costs, and how to argue either case.
Day 2: running a system, handing it over, and being woken by it without dreading the call.
Failure you planned for, recovery you have rehearsed, and the difference between the two.
The best posts here started as a question someone was living with: a security questionnaire they could not answer, a restore nobody had tried, a deploy that only one person could run. If that is you, send the question rather than the keyword.
Useful pitches say three things:
We reply to every message. If we do not know the answer well enough to write it, we will say so, and usually point at someone who does.
The BuiltForProd engineering team writes them, drawing on the systems we build and hand over. Posts are published under the BuiltForProd byline because they are reviewed by more than one engineer before they ship.
No. Every post is written so an engineer can act on it without buying anything. Posts end with the option to book a 30-minute call with an engineer, and that is the extent of it; the blog itself is still not a pitch.
Yes. Book the call at https://builtforprod.com/meet/: it is 30 minutes, with an engineer who scopes engagements, not a salesperson. Bring what you run and the post that prompted the question. If you want a written, evidence-based answer instead of a conversation, the BuiltForProd Assessment exists for that.
Concrete figures describe a real system, usually the AWS Enterprise Baseline, and are labeled that way in the text. We do not publish customer counts, testimonials or benchmark numbers we cannot show the workings for.
Weekly during a campaign and roughly every two weeks otherwise. Posts are written ahead and scheduled, and the site rebuilds on a schedule so a dated post goes live without anyone pressing anything.
Quote freely with a link back to the original. For a full republication, email [email protected] and we will agree a canonical link so the two copies do not compete in search.
Email [email protected] with the question you want answered and the situation behind it. The best pitches are a problem you are living with right now, not a keyword.
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.