For years, hybrid cloud was presented as the practical middle ground.

Keep sensitive systems on-premises or in private infrastructure. Move scalable workloads to the public cloud. Connect everything through a carefully designed architecture. Get the flexibility of cloud without giving up control of critical systems.

It made sense.

For many enterprises, it still does.

But the conversation around hybrid cloud is changing.

The problem is no longer whether businesses can connect private and public environments. They can. The harder question is whether they should continue carrying the operational complexity that comes with doing so.

Hybrid environments now sit alongside SaaS platforms, multiple cloud providers, AI infrastructure, legacy applications, sovereign cloud requirements, distributed data and increasingly specialised workloads. What began as a deliberate architectural choice can gradually become a collection of environments that nobody intentionally designed.

Flexera’s 2026 State of the Cloud report found that 73% of surveyed organisations operate hybrid cloud environments, up three percentage points from the previous year. At the same time, Flexera reported that 29% of cloud spend was estimated to be wasted, while security, governance and complexity remain major concerns.

So businesses are not abandoning hybrid cloud.

They are reconsidering why they have it, what belongs where and whether every workload still needs the same architecture.

Hybrid Cloud Was Once About Flexibility

The original argument for hybrid cloud was relatively simple.

Some workloads were better suited to private infrastructure. Others benefited from public cloud scalability. Organisations could therefore place workloads according to their requirements instead of forcing everything into one environment.

For a large enterprise with decades of existing technology investment, that flexibility was valuable.

A bank might retain certain core systems within controlled infrastructure while using public cloud for digital channels. A manufacturer might keep factory systems close to operational environments while moving analytics workloads to cloud platforms. A government organisation might separate sensitive workloads from public-facing applications.

Hybrid cloud made it possible to modernise without replacing everything at once.

The difficulty is that this model assumes the organisation can manage the boundary effectively.

That assumption is becoming harder to maintain.

The Hybrid Estate Is Becoming More Complicated

A typical enterprise cloud environment is no longer simply “on-premises plus one public cloud.”

It may contain:

• Legacy data centres and private infrastructure
• One or more public cloud providers
• SaaS applications
• Edge infrastructure
• Managed databases and specialised platforms
• AI and GPU workloads
• Data platforms
• Multiple networking and identity layers

Every additional environment creates another operational relationship.

Data has to move between systems. Identity has to remain consistent. Security policies need to apply across boundaries. Monitoring has to work across different platforms. Engineers need expertise across multiple technology stacks.

The result is an uncomfortable paradox.

Hybrid cloud was adopted to give enterprises more flexibility.

Poorly designed hybrid cloud can eventually reduce flexibility because every change requires coordination across more systems.

The Question Is No Longer “Cloud or On-Premises?”

This is where the cloud conversation is becoming more sophisticated.

Enterprises increasingly need to ask where a particular workload should run rather than choosing one infrastructure model for the entire organisation.

Cost, latency, regulatory requirements, data gravity, resilience, security, performance and AI requirements can all influence that decision.

Gartner’s 2025 research on the future of cloud highlighted the growing importance of multicloud and cross-cloud architectures, while warning that interoperability challenges can prevent organisations from getting the expected results from multicloud strategies. Gartner also identified digital sovereignty as an increasingly important cloud consideration.

This suggests a fundamental shift.

Cloud strategy is becoming less about selecting a destination and more about making intelligent workload-placement decisions.

AI Is Changing the Hybrid Cloud Equation

Artificial intelligence is one of the biggest reasons businesses are reconsidering existing cloud architectures.

Traditional enterprise applications generally have relatively predictable infrastructure requirements. AI workloads can behave very differently.

Training, inference, high-performance computing, large datasets, GPU availability and real-time processing can create infrastructure requirements that do not fit neatly into an existing cloud strategy.

Gartner has predicted that 50% of cloud compute resources could be devoted to AI workloads by 2029, compared with less than 10% when the prediction was published in 2025. Gartner also noted that organisations may increasingly need to bring AI capabilities closer to the data rather than assuming all AI processing should happen in the public cloud.

That changes the architecture discussion.

A business may want cloud elasticity for certain AI workloads but require local infrastructure for sensitive datasets. Another organisation may need specialised compute in one environment while keeping operational systems elsewhere.

Hybrid architecture can support these requirements.

But only if it is intentionally designed.

Otherwise, AI can make an already fragmented infrastructure estate even more difficult to manage.

Cost Is Becoming Harder to Ignore

Hybrid cloud is often justified as a cost optimisation strategy.

But infrastructure diversity does not automatically reduce costs.

Running private infrastructure has capital, maintenance, staffing and lifecycle costs. Public cloud introduces consumption-based charges, data-transfer costs, managed-service pricing and potentially unpredictable workloads. Operating both means the organisation carries both sets of economics.

Then there are the costs that are harder to see.

Duplicated monitoring systems. Multiple security tools. Specialist engineering skills. Integration platforms. Data movement. Disaster recovery across environments. Network complexity.

These costs rarely appear on a simple cloud bill.

Flexera’s 2026 research illustrates the issue. While 64% of organisations reported that value delivered to business units is now a leading measure of cloud progress, estimated wasted cloud spend rose to 29%. The same report notes that organisations are increasingly considering cloud costs earlier in architecture and migration decisions rather than waiting until after workloads have moved.

That is an important change in thinking.

The question is no longer simply:

“How much does this cloud workload cost?”

It is:

“What is the total economic cost of running this workload in this architecture?”

Data Movement Can Become the Hidden Constraint

One of hybrid cloud’s less obvious problems is data movement.

Applications can be distributed relatively easily. Data is different.

Large datasets may be expensive and slow to move. Regulatory restrictions may limit where data can be processed. AI workloads may require frequent access to large datasets. Real-time applications may not tolerate network latency between environments.

This creates what is often called data gravity.

The larger and more interconnected the dataset becomes, the harder it is to move the data simply because a different compute environment appears cheaper or more convenient.

That means workload placement increasingly needs to consider the relationship between applications and their data.

Moving an application to the cloud without considering where its data lives can create an architecture that looks modern on a diagram but performs poorly in production.

Sovereignty Is Adding Another Constraint

Cloud decisions are also becoming more closely connected to regulatory and geopolitical considerations.

For enterprises operating across countries, the location of data, infrastructure and operational control can influence architecture decisions.

This is particularly relevant in sectors such as government, financial services, healthcare and critical infrastructure.

A workload might technically be able to run in a global public cloud but still require a different deployment model because of regulatory, sovereignty or organisational requirements.

Gartner’s 2025 cloud research identified digital sovereignty as one of the major forces shaping cloud strategy and predicted that more than half of multinational organisations would have digital sovereignty strategies by 2029.

Hybrid cloud therefore increasingly needs to be evaluated alongside sovereignty requirements rather than treated as a purely technical infrastructure choice.

Hybrid Cloud Can Become an Accidental Architecture

This may be the biggest reason businesses are reconsidering it.

Not every hybrid environment was intentionally designed.

An organisation acquires another company and inherits its cloud environment. A business keeps an old data centre because one critical application has never been modernised. Another department adopts SaaS independently. A development team chooses a second cloud for a particular workload.

Five years later, the organisation has a hybrid and multicloud environment.

Nobody necessarily chose it.

Flexera’s 2026 research specifically notes that many organisations end up with complex cloud environments through mergers, acquisitions, siloed applications and inherited infrastructure rather than deliberate strategy.

This distinction matters.

A strategically designed hybrid architecture can be powerful.

An accidental hybrid architecture is usually expensive.

The New Goal Is Not Hybrid Cloud. It Is Architectural Fit.

This is why some organisations are moving away from thinking about hybrid cloud as a permanent destination.

Instead, they are evaluating workloads individually.

A customer-facing application may belong in a public cloud because scalability and global availability matter. A latency-sensitive manufacturing workload may belong closer to the factory. A sensitive dataset may require a controlled environment. An AI inference workload may need specialised infrastructure. A legacy system may remain where it is temporarily because modernising it has a poor economic case.

The architecture becomes a collection of deliberate decisions.

That is more complicated than saying “we are a hybrid cloud organisation.”

It is also more useful.

Modernisation Does Not Automatically Mean Moving Everything to Cloud

Another misconception businesses are reconsidering is the idea that cloud migration is synonymous with modernisation.

It is not.

Moving an inefficient application from a data centre into a cloud environment does not automatically make the application efficient.

The same architecture may simply acquire a different infrastructure bill.

Modernisation may instead involve redesigning the application, changing its data architecture, removing unnecessary dependencies, introducing APIs, decomposing selected services or changing how workloads are operated.

Sometimes the right decision is to move.

Sometimes it is to modernise before moving.

Sometimes it is to keep the workload where it is.

The important part is that the decision should be driven by business and technical requirements rather than cloud migration targets.

Hybrid Cloud Needs a Stronger Governance Model

Once an organisation operates across multiple environments, governance becomes much more important.

Security policies cannot exist independently for every platform. Identity management needs consistency. Data classification must influence workload placement. FinOps needs visibility across infrastructure types. Monitoring needs to cover the entire application path.

This is one reason Gartner identified hybrid computing as a major infrastructure and operations trend for 2026, describing it as an approach that orchestrates across diverse compute, storage and networking mechanisms. Gartner also linked hybrid computing with the need for more composable technology architectures.

The future of hybrid architecture therefore is unlikely to be about simply connecting environments.

It is about orchestrating them intelligently.

What Businesses Should Reconsider Before Redesigning Hybrid Cloud

Organisations do not necessarily need to dismantle their hybrid environments.

They need to understand whether the current architecture is still serving the business.

A useful review should examine:

• Workload fit: Is each workload running in the environment that best matches its performance, security, cost and scalability requirements?
• Data relationships: Where does the data live, and how much movement is required between environments?
• Economic reality: What are the combined infrastructure, licensing, networking, operations and engineering costs?
• Operational complexity: How many tools, platforms and specialist skills are required to operate the environment?
• Future requirements: Can the architecture accommodate AI, new regulatory requirements and changing business models without creating another layer of complexity?

The goal should not be maximum cloud adoption or minimum cloud adoption.

It should be minimum unnecessary complexity.

Hybrid Cloud Is Not Going Away. The Default Mindset Is.

The idea that businesses are simply moving away from hybrid cloud misses what is actually happening.

Hybrid remains dominant. Flexera’s 2026 data shows that clearly, with 73% of surveyed organisations operating hybrid estates.

What is changing is the assumption that hybrid is automatically the right answer.

Businesses are becoming more deliberate about workload placement. AI is changing infrastructure requirements. Sovereignty is influencing where data and workloads can operate. Cloud economics are receiving greater scrutiny. And the operational cost of managing fragmented environments is becoming harder to hide.

The mature enterprise cloud strategy will therefore not ask, “Should we be hybrid?”

It will ask:

“Why is this workload here, what does it depend on, what does it cost, and can we operate it effectively?”

That is a much more difficult question.

It is also the question that prevents cloud architecture from becoming another form of technical debt.

How Verbat Technologies Helps Businesses

Reconsidering a hybrid cloud architecture often requires more than moving workloads between environments. Businesses need to understand application dependencies, modernise legacy systems, redesign integrations, improve data flows and establish infrastructure strategies that support changing operational and business requirements.

Verbat Technologies works across cloud solutions, application modernization, enterprise application integration, API development, data engineering, AI/ML, DevOps, custom software development and digital transformation to help organisations evaluate and evolve complex technology environments.

The objective is not to make an organisation more “cloud-first” for the sake of it.

It is to create an architecture where workloads run in environments that make business, technical and economic sense.

Hybrid cloud was never really about having infrastructure in two places.

The next stage is deciding why each workload belongs where it is, and being willing to change that decision when the business changes.