Onam Security
Onam FinOps

Where is the money going, and who owns it?

The bill arrives every month. The explanation does not.

Onam FinOps turns reconciled billing data into the four answers finance actually asks for: what did we spend, who owns it, what will we spend next, and what can we stop spending — with the reconciliation history on the page so you can tell whether the number is trustworthy yet.

10,000+
security rules
7
cloud providers
< 5 min
to first finding
100%
agentless
Why this matters

Cost went up eleven percent and nobody can say why before the next board meeting.

The provider console shows the total but attributes it by account, not by team. The tagging strategy covers about two thirds of resources, so a third of the bill belongs to nobody. Savings recommendations arrive as a list with no owner attached, so they are read, agreed with, and never actioned. Meanwhile the finance team is reconciling against an export that landed mid-close, and no one is sure whether this month's figure is final or still moving.

The risk of not knowing

If it is not surfaced today, it is exposed today. Attackers do not wait for your quarterly review — and neither do auditors.

Real-time detection, not periodic audits
How does it actually work?

The mechanism, not the marketing

  1. 1

    Billing data is ingested on a daily cadence with a separate monthly-close run, and each cost period reports both its billed cost and its effective cost so discounts and commitments are not silently flattened into one figure.

  2. 2

    Every ingestion run is recorded with its reconciliation state, so the console can tell you whether a period is settled or still moving instead of presenting a partial month as if it were final.

  3. 3

    Ownership rules attribute cost to owners and cost centres, and the attribution coverage is reported as a number alongside the unattributed amount — the honest version of tag-based allocation, which is never complete.

  4. 4

    Costs are decomposed by category, by owner, by resource and by day, with period-over-period movement so a change is traced to what moved rather than asserted.

  5. 5

    Forecasting produces a low, expected and high figure rather than a single line, budgets are tracked against it, and anomalies are surfaced against the daily series.

  6. 6

    Savings recommendations carry a portfolio upper bound and an explicit accept-or-dismiss decision, so a recommendation has a state and a person rather than being a row on a list.

What do you actually get?

Specific outputs, measurable outcomes

Billed cost and effective cost per period, with the difference visible rather than flattened
Reconciliation status on every period
is this month settled, or still moving
Cost by category, by owner, by resource and by day
Period-over-period movement analysis
what actually changed, not just that it changed
Attribution coverage percentage and the unattributed amount, stated plainly
Ownership rules that map cost to owners and cost centres
Forecast with low, expected and high bounds instead of a single false-precision line
Budget tracking and anomaly detection against the daily cost series
Savings recommendations with a portfolio upper bound and an accept or dismiss decision
Ingestion and reconciliation run history, so the provenance of every figure is on the page
See it live

Onam FinOps in the real console.

Not a mockup — the actual Onam console on a live demo account, showing exactly what your team sees.

Dashboard
Run Scan
0
Risk Score
▲ +4 this week
0
Critical Findings
▲ 3 new today
0
Cloud Assets
▲ 231 discovered
0%
Compliance Score
CIS · NIST · SOC 2
Engine Status
IAM
Network
Compliance
CDR
Risk
Encryption
Container
Data Sec
Vuln
Finding Severity
Critical12
High89
Medium234
Low512
Info1,204
Top Critical Findings
Correlating findings…
A
G
A
Your whole cloud on one screen
Risk score, engines, severity and connected clouds — 12,481 assets live
Clip length
12s
Data
Demo account
FAQ

Questions we get a lot

Billed cost is what the provider invoiced. Effective cost spreads commitments and amortised charges across the periods they actually cover. Reporting only one of them is how a month with a large upfront reservation looks like a crisis, or how a discounted month looks like an efficiency win. Onam FinOps reports both.
Ready to see it live

Ready to see Onam FinOps in your cloud?

Connect a read-only role in three minutes. Your first findings surface in under five.