The Five Levels of Cloud Operations: Where Is Your Team Today? 

Levels of cloud operations

Everyone is talking about AI agents running the cloud. Here’s an honest way to see how far you are from that, and what the next step looks like. 

Everyone Wants Autonomous. Very Few Are Ready For It. 

Ask any cloud team about AI agents and you’ll hear the same picture: systems that spot problems, fix them and keep running with no one watching. It’s a good picture. But in most organizations, I work with, the reality on a Monday morning looks very different. 

Teams are running AWS, Azure and Oracle Cloud side by side. Each one has its own console, its own alerts, and its own way of doing things. Engineers jump between tools to check what’s wrong, raise a ticket, and fix it. And the security updates keep coming. Oracle, for example, moved to monthly critical security patches in 2026, on top of its quarterly updates. 

So the real question isn’t “when do we get autonomous operations?” It’s “where are we today, and what’s the next sensible step?” 

The Five Levels 

Cloud operations maturity is a journey, and you can’t skip levels. Here’s a simple way to see where you are: 

LevelNameWhat it looks like day to day
1FragmentedEach cloud runs its own way. People react to whichever alert is loudest.
2StandardizedRunbooks, monitoring, and tickets exist, but people still investigate and fix it by hand.
3AutomatedChecks, reports, and routine jobs run on their own. People still decide and apply the fix.
4AgenticAn agent investigates an issue, shows the evidence, and recommends the fix. A person approves it.
5AutonomousAgents work together on routine issues within limits you set. People handle exceptions.

Why You Can’t Jump Straight to Level 5 

Every level build on the one before it. An agent can only investigate an issue well if the data it needs is already collected in one place. That only happens at Level 3. And you can only automate a task safely if it’s already done the same way every time. That’s Level 2. 

Teams that try to skip ahead usually end up automating confusion. The agent makes recommendations based on gaps in the data, nobody trusts them, and people go back to doing things by hand. 

Most Teams Are Between Level 2 and Level 3 

In practice, most teams I see are somewhere between Level 2 and Level 3. Monitoring is in place. Some reports run on their own. But raising tickets, routing them and working out the root cause is still largely manual. That’s normal, and it’s a good place to build from. 

A Quick Check: Which Level Are You At? 

Answer these five questions honestly: 

  • Do you see alerts and security findings from all your clouds in one place, or in several different consoles? 
  • When an alert fires, does a ticket get created and routed automatically, or does someone do it by hand? 
  • Are routine jobs like health checks, reports and patching run by automation, or by an engineer following a runbook? 
  • When something breaks, does anything help your team find the root cause, or do they start from scratch every time? 
  • Do you trust any system to recommend a fix, even if a person still approves it? 

If you answer “by hand” or “several consoles” to most of these, you’re at Level 1 or 2. If most of it is automated but the fixing is still manual, you’re at Level 3, and the next step is bringing in agents that recommend actions for a person to approve. 

The Next Step Is Smaller Than You Think 

Moving up a level doesn’t mean replacing your tools or your team. It usually means picking one task your team repeats every week or month, such as patching, health checks or chasing the cause of the same alert, and making it run better. Then do the next one. 

That’s the idea behind WinfoCloudX: one place to bring monitoring, automation and agents together across AWS, Azure and Oracle Cloud, so your team can move up the levels one practical step at a time. 

See It Live On 19 November 

Join our webinar, The Journey to Autonomous Cloud Operations, on 19 November 2026. We’ll walk through the five levels and show real work running today, across AWS, Azure and Oracle Cloud. 

What do you think?
Leave a Reply

Your email address will not be published. Required fields are marked *

From our blog

Articles & insights

Agentic Cloud Operations: What AI Agents Should and Shouldn’t Do. Learn where autonomous agents add value, where human oversight is essential, and how to govern
Oracle Fusion AP automation uses AI agents to streamline invoice processing, improve cash visibility, strengthen controls, and reduce AP costs.
Modernize compensation planning with Oracle Workforce Compensation to improve budget control, governance, visibility, approvals, and fair rewards.