Hybrid is the prevailing IT model, and the hardest thing about it is not architecture — it is knowing what you have. Without one view across on-premises, private and public cloud, every workload decision is a guess.
As organisations push further into digital transformation, hybrid has become the prevailing IT model. Combining on-premises infrastructure, private cloud and public cloud lets you meet regulatory and security requirements while taking the flexibility, scalability and performance of public cloud services where they genuinely help.
That evolution brings one problem to the front, and it is not an architectural one. It is visibility.
For a CIO, hybrid cloud visibility is not a technical concern to delegate. It decides whether the hybrid strategy works. Without a unified view of assets, usage and cost across the full scope — on-premises, private cloud and public cloud — it becomes very difficult to make value-driven decisions, and almost impossible to defend them afterwards.
So how do you avoid losing control of your environments, your budgets and your compliance position?
Hybrid environments are inherently complex. They span multiple platforms, vendors and geographies, and the boundaries between them move.
The tool categories grew up on opposite sides of that boundary. Classic ITAM and SAM tools were designed for infrastructure you owned, and were never asked to model consumption-based compute in a granular, value-driven way. The wave of cloud management and FinOps tools that followed were conceived cloud-first — useful for optimisation, largely indifferent to anything running in your own data centre.
The result is a reconciliation problem. On-premises and private cloud sit in one record; public cloud sits in another; nobody owns the join. That produces three predictable failures:
Shadow IT and SaaS sprawl. Business units adopt cloud services outside IT’s line of sight, creating unmanaged risk and redundant spend that never appears in a budget review.
Inconsistent data. Disparate tools and siloed systems make asset data impossible to reconcile, which produces reporting nobody quite trusts and decisions taken despite it.
Cost unpredictability. Without current visibility of consumption, aligning usage to budget is guesswork, and FinOps principles cannot be applied to numbers that arrive a month late.
These are compounded by the pace of change. New services, applications and infrastructure are deployed constantly, often without central oversight. Maintaining a reliable inventory is hard enough; optimising against one you do not trust is not really possible.
The waste this produces is measurable. 29% of cloud spend is wasted — a figure that rose for the first time in five years.
As the race towards AI accelerates, so does the criticality and the cost of the workloads involved. The question for most CIOs is no longer whether to be cloud first. It is where each particular workload actually belongs.
AWS? Oracle Cloud? Google Cloud? Or repatriated to your own data centre?
There are more dynamics to that decision than price and performance. Organisations with mature ITAM and FinOps practices are often driven by the need for granular cost-benefit analysis so they can charge back or show back to specific stakeholders. There may be data residency or security obligations to satisfy. There may be a need to scale in days rather than quarters. And there is frequently an entitlement you already own that makes one option quietly much cheaper than the invoice suggests.
Answering that question well requires a clear view of the options — which is exactly what a unified record across on-premises, private and public cloud gives you.
The consequences of poor ITAM and FinOps visibility run in three directions at once.
Security. Unknown assets are unprotected assets. Vulnerability management can only cover what the inventory knows about.
Finance. Missing insight leads to overspending and to optimisation opportunities that expire unnoticed.
Governance. Compliance cannot be enforced against systems you cannot enumerate, and it certainly cannot be evidenced to an auditor.
CIOs are also under increasing pressure to demonstrate value from IT investment while the ground keeps moving. Hybrid environments change daily — new workloads, new services, new users. Without continuous visibility, IT leadership is permanently reacting. With it, visibility enables agility, accountability and alignment to what the business is actually trying to do.
For a CIO, then, visibility is not an operational efficiency. It is the precondition for strategic control, and the foundation for:
Effective FinOps. Knowing where cloud spend goes, who is consuming it, and which levers reduce it.
Optimised IT asset management. Real visibility of critical infrastructure, so investment decisions follow evidence and consumption follows need.
Stronger security and compliance. Identifying exposure, enforcing policy, and demonstrating control when asked.
Better decisions. Accurate, current data behind investment choices, software rationalisation and transformation planning.
Visibility also supports the cross-functional work. Finance, procurement, security and IT operations all depend on accurate asset data. When a CIO can supply one source of truth, every one of those functions moves faster and with more confidence that it is moving in the right direction.
Closing the visibility gap needs more than better point tools. It needs ITAM, SAM, SaaS management and FinOps on one platform and one data model — because the reconciliation problem is created by having several.
That is what CerteroX is. Not a portfolio assembled by acquisition, but five products over a single asset record: CerteroX ITAM, CerteroX SAM, CerteroX SaaS Management, CerteroX Cloud Management and CerteroX AI Management.
In practice, for a hybrid environment, that means:
Unlike point tools that address one segment, this spans the full asset lifecycle — procurement, deployment, usage, optimisation and retirement — which improves accuracy and cuts the effort of running a complex environment at the same time.
Hybrid cloud is here to stay, and so are the problems that come with it. The difference is that the tooling question has been answered: the combined ITAM, SAM, SaaS and FinOps scope exists today rather than on a roadmap.
To see on-premises assets and cloud consumption answering the same question, book a demo.
Other posts covering the same ground.
Senior stakeholders decide whether to fund your ITAM and SAM programme. Treat them like investors: work out what each group actually needs, then show the data you can already give them.
The original 2016 version of this post reported a customer survey we can no longer substantiate. What survives is the argument underneath it: idle computing is one of the few costs you can remove without anyone giving anything up — and you cannot schedule what you have not discovered.
Hybrid IT broke the ITAM tools built for the data centre. What unified discovery, software recognition and governance actually have to cover when your assets span on-premises, virtual, cloud and SaaS — and how to test a vendor against it.
Everything argued above is checkable. Name the publisher, the billing account or the platform you would argue with, and the session is built around it — the reasoning attached, not a summary slide.
No gated download at the end of it.