Skip to main content
Five shifts to plan for, why timing matters, and the one architecture choice every 2026 buyer faces: a native agent per cloud, or one platform across all of them. This chapter covers five shifts to plan for, how to choose between hyperscaler-native agents and one platform across clouds, and what to do first. The CloudThinker mapping for each practice is on About CloudThinker.

​
10.1 Five near-term shifts

Each row pairs a shift with one thing you can do this quarter.

​
10.2 The strategic window

Two Gartner forecasts look like they disagree: They don’t conflict. Together they sort organizations into two groups: those that move from experiment to production with staged autonomy, real governance, and honest measurement, and those that stall. Getting to production early compounds:
  • Every resolved incident adds to what the agents know about your systems.
  • Every hour of toil removed goes back to engineering work.
  • Operating cost stops growing in step with the estate.

​
10.3 Hyperscaler agents or one platform across clouds?

The hyperscaler agents covered in this book (AWS DevOps Agent, Azure SRE Agent, Gemini Cloud Assist) are good at what they were built for. Each goes deepest on its home cloud, follows its vendor’s pricing model, and focuses on investigation, with automated fixes arriving more slowly. If you run a single cloud, the native agent is a strong default. Most enterprises don’t. Many regulated estates, including much of Southeast Asia’s financial sector, mix hyperscalers with local or sovereign clouds and on-premise systems. Three single-cloud agents mean three consoles, three governance models, and three audit trails: the same swivel-chair problem this book argues against, one layer up.

​
Pick a column

Answer four questions:
  1. How many clouds, local clouds, and on-premise environments do you run today, and how many will you run in two years?
  2. Does your regulator or security team need one audit trail across all of them?
  3. Must data stay inside a specific country or inside your own perimeter?
  4. Do you need fixes carried out under approval, or is investigation enough for now?
Count the answers that point beyond one cloud or beyond investigation:
  • None: start with the native agent.
  • One: start with the native agent, unless that answer is a hard requirement, such as data that must stay in one country. Then treat it as two.
  • Two or more: shortlist platforms that run across clouds, and test each with the eight data-control questions in §6.3 and the five-question vendor test in §3.3.

​
A disclosure

This field guide is published by CloudThinker, which builds in the second column. We kept that interest away from the evidence: benchmarks are attributed, the hyperscaler agents are shown at their strongest, and the framework chapters apply whatever platform you choose. Hold us to the same two tests from the list above. About CloudThinker maps each practice in this guide to a product page you can check.

​
10.4 What to do Monday

  1. Capture a baseline. Export 90 days of MTTR, alert volume, and pages from your paging and ticket tools (§8.2).
  2. Pick one bounded domain with frequent, repetitive, reversible incidents (§9.2).
  3. Start every write on approval. In CloudThinker, set the Approval mode to Manual before you connect anything, and under Run types override Automations to Manual too. A chat can pick its own mode, so check it there.
  4. Name the autonomy policy owner before the pilot starts (§7.2).

​
Next steps

Read About CloudThinker to see how the ideas in this guide map to the product and how to start the 90-day pilot from Chapter 9 on your own environment.