General FAQ
The questions customers ask before and after buying, answered from the offerings note, the brand note and the repositories.
What is BuiltForProd?
BuiltForProd is a production engineering company and brand of Nexstella, positioned as "BuiltForProd by Nexstella". It sells three things: BuiltForProd Baseline, a production-ready multi-account cloud foundation as infrastructure as code; BuiltForProd Blueprints, opinionated reference architectures for real workloads that deploy on the Baseline; and BuiltForProd Managed, DevOps-as-a-Service for maintenance, support and staff augmentation. The philosophy behind all three is that production is a standard, not a phase; see what is BuiltForProd.
What exactly do I receive with the Baseline?
A complete multi-account AWS environment deployed into your own AWS accounts by BuiltForProd's engineering team, a full handover of the customized Git repositories and infrastructure code, and extensive documentation: architecture decision records, how-to guides, troubleshooting manuals, FAQs and scaling best practices. The AWS Baseline repository builds an AWS Organization with fourteen accounts in two organizational units, hub-and-spoke networking, centrally managed identity, security services delegated to a security account, compliance monitoring and a plan-review-apply pipeline. The Baseline product page lists the deployment tiers.
What is a Blueprint?
A Blueprint is a production-ready reference architecture for a specific workload, deployed on the Baseline so that your team builds the application rather than the platform. Three exist today: the Web App Blueprint (a working frontend and backend on EKS with DocumentDB, ElastiCache, CloudFront and ArgoCD), the Data and ETL Blueprint (an S3 data lake with Lake Formation, Glue and an event-driven Lambda trigger), and the Secrets Blueprint (SOPS with AWS KMS, synced to SSM Parameter Store). Each is delivered as repositories with code, pipelines and documentation; see Blueprints.
Do I own the result?
Yes. The repositories and the AWS accounts are yours. The code is licensed under the Polyform Internal Use License: you may deploy, modify and share it inside your organization; you may not resell it, publish it or use it to provide managed services to third parties. BuiltForProd holds no access to your accounts after handover unless you engage Managed.
Who is BuiltForProd for?
Startups, small and medium-sized businesses and large enterprises that need a secure, production-ready cloud foundation without spending months engineering it, that need to scale across accounts, regions and environments, or that have an MVP moving to production. The brand note is equally direct about who it is not for: teams still searching for product-market fit with nothing at stake, prototypes, demos and internal experiments, teams that want the cheapest fix for one symptom, or teams that want extra hands without adopting a standard.
Which clouds are supported?
AWS today: the AWS Enterprise Baseline and the three Blueprints are production-ready repositories. The offerings note states that Azure and GCP baselines, and more Blueprints, are the next phase after go-to-market. No dates are given.
How is this different from Cloud Posse or AWS Control Tower Account Factory for Terraform?
The offerings note describes the Baseline as conceptually similar to Cloud Posse architectures and to AWS Control Tower Account Factory for Terraform, but delivered as a turnkey customized product: BuiltForProd's team customizes the repositories for you and deploys them into your accounts, then hands over the code and documentation.
Is it opinionated?
Yes, deliberately. The repositories encode decisions: one address plan, isolation domains between prod and non-prod, no IAM users, immutable image tags, a fixed promotion order. Every deployment-specific value is tagged TODO: and every optional choice is tagged @optional:, so you can see what must be set and what may be changed. The technical FAQ covers how customization works.
What tooling does it use?
OpenTofu and Terragrunt for infrastructure, GitHub Actions with OIDC federation for CI/CD, ArgoCD and Helm for the web application, SOPS with KMS for secrets, and Checkov, Trivy and tflint for scanning. The pinned versions are on the release notes page.
Where do I start?
The brand note's guidance: start with the Baseline if you need the foundation; start with Blueprints if the foundation exists and you need production-ready workload architecture; start with Managed if you need experienced engineers to operate production as an extension of your team. If you are unsure, BuiltForProd offers an assessment against the BuiltForProd Standard, and states that it will say so when it is not the right fit.