Define requirements
Define ownership, security expectations, budget boundaries and the outcome the cloud environment must support.
Book a demoStatepoint.Build
Design cloud environments with cost, control and delivery built in.
Turn requirements into cloud architecture with AI-assisted design. Review dependencies, policy and cost, then validate and approve the infrastructure for delivery.
Every environment keeps its approved intent, design, cost and delivery history.
Watch platform overview · 1:02
Azure architectureMRD-AZ-PRD-01vnet-meridian-prd10.30.0.0/16 · private AKS subnet
HTTPSPrivate endpointManaged identity
Application GatewayPublic HTTPS ingress
AKS clusterPrivate workload subnet
Azure PostgreSQLPrivate endpoint
Key VaultManaged identity access4 managed services3 verified relationshipsSoutheast Asia · Policy aligned
Azure Terraformmain.tf
resource "azurerm_application_gateway" "edge" {
name = "agw-meridian-prd"
resource_group_name = azurerm_resource_group.product.name
}
module "aks" {
source = "./modules/aks"
subnet_id = azurerm_subnet.workload.id
ingress_gateway_id = azurerm_application_gateway.edge.id
}
resource "azurerm_postgresql_flexible_server" "data" {
name = "psql-meridian-prd"
subnet_id = azurerm_subnet.data.id
}
resource "azurerm_key_vault_access_policy" "workload" {
key_vault_id = azurerm_key_vault.product.id
object_id = module.aks.kubelet_identity_id
}Architecture valid
Private data path verified
Budget policy passed
How Statepoint.Build works
Move from requirement to governed infrastructure without losing context.
Shape the architecture
Start from intent, a blueprint or visual design. The AI Infrastructure Copilot helps clarify requirements and propose an architecture for engineering review.
Validate the design
Review cost, policy, Well-Architected guidance, dependencies, software risk and generated infrastructure code before change reaches the cloud.
Approve and deliver
Approve and execute versioned infrastructure changes while preserving delivery evidence and the decision context established before provisioning.
What Statepoint.Build brings together
One workspace for the decisions behind every cloud environment.
Architecture, policy, cost and delivery stay connected from the first requirement through every approved infrastructure change.
Statepoint.Build
Governed project context
Keep owners, requirements, security plans and budget boundaries with the environment from the start.
Owners & requirements
Security plans
Budget boundaries
Business and engineering value
Control architecture, cost and change in one product lifecycle.
Statepoint.Build gives platform engineering, cloud architecture, security and FinOps one governed place to make decisions before provisioning and to execute approved changes safely.
Financial control by design
See cost implications and budget fit before resources are provisioned, while architecture choices are still easy to change.
Model → price → approveReusable platform standards
Turn approved architectures into versioned blueprints with policy, security and financial boundaries built in.
Standardize → reuse → governSafe, reviewable change
Validate dependencies and generated infrastructure code before executing approved changes through controlled delivery.
Validate → version → deliverDecision continuity
Keep architecture, cost and approval context attached to infrastructure change from design through controlled delivery.
Design → approve → deliverTraceability by design
Every infrastructure change keeps its design and financial context.
Requirements, budget choices, architecture versions, validation results and delivery artifacts remain connected. Teams can explain what changed, why it was approved and what it was expected to cost.
01
Governed intentOwners · requirements · security plan · budget
02
Design decisionArchitecture · cost model · policy checks
03
Versioned changeTerraform · approvals · delivery evidence
Frequently asked questions
Questions teams ask about Statepoint.Build.
Clear answers for teams evaluating how Statepoint.Build fits their infrastructure, governance and assurance workflows.
Does Statepoint.Build use AI?
Statepoint.Build’s AI Infrastructure Copilot is designed to help engineers express requirements in natural language, clarify intent and develop architecture proposals. Engineers review and refine the design with dependencies, policy and cost in context. Engineering logic—not free-form model output—governs validation and Terraform generation; people govern approval and delivery.
Do I need to be a Terraform expert to use Statepoint.Build?
No. Statepoint.Build lets teams work visually with cloud architecture, requirements, policies and cost context while producing reviewable Terraform. Familiarity with cloud infrastructure is useful, but users do not need to write every resource definition by hand.
How is Statepoint.Build different from using Terraform alone?
Terraform describes and provisions infrastructure. Statepoint.Build adds the governed context around that change: ownership, requirements, architecture decisions, cost expectations, policy checks, approvals and delivery evidence. The infrastructure code remains reviewable while the reason behind it stays attached.
Can Statepoint.Build bring an existing cloud environment under governance?
Yes. Statepoint.Build supports brownfield discovery as well as new environment design. Existing resources and relationships can be brought into a governed model, connected to owners and requirements, and evolved through controlled, versioned change.
Which cloud platforms does Statepoint.Build support?
Statepoint.Build supports governed cloud design and delivery across AWS, Microsoft Azure, Google Cloud and OCI, including supported managed Kubernetes foundations. Available design components and delivery artifacts are confirmed for your environment during evaluation. On-premises operating evidence is covered by Statepoint.Operate; it is not a claim of on-premises provisioning through Build.
Can teams understand cost before provisioning?
Yes. Financial impact and budget fit can be evaluated while the architecture is still being designed. This helps teams compare choices before committing to infrastructure, while keeping cost decisions with the approved design record.
Can we create reusable architecture templates and blueprints?
Yes. Approved architectures can become versioned, reusable blueprints with engineering, security and financial boundaries built in. Teams can standardize common patterns without losing the project-specific decisions that make each environment accountable.
How does Statepoint.Build control infrastructure delivery?
Statepoint.Build produces reviewable infrastructure changes, evaluates policy and dependencies, and preserves approval history. Your team authorizes delivery through the agreed controlled execution workflow; AI recommendations do not authorize changes. Supported delivery components and execution requirements are confirmed for your environment during evaluation.
How do Statepoint.Build and Statepoint.Operate work together?
Build’s AI Infrastructure Copilot helps shape architecture from requirements. Operate connects the running estate to current operating evidence. AI-powered Assurance brings that evidence together with design and control context to explain priorities and recommend responses. Engineering controls and people govern changes, and reassessment verifies the result.
How do Statepoint.Build and Statepoint.Operate handle container risk?
Statepoint.Build preserves the approved architecture and delivery context behind a workload. Statepoint.Operate connects registry, image, SBOM, package and vulnerability evidence to the running environment. Together, they help teams decide what should ship, understand what is running, approve action and verify the outcome.
How does the Statepoint.Build record support Assurance Intelligence?
Build’s Copilot helps develop architecture proposals; Assurance has a different role. It connects the design context, requirements and controls with operating evidence to explain priorities and recommend responses. The architecture record connects these two perspectives without making the AI the authority for validation or change.
Where is Statepoint deployed?
Statepoint is delivered as a dedicated instance in your nominated Azure subscription or AWS account. This is separate from infrastructure coverage: Statepoint.Operate connects cloud and on-premises evidence, while Statepoint.Build governs supported cloud design and delivery. Collectors, connectivity and supported components are confirmed for your environment during evaluation.
Statepoint.Build