Cloud Build
Infrastructure as a Conversation, with Nora
One flow, guided by Nora, our AI agent: plan the environment, see what it costs, review the architecture, and ship it. Pre-sales teams follow the same four stages to a priced proposal instead.
1
Plan
The brief Nora reads
2
Cost
Every service, priced
3
Diagram
The architecture, live
4
Compose
Shipped as infrastructure
For sales & pre-sales teams
4 Generate Proposal
After Diagram, generate a priced proposal instead of composing infrastructure — nothing is deployed.
STAGE 1
Plan
This is the project brief where you add the project artifacts, requirements, and instructions for Nora to read and use to build the cloud infrastructure environment.
What Nora reads from the brief
Requirements
Workload, target clouds, and a budget ceiling.
Service levels
Availability, latency, RPO and RTO — each one constrains the design.
Notes
What matters to the customer, pulled from calls and RFPs.
Open questions
Nora asks questions when unsure.
STAGE 2
Cost
The cost breakdown is shown for all the different cloud services needed. Work with Nora to reduce costs and see how it impacts the Diagram.
Every resource, grouped by category
Compute
largest share
Network
load balancer, egress
Storage & backup
driven by RPO
Observability
alerts, from your SLOs
Every resource on the diagram appears here once, with its share of the monthly total against your budget ceiling — so the expensive decisions are obvious before you move to Diagram.
STAGE 3
Diagram
Users can see the exact architecture and work with Nora to fine-tune or reduce costs.
Every part carries its own cost
Internet
Load balancer
Foundation · 1 subnet
Σ sum of everything inside
App tier
2 instances
2 instances
Database
private subnet
private subnet
Every part of the diagram carries its own monthly cost, and every container sums what's inside it — so the expensive branch of the architecture is visible without opening the Cost stage. Compare up to three scenarios side by side as Nora forks and re-prices the design.
STAGE 4
Compose
The whole design is converted into deployable infrastructure as code.
Generated manifests, validated before deploy
Manifests
network.yaml
instance.yaml
policy.yaml
Generated from the design
Validated against the manifest
Deploy — blocked until validation passes
Manifests can be edited directly, or through Nora. Once a manifest is already deployed, an edit lands as a commit in the repo — never a silent overwrite — so infrastructure and design stay in sync.
For sales & pre-sales teams
Generate a proposal, instead of Compose
At Stage 4, sales and pre-sales teams generate a proposal instead of composing infrastructure. Nora assembles a complete, ready-to-send document from the same Plan, Cost and Diagram — cover, executive summary, recommended environment, cost summary, alternatives considered, and terms — with nothing deployed.