Intelligence
The analytical core of the platform — telemetry ingestion, waste scanning, commitment negotiation, forecasting, regression attribution, and finance reporting.
At a glance
| Route | /intelligence |
| Group | Analyze |
| Page permission | intelligence |
What it is
The analytical core of the platform and its largest single surface. It is where telemetry-driven analysis, waste scanning, commitment negotiation, forecasting, regression attribution, and finance reporting are computed.
Most other Analyze modules are presentation layers over data this module produces. If you are wondering where a number came from, it usually came from here.
Who it is for
FinOps analysts, platform engineers, and finance business partners who need the underlying analysis rather than a summarised view.
How it works
Telemetry elevates detection
Intelligence hosts the ingestion endpoints for utilisation telemetry from all four cloud providers, plus deployment events, cloud activity events, and OCI Cloud Guard security findings.
That telemetry is what elevates detection from spend-pattern guessing to measured evidence.
The commitment negotiator
It also hosts the commitment negotiator, which:
Analyses historical on-demand usage
Generates purchase strategies with projected savings and break-even analysis
Supports dry-run simulation
On approval, executes AWS Savings Plan purchases through your own IAM role
Features
How to use it
Ensure telemetry ingestion is configured for every provider
Several analyses degrade to heuristics without measured telemetry. They will still produce numbers; those numbers will just be weaker.
Run a waste scan
And confirm opportunities are reaching Opportunity Queue.
Establish a maturity baseline
Review the FinOps score, then use the improvement roadmap it generates.
Use regression attribution when cost rises unexpectedly
Identify the specific pull request or deployment responsible, rather than discovering the increase in a monthly review with no explanation.
Check backtest accuracy before budgeting on a forecast
Generate the forecast, then look at how it performed against known history.
Size commitments from real usage
Use the commitment advisor rather than estimates. Coverage recommendations change as the estate changes.
Run the negotiator in simulation first
Review projected savings and break-even, then route through Approvals before execution.
Produce the finance report with its variance narrative
For the monthly close.
Why it matters
This is the module that converts raw billing data into decisions.
Regression attribution changes the character of cost management
Instead of discovering in a monthly review that spend rose fifteen percent, a team learns which change caused it — and can reverse or justify it.
The commitment negotiator addresses the single largest cost lever available to most cloud customers. Commitment coverage is typically worth twenty to fifty percent, and sizing it is otherwise done manually in spreadsheets.
Connects to
- Feeds Reports, Predictive Analytics, Unit Economics, FinOps Maturity, Cost Center, API Monitoring, and Cloud Playground
- Consumes ingestion from Cloud Accounts and telemetry configured in Integrations
- Commitment execution requires Approvals