Key takeaways
- Side by side, Gartner's 2026 and 2027 trend lists move from building AI capability to bounding it.
- Faster AI-generated code (2026) is followed by the need to verify it at scale (2027's agent coding harness).
- Geopatriation becomes SovereignTech: design for exit rather than reacting by moving workloads.
- For most AWS-based teams: act now on harness, identity, context, AI security and provenance; plan for sovereignty; watch the frontier trends.
Every October, Gartner publishes its Top 10 Strategic Technology Trends. Read on their own, the lists can feel like a parade of new names. Read side by side, the 2026 and 2027 lists tell a clearer story about where enterprise technology is heading, and what engineering leaders should do about it.
The two lists in brief
| 2026 (announced October 2025) | 2027 (announced October 2026) |
|---|---|
| AI-native development platforms | Large quantitative models |
| AI supercomputing platforms | Speech reasoning models |
| Confidential computing | World models |
| Multiagent systems | AI context platforms |
| Domain-specific language models | Agent coding harness |
| Physical AI | AI agent identity |
| Preemptive cybersecurity | Autonomous exposure remediation |
| Digital provenance | SovereignTech |
| AI security platforms | Disposable applications |
| Geopatriation | Wetware as a service |
Sources: Gartner press releases and trend pages.[1][2]
Three shifts worth noticing
1. From building agents to bounding them
In 2026 the emphasis was on capability: multiagent systems, AI-native development platforms and domain-specific models. In 2027 a whole theme is about control: context, harnesses, identity and remediation, with Gartner describing the aim as limiting what autonomous agents can see, use and produce.[2] Our reading: the market has moved from "can agents do this?" to "can we let them?"
2. From faster code to verified code
The 2026 list predicted that by 2030 AI-native development platforms will lead 80% of organisations to shift to smaller, AI-augmented engineering teams.[1] The 2027 list answers the obvious follow-up with the agent coding harness: if code generation scales, verification has to scale too.[2] This is the same message as DORA's research on AI and delivery stability.[3]
3. From geopatriation to designed-in exit
2026's geopatriation (moving workloads to sovereign or local environments) becomes 2027's SovereignTech: technology designed to offer realistic exit options from critical providers. Gartner predicts that by 2030 over 75% of non-U.S.-based organisations will adopt digital sovereignty strategies.[1][2] The shift is from reacting by moving workloads to designing so you could move them.
What to act on, what to watch
Not every trend is a call to action for every organisation. Gartner itself places trends on different planning horizons. Here is our view for a typical mid-sized engineering organisation running on AWS:
| Trend | Our view | First practical step |
|---|---|---|
| Agent coding harness | Act now | Automatic test, scan and size gates before any agent-written change reaches review |
| AI agent identity | Act now | Agent register; one short-lived IAM role per agent; no shared credentials |
| AI context platforms | Act now | Owned, dated sources for your top AI use case; retrieval logging |
| AI security platforms (2026) | Act now | Threat-model AI apps against the OWASP LLM Top 10; add injection tests to CI |
| Digital provenance (2026) | Act now | SBOMs and signed artefacts in every pipeline |
| Autonomous exposure remediation | Pilot | Agent-proposed dependency fixes as pull requests on one service |
| SovereignTech / geopatriation | Plan | Exit plan and data-residency map for critical workloads |
| Disposable applications | Plan | Lifespan, owner and retirement trigger recorded for every new internal app |
| Domain-specific and quantitative models | Evaluate per use case | Compare against a general model on your own evaluation set, including cost per task |
| Speech reasoning, world models, physical AI | Watch unless core to your business | Track; run a pilot only with a clear business owner |
| Wetware as a service | Watch | No action for most organisations |
Disposable applications deserve a closer look
Gartner describes disposable applications as software built for a purpose and intentionally retired once that purpose is fulfilled, and notes that this changes how software is bought, designed and budgeted.[2] The risk is obvious: cheap-to-build apps that are never retired become an estate of unpatched, unowned software with live credentials. The answer is platform engineering and FinOps working together:
- every new app is created from a paved-road template with logging, identity and tagging built in;
- an owner, an expected lifespan and a retirement trigger are recorded at creation;
- cost and usage are reviewed monthly; apps past their trigger get a decision, renew or retire;
- retirement is automated: archive data, remove integrations, revoke access, delete resources.
Trend lists tell you where to look. Your own baselines tell you where to start.
Gartner is a registered trademark of Gartner, Inc. and/or its affiliates. This article is Stepwell's independent commentary on publicly announced trends and is not endorsed by or affiliated with Gartner. Predictions are quoted from Gartner's public press releases.
This article is general information, not legal, regulatory or financial advice. Figures are quoted from the public sources listed below as at the publication date; check the source for updates.
Sources
- Gartner, "Gartner Identifies the Top Strategic Technology Trends for 2026", press release, October 2025; and "Top 10 Strategic Technology Trends for 2026". gartner.com
- Gartner, "Gartner Identifies the Top Strategic Technology Trends for 2027", press release, 20 October 2026; and "Top 10 Strategic Technology Trends for 2027". gartner.com
- Google Cloud, "Announcing the 2024 DORA report", October 2024. cloud.google.com