Knowledge base
Everything we build is documented before it is handed over. This page explains what exists, how it is organized, how you get access, and where to start.
What the knowledge base is
The BuiltForProd knowledge base is docs.builtforprod.com: the documentation set delivered with every engagement and kept current after it. It is not a marketing library. It is the manual for the platform in your accounts, written so that a second engineer can operate the system safely without asking the first one.
It holds architecture pages and design decision records, how-to guides, operations runbooks, troubleshooting entries organized by symptom, upgrade guides, a compliance and audit-readiness section, scaling guidance and a full reference. The AWS Enterprise Baseline set alone is 271 pages, and the customer-facing documentation across the platform and the three Blueprints runs to several hundred more.
Two things make it usable rather than decorative. Every page is personalized to your organization, and every code snippet is pulled from the real repositories and pinned by content hash, so the build fails rather than publish stale code.
How it is organized
One public set, then one set per product. A set is a complete manual, not a category.
| Set | Path | Access | What it holds |
|---|---|---|---|
| Platform | /platform/ |
Public. Indexed by search engines, readable without signing in. | Concepts, the Standard, product pages, the glossary, release notes, trust pages and the FAQ. |
| Baseline edition | /aws/baseline/, /azure/baseline/, /gcp/baseline/ |
The overview section is public. The rest needs sign-in and the matching product entitlement. | Architecture, accounts, networking, identity, security, compliance, pipelines, runbooks, upgrades and reference. |
| Blueprint | /aws/blueprints/webapp/, /etl/, /secrets/ |
The overview section is public. The rest needs that Blueprint entitlement. | The architecture, the code, the pipelines, the procedures and the reference for that workload. |
The Baseline comes in three editions, the AWS, Azure and GCP Enterprise Baselines, each measured against the same BuiltForProd Standard and each with its own documentation set. Blueprints are listed in the catalog at docs.builtforprod.com/blueprints/.
Personalized to your organization
Sample values become your values, in your browser, on every page.
| Value | Sample | Where it appears |
|---|---|---|
| Organization abbreviation | acme, ACME |
Resource names and single sign-on group names |
| GitHub organization | your-github-org |
Every repository reference |
| Primary domain and internal zone | company.com, internal.company.com |
Zone names and hostnames |
| Home region and slug | us-west-2, usw2 |
Region-specific resource names |
| Account ids | 111111111111 and the rest |
Account references in commands and policies |
Substitution happens in your browser
The pages themselves, the search index and any screenshot contain only the sample values. Nothing is rendered on the server with your organization's values in it, and the account ids in a profile are identifiers, not credentials. See privacy and data handling.
How to get access
- Your organization is created at purchase. BuiltForProd staff create the organization and set the product entitlements it holds when a purchase completes. You cannot grant an entitlement to yourself, and no entitlement is needed to read the Platform set or any product overview.
- Sign in from the navigation bar. One sign-in opens every product your organization holds. If you open the root of a gated set without the product, you are redirected to its public overview rather than shown an error.
- An admin invites the team. Organization admins invite colleagues from the same email domain and set their roles.
- An admin fills in the organization profile once. Namespace, GitHub organization, domains, home region and account ids. Every page then reads in your own names.
Lost access, or nobody left who is an admin? Contact us and we will re-establish it. The getting started page describes where this sits in the delivery flow.
How to search
Search is scoped to the set you are reading: on a Baseline page the Baseline set is searched first, on a
Platform page the Platform set. The index holds the sample values, not your own, so search for
acme-usw2-dev-eks rather than the cluster name the page is showing you.
Every page ends with two generated blocks: What's next, the one to three pages to read after this one, and Related topics, the pages that cover the same ground from another angle. Following What's next from a set's first page reads the set in order.
Start here
Public pages. No sign-in, no entitlement, no form.
What is BuiltForProd
The one-page answer, written for someone who has never seen the platform.
How to use these docs
Sets, sign-in, placeholders, search and the page conventions.
Reading paths by role
Which pages a platform lead, a developer, an auditor or an executive should open, in order.
Prerequisites
The six things your organization needs to own before a deployment starts.
Key concepts
Landing zones, units and stacks, promotion, drift and least privilege, defined once.
The BuiltForProd Standard
The eight properties and the test each one applies, with a page per property.
Glossary
Every acronym and every AWS service the platform uses, each with its own explainer.
Release notes
Pinned tool versions, the versioning policy, upgrade guides and deprecation notices.
Product overviews
AWS Enterprise Baseline overview
What you receive, the architecture, the service inventory and the pinned versions.
Web App Blueprint overview
A working front end and back end on Amazon EKS, with DocumentDB, ElastiCache, CloudFront and ArgoCD.
Data and ETL Blueprint overview
An S3 data lake governed by Lake Formation, with Glue jobs and an event-driven Lambda trigger.
Secrets Blueprint overview
Secrets encrypted with SOPS under AWS KMS and synced to SSM Parameter Store.
Each overview section is public and holds four pages: what you receive, the architecture overview, the service inventory and the pinned versions. The rest of the set opens with the entitlement.
Trust and answers
Trust pages
Documentation FAQ
Our own summaries of the same ground are on the FAQ, security and ownership and compliance readiness.
What is not published there
- Deployment procedures, bootstrap steps and credentials. Customer pages describe the platform and how to operate it. The steps BuiltForProd runs to stand it up stay internal.
- Service level figures. Response times live in your customer agreement, not on a web page. The terms they use are defined under SLA definitions.
- Prices. Engagements are quoted per customer. Pricing explains what shapes a quote.
- Anything from another customer. An organization's profile is readable only by its own members.
Knowledge base questions
What is the BuiltForProd knowledge base?
The BuiltForProd knowledge base is the documentation site at docs.builtforprod.com, organized as one public Platform set plus one set per product you hold. It covers architecture, design decisions, how-to guides, operations runbooks, troubleshooting, upgrade guides, compliance evidence and a reference section, and it is written to be operated from rather than read once.
Which documentation is public and which needs sign-in?
The Platform set is entirely public and indexed by search engines, and every product set publishes its overview section publicly. The rest of a product set needs sign-in and the matching entitlement, and gated pages are served with no-store and noindex headers so they are never cached or listed.
How do I get access to my product documentation?
BuiltForProd staff create your organization and set its product entitlements when a purchase completes, and you sign in from the navigation bar on docs.builtforprod.com. An organization admin can then invite colleagues from the same email domain and can fill in the organization profile that personalizes every page.
Are the code samples in the documentation real?
Yes. Every code snippet is pulled from the real repositories and pinned by content hash, so the documentation build fails rather than publish a sample that has drifted from the code. Configuration is shown as it appears in the repository, with a caption naming the file.
Does the documentation show my own account ids and domains?
Yes, once an organization admin fills in the organization profile. Sample values such as acme, company.com and us-west-2 are replaced in your browser with your own namespace, domains, region and account ids; the published pages, the search index and any screenshot contain only the sample values.
How do I search the documentation?
Search is scoped to the set you are reading, so a Baseline page searches the Baseline set first and a Platform page searches Platform. The index holds the sample values rather than your own, so search for the sample resource name (acme-usw2-dev-eks) rather than the name you see on the page.
Want to see the documentation before you buy?
The Platform set and every product overview are public. Read them, then tell us what you are running and we will tell you what we would build.