Architecture Review¶
Architecture Review evaluates a described architecture for cost, service mapping, resilience, compliance, and improvement opportunities.
Open Architecture Review¶
Go to Architecture > Architecture Review.
Run a review¶
- Enter a focused request in the prompt box. The UI suggests asking CloudVerse to estimate cost, map services, or assess resilience and compliance.
- Add the provider, target region, and other scope options shown for the review.
- Attach the supported architecture artifact when the upload control is available.
- Submit the request.
- Follow the Review thread as CloudVerse returns analysis.
- Review Key findings, estimates, mapped services, risks, and recommended next steps.
- Download or open the generated artifact when Artifact ready appears.
Prompt examples¶
Estimate the monthly cost of this AWS architecture in us-east-1 for 10 million API requests per month, 2 TB of data transfer, and a three-node production database.
Review this Azure architecture for resilience gaps and identify lower-cost service or region alternatives that preserve the same availability target.
Review outputs¶
| Output | Use it for |
|---|---|
| Cost estimate | Compare design choices before provisioning. |
| Service mapping | Confirm that the proposed architecture uses the intended provider services. |
| Resilience notes | Find single points of failure and missing failover assumptions. |
| Compliance notes | Identify data residency, encryption, network, or access-control questions. |
| Recommendations | Create engineering follow-up items with estimated impact and risk. |
Best practices¶
- State workload scale, availability goals, data residency, and traffic assumptions.
- Use exact region names, such as those accepted by the region field.
- Validate generated estimates against current provider pricing and your negotiated discounts.
- Have architecture, security, and finance owners review material decisions.
Generated findings are decision support, not automatic approval to change production architecture.