One set of numbers,
from the server room
to the boardroom.
Five disciplines report into one store. Federated visibility, governance, topology, virtualisation and dependency across all of them, with a monthly KPI series per domain in your own currency.
The layer above one data model across ITAM, SAM, SaaS, Cloud and AI.
Federated rollup
IllustrativeEvery discipline, one reporting period
Three feeds in, five disciplines reporting
- Platform (ITAM/SAM) ITAM and SAM, one feed
- 32,190
- SaaS Management subscriptions and seats
- 318 apps
- Cloud Management cloud and AI resources
- 4,740
KPI history
monthly, per domain, per currency
- built-in data sources
- 3
- disciplines reporting in
- 5
- federated views across every source
- 5
- KPI series per domain
- monthly
Four teams, four consoles, one question.
The board asks what the organisation owns and what it costs. Four teams answer from four consoles, in three currencies, on four different reporting periods, and somebody spends a fortnight reconciling them into one slide that is out of date before it is presented.
Each team is right about its own console and none of them is answering the question that was asked. The reconciliation is not analysis — it is somebody deciding which of four true numbers goes on the slide, and doing it again next quarter.
Five disciplines. Three feeds. One store.
The join is the part worth understanding. ITAM and SAM arrive on one platform feed, SaaS on its own, and cloud brings AI spend with it — so there is nothing between the disciplines to integrate, because they were never separate.
Five disciplines
- ITAM
- SAM
- SaaS
- Cloud
- AI
Three feeds
-
Platform (ITAM/SAM)
core.data_sources · platform
-
SaaS Management
core.data_sources · saas
-
Cloud Management
core.data_sources · cloud
Each feed is named, holds its own configuration and can be switched off on its own.
One store
- platform computer systems, licence compliance, packages, SNMP devices
- cloud accounts, resources, optimizations, cost breakdown
- saas applications, users, spend
- core data sources, ingest log, KPI history, conversations
Every run into it is recorded, so a figure resolves to a feed and a date.
Each one runs on its own. None of them reports on its own.
Every product below is standalone and shares one asset model. Command Centre is where they arrive together, on one reporting period.
- IT Asset Management CerteroX ITAM Hardware and devices, discovered and reconciled across every platform you run.
- Software Asset Management CerteroX SAM Effective licence position and audit defence, with real depth on the publishers that bite.
- SaaS Management CerteroX SaaS Management Shadow IT and Shadow AI discovery, licence reclamation and offboarding that actually completes.
- Cloud Management CerteroX Cloud Management FinOps across twelve providers, with a named recommendation engine and real governance.
- AI Management CerteroX AI Management Model, experiment, GPU and AI-seat governance — the newest asset class, under the same roof.
What it does with everything once it is in one place.
The same four pillars every CerteroX product is built on, applied to the federated store rather than to one discipline.
Visibility
One question, one answer, across every discipline at once.
- Federated Visibility across cloud, SaaS, SAM and ITAM
- Cloud, SaaS, SAM and ITAM Visibility as their own views
- Trends & Analytics over the monthly KPI series
- Monthly KPI history per domain: assets, spend, savings and growth
- Per-currency KPI history, so a global rollup is not a spreadsheet job
- Value Proposition view for the numbers that go upward
Optimization
Savings ranked across every source, not four separate lists.
- Optimization Hub spanning every connected source
- Cloud optimizations and resource summaries carried through from Cloud Management
- Savings tracked month over month alongside spend and assets
- Vendor spend and cloud cost breakdown by provider
Management
Ask it a question instead of building a report.
- Federated Management across all connected sources
- In-product conversational assistant with saved conversations
- MCP Tool Explorer, with every tool call recorded
- Model Context Protocol servers registered and managed in-product
- Search across the federated store
Governance
Know where every number came from and when it last moved.
- Federated Governance across every source
- Federated Topology, Virtualization and Dependency views
- Data Source Governance — each feed named, configured and enabled or disabled
- Ingest log recording every run into the federated store
- Federated Observability alongside Federated Visibility
Three things a rollup usually is not.
Federating four consoles is a reporting exercise most organisations do by hand every quarter. These are the parts that make it a product instead.
- 01
The rollup is a product, not a project
Federated visibility, governance, topology, virtualisation and dependency are views that already exist across every connected source. Nobody exports four consoles into a spreadsheet and reconciles them by hand for the board pack.
5 federated views
- 02
The numbers have a history
A monthly series per domain carrying assets, spend, savings and growth, each in its own currency. The question "is this better or worse than last quarter" is a row in a table rather than an exercise in finding last quarter’s slides.
monthly, per domain
- 03
Every feed is named and every run is logged
Three built-in data sources, each configured and individually switchable, with an ingest log behind them. When a board number looks wrong, you can say which source it came from and when that source last reported.
3 sources, 1 ingest log
Questions worth asking us.
Is this a sixth product to buy and run?
It is the layer above the five rather than one beside them. The disciplines already share one asset model; Command Centre is where they report in together, with federated visibility, governance, topology, virtualisation and dependency running across every connected source at once. There is no integration project underneath it, because the feeds are the products you already have.
What actually feeds it?
Three built-in sources: Platform, which carries ITAM and SAM together; SaaS Management; and Cloud Management, which brings cloud and AI spend. That is why five disciplines report in over three feeds. Each source is named, holds its own configuration and can be switched on or off on its own.
What does it keep that the individual products do not?
A monthly KPI series per domain — assets, spend, savings and growth, each in its own currency. The disciplines answer what is true now; this keeps what was true in April, which is the question a board actually asks.
A figure gets challenged. What can we show?
Which feed it came from, what that feed was configured to collect, and when it last reported. Data Source Governance names every source and the ingest log records every run into the store, so the answer is a provenance trail rather than an assertion.
What does the assistant do here?
It answers over the federated store, so a question does not become a reporting request. Conversations are saved and every tool call it makes is recorded, which means an answer that went into a board pack can be traced afterwards. It does not decide what counts.
Does it change how the five disciplines are licensed or run?
No. Each product still runs standalone on the shared asset model, and turning a feed off in Command Centre stops it reporting upward rather than stopping it working. What changes is that the rollup is a view rather than a fortnight of somebody’s time.
Bring the question you dread.
We will answer it live.
The one that crosses ITAM, SAM, SaaS and cloud at once, in whichever currencies you report in. Tell us what your board asks and the session starts on the federated view that answers it.
A populated environment at realistic scale, a technical person on the call, and a straight answer where we do not fit.