Skip to main content

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 cloud environment deployed into your own cloud by BuiltForProd's engineering team, a full handover of the customized Git repositories and infrastructure code, and the documentation to run it: architecture decision records, how-to guides, troubleshooting manuals, FAQs and scaling best practices. What the environment contains depends on the edition:

  • AWS Enterprise Baseline: an AWS Organization with fifteen accounts in two organizational units, hub-and-spoke networking, IAM Identity Center, security services delegated to a security account, compliance monitoring and a plan-review-apply pipeline.
  • Azure Enterprise Baseline: a management group hierarchy with 15 subscriptions in your Microsoft Entra tenant, a hub VNet with Azure Firewall, Entra groups with Conditional Access, Azure Policy guardrails, Defender for Cloud in every subscription and a plan-review-apply pipeline with federated identities; see what you receive.
  • GCP Enterprise Baseline: a Google Cloud organization with 15 projects in three folders, a Shared VPC with one network per isolation domain, Google groups with Privileged Access Manager, organization policies, Security Command Center and a plan-review-apply pipeline through Workload Identity Federation; see what you receive.

The Baseline product page lists the deployment options.

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. Each edition has three, built with its cloud's services, and the blueprint catalog lists every one with the cloud it runs on:

  • Web App Blueprint: a Flask API and a React single-page app with ArgoCD delivery; on AWS with EKS, DocumentDB, ElastiCache and CloudFront; on Azure with AKS, Front Door, Cosmos DB for MongoDB vCore and Azure Managed Redis; on GCP with GKE, Cloud Armor, Cloud Run, Firestore and Memorystore for Valkey.
  • Data and ETL Blueprint: an event-driven data platform; on AWS an S3 data lake with Lake Formation, Glue and a Lambda trigger; on Azure Data Lake Storage with Azure Databricks and Unity Catalog; on GCP Cloud Storage with Dataproc Serverless, BigQuery and an Eventarc-driven trigger.
  • Secrets Blueprint: application secrets encrypted with SOPS under one key per stage and synced on merge; on AWS with KMS to SSM Parameter Store, on Azure with Key Vault keys to Key Vault, on GCP with Cloud KMS to Secret Manager.

Each is delivered as repositories with code, pipelines and documentation; see Blueprints.

Do I own the result?​

Yes. The repositories and the cloud environment they deploy 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 environment 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, Azure and Google Cloud. The Baseline comes in three editions, the AWS, Azure and GCP Enterprise Baselines, each measured against the same BuiltForProd Standard. Blueprints are built for a specific cloud, and the blueprint catalog lists each one with the cloud it runs on.

How is this different from Cloud Posse or AWS Control Tower Account Factory for Terraform?​

For the AWS edition, 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. Every edition is delivered the same way.

Is it opinionated?​

Yes, deliberately. The repositories encode decisions: one address plan, isolation domains between prod and non-prod, no long-lived credentials for people or pipelines, 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?​

The same tools in every edition: OpenTofu and Terragrunt for infrastructure, GitHub Actions with OIDC federation for CI/CD, ArgoCD and Helm for the web application, SOPS with each cloud's key service (AWS KMS, Azure Key Vault, Cloud KMS) for secrets, and Checkov, Trivy and tflint for scanning. The pinned versions are on the release notes page and on the versions pages of the Azure and GCP editions.

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.