Optimize¶
CloudVerse optimization turns billing, inventory, and telemetry into ranked savings actions. Each action should explain the resource, evidence, confidence, savings estimate, risk, and execution path.
Review rightsizing, idle cleanup, storage, scheduling, and provider-specific savings opportunities.
ML ML RecommendationsUse model-backed signals and generation jobs for advanced recommendations.
Compute Spot OptimizerFind workloads that can safely use Spot capacity with fallback and approval controls.
Placement SKU & Region OptimizerCompare equivalent SKUs, regions, and target shapes before changing workloads.
Licenses License OptimizerAnalyze cloud software licenses, entitlements, marketplace inventory, and license actions.
Commitments Commitment OptimizerPlan and execute committed-use discounts in the dedicated Commitments section.
Recommendation lifecycle¶
| Stage | What to confirm |
|---|---|
| Discovery | Required billing, inventory, and telemetry inputs are present. |
| Evidence | The recommendation includes enough utilization, cost, and ownership context. |
| Decision | Owners approve, dismiss, snooze, or route the action. |
| Execution | Approved actions go through workflows, automation, or manual change paths. |
| Verification | Realized savings and post-change state are reconciled. |
Safe optimization posture¶
Start with high-confidence, low-risk recommendations. Use approval-required workflows for production changes, commitments, Spot migrations, and destructive actions.