Kedify | FinOps: Compute, Cost & Savings

FinOps: Compute, Cost & Savings

See how compute levels across monitored clusters translate into estimated cost, recent peak exposure, and savings opportunities.

Window

Start here for the main cost, peak, and savings signals across monitored clusters.

How to read this data

Spend shows current cost, recent peak cost, and estimated savings. Pods show ScaledObject pod-hour savings. Nodes, CPU, Memory, and GPU show how far current capacity is sitting below recent peaks.

These are estimates, not billed cloud costs. They use monitored usage and public pricing, so discounts and billing details can still change your final invoice.

Estimated spend and savings

Cost data unavailable for this window.

Spend

Total current cost, recent peak, and estimated savings.

Current / hr

—

Peak / hr

—

Spend (7d)

—

Estimated savings

—

Pods

ScaledObject pod-hours saved and used across monitored clusters.

Used pod-hours (7d)

—

Saved pod-hours (7d)

—

Savings efficiency

—

Avg pods avoided

—

Nodes

Used, saved, and peak nodes across the org.

Used node-hours (7d)

—

Sum of peaks

—

Saved node-hours (7d)

—

Savings efficiency

—

CPU

Used, saved, and peak cpu cores across the org.

Used core-hours (7d)

—

Sum of peaks

—

Saved core-hours (7d)

—

Savings efficiency

—

Memory

Used, saved, and peak memory across the org.

Used GiB-hours (7d)

—

Sum of peaks

—

Saved GiB-hours (7d)

—

Savings efficiency

—

Pricing coverage

Public pricing coverage for the node mix seen at recent peaks.

Coverage

—

No peak pricing data yet

Clusters

0 / 0

monitored clusters with priced nodes

Clouds

—

Latest peak

—

latest priced peak mix captured

Monitored clusters

Only monitored clusters with active FinOps data are listed here. Open a cluster for detailed FinOps charts and pricing coverage.

Showing 0 of 0


No monitored clusters with FinOps data are available.