Onam
3 · Optimise · Onam FinOpsForecast, budgets & anomalies

What will we spend, and are we going over budget?

Onam FinOps forecasts spend as a range, not a single line. Budgets are tracked against the forecast as well as actuals, and anomalies are found in the daily series.

Request a demo Read the docs
Illustration: daily cost bars beside a stack of coins and an ownership tag.
Illustrative
The problem

In your words

Our forecast is one line, and it is wrong every month, so nobody reads it any more. We find out about a budget overrun after it has happened. A spike that started and was fixed inside a week never shows up in the monthly numbers, so we cannot tell whether it was real or what it cost.
What you see

What Forecast, budgets & anomalies shows you

Described from the product documentation — what the view holds, not what we hope it will.

  • A forecast range

    A low, an expected and a high figure. A period that lands outside the band is a genuine signal, not routine noise.

  • Budgets against forecast

    Budgets compared with where spend is heading, so the warning comes early enough to act on.

  • Budgets against actuals

    Budgets compared with what has actually been spent so far.

  • Anomalies in the daily series

    Unusual spend detected day by day, not against monthly totals, so short spikes are not averaged away.

How it works

The mechanism, step by step

What Forecast, budgets & anomalies does, in the order it does it.

  1. 1
    The daily series builds up

    Daily ingestion gives forecasting and anomaly detection a history to work from.

  2. 2
    A forecast band is produced

    Low, expected and high figures for the period ahead.

  3. 3
    Budgets are tracked

    Each budget is compared with both the forecast and actuals.

  4. 4
    Anomalies are surfaced

    Spend that departs from the daily baseline is flagged for review.

Limits, said plainly

What it does not do

Knowing where a capability stops is part of deciding whether to buy it.

  • Anomalies need history

    Detection needs enough daily history to have a baseline. A newly connected account produces few useful anomalies until the series has a shape.

  • A forecast is a range, not a promise

    The band says what the forecast knows. Spend can still land outside it, and when it does, that is worth looking at.

Onam AIOps

The FinOps Agent

Onam AIOps agents investigate with evidence on every claim and propose changes a person approves. Nothing changes your cloud without that approval.

FinOps Agent

On the roadmap

On the roadmap: the FinOps Agent is designed to analyse cost, waste, idle resources and anomalies, and to explain where the waste is.

On the roadmap: Designed, not offered. No date is promised.

Read the FinOps Agent docs About Onam AIOps
FAQ

Questions about Forecast, budgets & anomalies

A single line is false precision. It is wrong every month, and a forecast that is always wrong stops being read. A low, expected and high band shows what the forecast actually knows.

Part of Onam FinOps

More in Onam FinOps

Back to Onam FinOps

Cost explorer

Why did our cloud bill go up, and what moved?

Explore Cost explorer

Savings

What can we stop spending — and who decided?

Explore Savings

Reconciled billing

Can we trust this month's cloud cost figure yet?

Explore Reconciled billing

Onam FinOps

Cloud cost and commitment management on reconciled billing data — attribution, forecast, budgets, anomalies and savings.

The whole product
3 · Optimise · Onam FinOps

See Forecast, budgets & anomalies on your own cloud.

Onam FinOps runs in the same console and login as the rest of Onam, with read-only access to your cloud.

Request a demo Read the docs