The Savings Report is available at two levels: an organization view that shows savings trends across all your clusters, and a cluster view that drills into a single cluster. Both views share the same underlying calculations — they group the data differently.

For the concepts behind the numbers — projected cost, baseline, realized savings, and workload autoscaler savings — see the Savings Report overview.

Shared elements

Both views include the same set of summary cards and charts, scoped to either your entire organization or a single cluster.

Overview cards

• Baseline spend — the modeled cost of running your cluster(s) without Cast AI.
• Realized savings — savings through the node autoscaler, including workload autoscaler impact when both are enabled. Appears only when the node autoscaler manages at least 20% of nodes (on at least one cluster in the organization view, or on the specific cluster in the cluster view).
• Workload autoscaler savings — modeled savings from the workload autoscaler. Appears when the workload autoscaler manages at least 20% of workloads in VPA mode.
• Actual spend — real spending over the selected period.

📘

Note

Realized savings and workload autoscaler savings appear independently. If neither autoscaler meets the adoption threshold, the corresponding card is hidden.

Savings over time

Shows realized savings and workload autoscaler savings trends across the selected period. Which lines appear depends on which autoscalers are adopted.

Workload autoscaler adoption

Shows the percentage of workloads managed by the workload autoscaler over time.

Workload utilization rate

Shows CPU and memory utilization (switchable between the two), helping you assess whether resources are being used efficiently.

Organization view

The organization view aggregates data across all clusters in your Cast AI organization. In addition to the shared elements above, it includes a per-cluster breakdown.

Breakdown by cluster

A table with one row per cluster, aggregated over the selected time range. For each cluster, you can see:

• Which optimizations are turned on (node autoscaler, workload autoscaler)
• Baseline source — how the baseline was determined for this cluster (see Savings baseline)
• Baseline cost — the modeled cost without Cast AI
• Actual cost — real spending for this cluster
• Savings — either realized or workload autoscaler savings, depending on which autoscalers are active

Click any cluster to drill into the cluster view.

Cluster view

The cluster view shows how much Cast AI has saved on a single cluster and where those savings come from. It adapts its sections based on which optimization components are active.

You can reach the cluster view by clicking a cluster in the organization-level breakdown table.

Node autoscaler impact

This section appears when the node autoscaler is active on the cluster, managing at least 20% of the nodes.

Provisioned capacity

Shows baseline, actual, and reduction in provisioned resources, for both CPU and memory. Baseline is what the cluster would have provisioned without Cast AI; actual is what's currently provisioned; reduction is the difference.

Average node count

Compares the average number of nodes the cluster would have run without Cast AI against the actual average node count, with the resulting savings.

Average cost per node

Compares the average cost per node without Cast AI against the actual average cost per node, with the resulting savings.

Workload autoscaler impact

This section appears when the workload autoscaler is active on the cluster, managing at least 20% of workloads in VPA mode.

Workload resource requests

Shows average original requests, average current requests, and resources freed over time — for both CPU and memory. This visualizes how rightsizing has reduced resource demand.

Workload optimization breakdown

A table listing every workload in the cluster. For each workload, you can see:

• Namespace
• Which optimizations are turned on (VPA, HPA)
• Workload autoscaler savings
• Percentage share of total savings