Portfolio

Four ways to get to production

A foundation, the architectures that run on it, the engineers who operate it, and an honest read on where you are today. Every one of them is built to the same Standard.

What BuiltForProd sells

BuiltForProd is a production engineering company. It delivers four things: BuiltForProd Baseline, a production cloud foundation deployed into your own accounts; BuiltForProd Blueprints, production-ready workload architectures deployed into that foundation; BuiltForProd Managed, experienced engineers who operate and evolve the platform through your own access and pipelines; and the BuiltForProd Assessment, a measurement of your current system against the BuiltForProd Standard. All four are delivered as infrastructure as code in your repositories and your cloud accounts, and all four are built to the same eight properties.

Your product is unique. Your infrastructure problems aren’t. Every team eventually solves the same set of them; most solve them from scratch, one crisis at a time.

The portfolio

Build the foundation

BuiltForProd Baseline

A multi-account cloud foundation in OpenTofu and Terragrunt: identity, network, guardrails, security services, compliance controls and CI/CD. Customized for your organization, deployed into your accounts by our engineers, then handed over with the repositories and the documentation.

  • Three editions: AWS, Azure and GCP Enterprise Baseline
  • Deployed and verified, not downloaded
  • Start here if you have no production foundation
Build the solution

BuiltForProd Blueprints

Opinionated reference architectures for real workloads, deployed into the workload accounts of your Baseline. Each one is a working system, not a diagram: repositories, pipelines and a running environment.

  • Web Application, Data & ETL, Secrets
  • Read account and network facts from the Baseline
  • Requires a Baseline to deploy into
Run it with us

BuiltForProd Managed

Production engineers who operate, upgrade and evolve the delivered platform as an extension of your team. They work through your single sign-on groups, your pull requests, your CODEOWNERS and your pipelines. Nothing is applied from a laptop.

  • On-Demand, Support SLA or Team Augmentation
  • Upgrades are in scope
  • Access ends when you remove it
Find out where you are

BuiltForProd Assessment

An assessment of your current environment against the eight properties of the BuiltForProd Standard, ending in a prioritized gap list. It is the cheapest way to find out whether you need any of the above, and the fee is credited toward a Baseline purchase.

  • Measured against a published standard
  • A prioritized gap list you keep
  • If we are not the right fit, we say so

How they fit together

Each product assumes the one before it. Nothing is bundled that you do not need.

  1. 01

    Know where you are

    The Assessment measures your environment against the eight properties and returns a prioritized gap list. Some teams skip it because the gap is obvious.

  2. 02

    Build the foundation

    The Baseline creates the accounts, identity model, network, guardrails, security services and pipelines that every workload will depend on. This is the part that is expensive to retrofit.

  3. 03

    Put workloads on it

    A Blueprint deploys a complete workload architecture into the Baseline’s workload accounts. It reads account and network facts from the foundation instead of duplicating them.

  4. 04

    Operate it

    Your team operates the platform using the runbooks and documentation, or Managed engineers operate it with you through your own pull requests and pipelines.

Which one to start with

Start from the situation, not from the product.
Where you are Start with Why
Everything runs in one cloud account, built by hand Baseline The account model, identity and network are the expensive parts to change later.
A security questionnaire or audit deadline is in front of you Baseline Controls and evidence sources come from the foundation, not from a screenshot scramble.
You have a foundation and a new workload to launch Blueprints A working architecture in your accounts instead of a quarter of design work.
Production matters but nobody owns it full-time Managed Engineers who already know the standard the platform was built to.
Leadership wants an honest read before spending Assessment A gap list against a published standard, credited toward a Baseline.
You are not sure production is a problem yet Read the Standard Eight questions. If you answer all eight confidently, you do not need us.

True of everything we deliver

You own it

Your repositories, your cloud accounts, full source under the PolyForm Internal Use License 1.0.0. No runtime to rent and nothing in the code names BuiltForProd.

No standing access

After handover, BuiltForProd holds no principal and no credential in your environment. Managed engineers work only through access you grant and can remove.

Built to one Standard

Secure, reliable, observable, scalable, automated, recoverable, compliant, operable — each mapped to shipped controls you can check. Read the Standard.

Fixed fee

Deployments are quoted per engagement as a fixed fee and fully executed by our team. What shapes a quote.

Documented

Architecture decisions, how-to guides, runbooks, troubleshooting entries and upgrade guides, personalized to your own accounts, domains and region.

Honest fit

We publish who we are not for. If BuiltForProd is not the right fit, we will tell you. Compare the alternatives.

Questions about the portfolio

Do I have to buy all four?

No. Most engagements start with one. The Baseline is the foundation everything else assumes, Blueprints need a Baseline to deploy into, Managed is optional, and the Assessment is a way to decide before committing to any of them.

How engagements are priced

What is the difference between a Baseline and a Blueprint?

The Baseline is the foundation: the organization, accounts, identity, network, security services, compliance controls and pipelines that every workload sits on. A Blueprint is one workload architecture deployed into that foundation, such as a web application or a data pipeline.

What a Blueprint is

Do you run the environment after you build it?

Only if you ask us to. The default is handover: the repositories and the cloud accounts are yours and BuiltForProd keeps no standing access. BuiltForProd Managed is a separate, optional service for teams that want engineers to keep operating and evolving the platform with them.

How Managed works

Which cloud does this run on?

BuiltForProd Baseline comes in three editions: the AWS Enterprise Baseline, the Azure Enterprise Baseline and the GCP Enterprise Baseline. Each is engineered around its cloud provider’s own architecture framework, and all three are built to the same BuiltForProd Standard.

The three editions

What do we own at the end?

You own the repositories and the cloud accounts. The full source ships in your own version control under the PolyForm Internal Use License 1.0.0, built on open-source tooling such as OpenTofu, Terragrunt, Kubernetes and ArgoCD, and nothing in the code names BuiltForProd.

Ownership and access

How do we buy?

Every engagement is a fixed fee, quoted per engagement, and fully executed by the BuiltForProd team. You can buy directly against an invoice, or through an AWS Marketplace private offer so the purchase runs on your consolidated AWS bill.

Talk to us

Find out what production would take.

Tell us what you are running and what is coming: a funding round, an audit, a first enterprise customer, a migration. We will tell you what we would build, what it costs, and whether we are the right fit.