New
Post-VMware licensing changes: what did you actually do?
Renegotiated, moved to another hypervisor, containerised, or went to public cloud? Share your path and what surprised you.
Editorial Answer this
Evaluation guide
How to evaluate hybrid and multicloud platforms
This guide is for infrastructure and platform leaders running workloads across their own data centres, one or more public clouds and the edge. It's written for teams rethinking where workloads live after a licensing change, a cost review or a new sovereignty requirement.
In short
Use this guide to compare hybrid and multicloud platforms on what decides the outcome: consistent operations across environments, the real cost of leaving, licensing terms, cost visibility, security policy and data residency. Then shortlist three to five companies on Techarda, check recent news for licensing or ownership changes, and compare them side by side.
What’s changing in Hybrid & Multicloud
Before you compare anyone, it helps to know what has shifted in the market, because it changes which questions matter.
Virtualisation licensing has been reset
Changes to licensing and packaging after a major acquisition in the virtualisation market have pushed many teams to reassess their private cloud platform and to price alternatives seriously for the first time in years.
Workload placement is being revisited
Some teams are moving specific workloads back on-premises for cost, performance or control. It is selective rather than a wholesale retreat from public cloud, and it depends on honest cost data.
Kubernetes has become the common layer
Most vendors now offer a managed control plane that spans environments. That helps with consistency, but the hard parts are still data, identity and networking.
Sovereignty and AI are shaping placement
Residency rules are driving demand for local and sovereign cloud options, and GPU capacity and data gravity now influence where training and inference run.
What to judge vendors on
Those shifts shape the criteria below. Each one says why it matters and what to ask, so you can take it straight into a vendor call.
| Criterion | Why it matters | What to ask vendors |
|---|---|---|
| 1Consistent operations across environments | The main promise of hybrid is one way of working. If every environment needs different tools and skills, you carry the cost of several platforms. | “Which management, policy and monitoring tasks work the same way on-premises and in each cloud we use, and which need separate tools?” |
| 2Portability and the cost of leaving | Moving a virtual machine or container is easy. Moving its data, identity and network dependencies is where time and money go. | “What would it take to move a workload from your platform to another, and which parts of the stack are proprietary to you?” |
| 3Licensing and commercial terms | Recent changes in this market show that terms can move sharply at renewal. Your exposure depends on what the contract lets you do next. | “What price protection do you offer at renewal, can we reduce commitments if we move workloads, and how are cores or consumption counted?” |
| 4Cost visibility across environments | Placement decisions are only as good as the cost data behind them. Egress and shared services are the usual blind spots. | “Can we see cost per workload across on-premises and cloud in one view, including data egress and shared services?” |
| 5Security and policy consistency | Different identity, network and key management in each environment creates gaps that are hard to see and easy to exploit. | “How are identity, network policy and encryption keys managed across environments, and who holds the keys?” |
| 6Data residency and sovereignty | Residency covers more than where the data sits. Control-plane metadata and support access can cross borders too. | “Where do our data and control-plane metadata live, and can support staff outside the country access either?” |
| 7Migration support and skills | Migrations stall on skills and sequencing more often than on technology. | “What tooling and services come with a migration, and what skills does our team need to run the platform day to day?” |
| 8Support across vendors | Multi-vendor stacks produce problems that sit between products, and support teams that point at each other. | “Who owns a problem that spans your product and a cloud provider’s, and do you have joint support arrangements in place?” |
Trade-offs to settle early
No vendor does well on every criterion, and some pull against each other. Decide where you stand on these before the demos start, or the demos will decide for you.
One control plane or native services in each cloud
A single control plane gives consistency and one skill set. Native services in each cloud are usually better integrated and quicker to adopt, but you run several ways of working.
Portability or managed services
Staying portable means avoiding the managed databases, queues and AI services that make a cloud productive. Decide which workloads need to move and accept lock-in where they do not.
Consumption pricing or owned capacity
As-a-service models for on-premises hardware turn capital spend into operating spend and shift some risk to the vendor. Owned capacity is often cheaper at steady load and gives you more control.
Move now or run a mixed estate
Migrating off a platform quickly limits licence exposure but adds delivery risk. Running two platforms during a longer transition is safer and costs more in the meantime.
Sovereignty or feature parity
Sovereign and local regions can lag the main regions on services and capacity. Check the specific services you need, not the region list.
Red flags
As the answers come back, watch for these. One on its own isn’t a deal breaker, but it deserves a follow-up question in writing.
- Portability claims that stop at the virtual machine or container and ignore data and identity.
- Multi-year commitments with no price protection at renewal.
- Cost tools that cannot see egress or shared services.
- Migration estimates given before anyone has assessed your estate.
- Sovereignty claims where the control plane or support team sits offshore.
Build your shortlist
Map your estate first, then use Techarda to narrow the field to three to five companies that fit it.
- List the environments you run today and expect to run in two years, and the workloads that must move or stay put.
- Keep companies that support those environments in production today, not on a roadmap.
- Compare like with like: platforms against platforms, management and cost tools against each other.
- Read recent stories for licensing, pricing or ownership changes, and plan questions around them.
- Use the practitioner questions below to see where teams like yours got stuck, then compare side by side.
Companies to consider in Hybrid & Multicloud
Listed by recent activity on Techarda (what people are reading, following and discussing). The order says nothing about quality, market share or fit for your needs.
Latest Hybrid & Multicloud stories
Once you have names, recent news is where pricing changes, acquisitions and outages show up first. These are the five newest stories in this category.
Hybrid & MulticloudHow-to
FinOps for AI: a practical guide to managing AI cloud costs
AI has crossed the threshold from speculative R&D to the operational engine of the modern enterprise. Engineering teams deploy autonomous agents to handle complex customer workflows; product squads embed foundation model APIs directly into flagship software; and business units independently license AI-powered SaaS platforms to streamline daily work. What began as a series of isolated experiments…
Hybrid & MulticloudHow-to
AI cost management: How to build a business case for executives
Stop guessing. Start governing. Your CFO doesn’t want a demo, they want a defensible business case. Here’s the 7-step checklist that builds one. Define your addressable AI spend: Inventory AI costs across model APIs, cloud GPUs, vector databases, AI software licences, agents, users and infrastructure Identify optimization opportunities: Evaluate model rightsizing, prompt caching, agent…
Hybrid & MulticloudHow-to
Your AI Strategy Depends on Partners; Here’s How to Find Them
The next phase of enterprise AI will not be built inside one provider’s platform. Models, accelerated compute, enterprise data, storage and network services increasingly…
Hybrid & Multicloud
When AI becomes an asset, not an expense
September 24, 2026 – Conversations about AI costs often begin with token prices and access to the latest cloud models. Those factors matter, but they can obscure the larger question: as AI moves into production, how can enterprises meet growing demand economically, predictably, and at scale? The issue becomes more urgent as demand grows steady and business-critical. A consumption-only approach…
Hybrid & Multicloud
HPE named a Leader in 2026 Gartner® Magic Quadrant™ for Infrastructure Platform Consumption Services
HOUSTON – September 23, 2026 – HPE (NYSE: HPE) today announced it was named a Leader in the 2026 Gartner® Magic Quadrant™ for Infrastructure Platform Consumption Services for the second consecutive year. Over the past year, HPE has advanced GreenLake with agentic AIOps and unified cloud operations software that simplifies managing and optimizing enterprise AI factories and IT infrastructure. “AI…
What practitioners are asking
News tells you what vendors announced. These open questions show what teams are still trying to work out, with the least-answered first.
New
How are you getting GPU capacity for AI in 2026?
Reserved cloud capacity, neoclouds, on-prem clusters, shared internal pools? What are lead times and utilisation like?
Where evidence is thin
A shortlist is only as good as the evidence behind it, and ours is still growing category by category. Here is what’s missing in Hybrid & Multicloud right now.
19 of 20 companies have no published reviews
If you’ve run one of these in production, a short review helps the next team decide. Reviews are moderated before they appear.
2 questions with no answers yet
An answer from someone who has made the same decision is often more useful than any guide. Share what worked, what didn’t and what you’d check next time.
Answer a Hybrid & Multicloud questionFrequently asked questions
What should I ask Hybrid & Multicloud vendors about portability and the cost of leaving?
Moving a virtual machine or container is easy. Moving its data, identity and network dependencies is where time and money go. Ask: What would it take to move a workload from your platform to another, and which parts of the stack are proprietary to you?
What should I ask Hybrid & Multicloud vendors about licensing and commercial terms?
Recent changes in this market show that terms can move sharply at renewal. Your exposure depends on what the contract lets you do next. Ask: What price protection do you offer at renewal, can we reduce commitments if we move workloads, and how are cores or consumption counted?
What should I ask Hybrid & Multicloud vendors about cost visibility across environments?
Placement decisions are only as good as the cost data behind them. Egress and shared services are the usual blind spots. Ask: Can we see cost per workload across on-premises and cloud in one view, including data egress and shared services?
What should I ask Hybrid & Multicloud vendors about data residency and sovereignty?
Residency covers more than where the data sits. Control-plane metadata and support access can cross borders too. Ask: Where do our data and control-plane metadata live, and can support staff outside the country access either?
This guide is written by Techarda editors. No vendor paid to appear in it or saw it before publication. See our methodology, the trust dashboard or go back to the Hybrid & Multicloud hub.