I have been spending a great deal of time talking with MSPs lately, and there’s this moment that keeps happening. It isn’t dramatic. No one’s making bold declarations. It’s usually just a pause… and then something like:
“Honestly… our customers are all over the place right now.”
That’s really it… of course, there’s a lot packed into that one sentence.
Some of their customers are still mostly on-prem. Some went all-in on public cloud a few years ago and are now… re-evaluating. Others are somewhere in the middle. They are trying to stitch together cloud, private infrastructure, maybe some edge, and hoping it all behaves like one system.
For a while, that kind of mix felt transitional – like everyone would eventually land in one place.
However, that’s not what’s happening.
The Part No One Really Talks About
What’s changed isn’t just where workloads live. It’s what those workloads are being asked to do now. A few years ago, a lot of systems were still fairly predictable. Batch jobs. Scheduled processing. Some elasticity, sure, but nothing too wild.
Now everything feels… live.
Data is coming in constantly. Systems are expected to respond instantly. AI models are sitting in the loop, making decisions in real time. Customer experience is tied directly to latency in a way it simply wasn’t before.
This is where things start to get a bit uncomfortable. The infrastructure that used to work just fine in a more static world no longer holds up when everything is happening at once.
The Cloud Story Got More Complicated
To be clear, public cloud didn’t “fail.” It still does a lot of things really well. However, the story got more complicated.
Costs, for one, don’t behave the way people expected once you’re moving large volumes of data around all the time. Especially with real-time analytics and AI workloads constantly pulling and pushing data.
Latency starts to matter in a very real way when you’re dealing with user-facing systems or anything tied to real-time decisioning.
Then there’s the data itself. Where it lives, how easily you can move it, and what rules apply to it, depending on geography or industry. Those questions don’t stay theoretical for long.
I heard a story recently from an MSP that stuck with me. They had a customer who went all-in on a major hyperscaler. Made sense at the time. Six months later, they were trying to unwind parts of it.
Not because the cloud was wrong, but because it didn’t fit everything. Costs had climbed faster than expected. Performance wasn’t consistent. Moving data out again was harder than anyone anticipated.
That last part is the one people don’t always plan for.
What The Smarter MSPs Are Doing Differently
The MSPs who seem the most comfortable right now aren’t the ones pushing a single answer.
They’re the ones who’ve stopped trying to force everything into one model. They’re starting with the workload instead and working outward.
Maybe the data runs closer to the edge or on dedicated infrastructure, if it is latency-sensitive. However, it stays in a private environment if the data is confidential or regulated. If something needs to scale unpredictably, sure, public cloud might make sense there.
This brings us to the fact that many are leaning into Kubernetes and containerization, not because it’s trendy, but because it gives them a method by which to seamlessly move things around without breaking everything. It’s less about picking a platform and more about architecting an environment. It is about building something that works, it doesn’t feel fragmented – in fact, it is the opposite… It makes sense.
See also: The Cloud’s Next Chapter: Evolving from Migration to Modernization
Hybrid Stops Being A Compromise
For a long time, hybrid cloud has had this reputation of being the “in-between” option. Like you weren’t fully committed to the cloud yet. That framing doesn’t really hold up anymore. If anything, hybrid is becoming the intentional choice.
When you’re dealing with real-time data, streaming inputs, AI models, IoT signals coming in from everywhere… You need flexibility. You need to be able to decide, very deliberately, where things run and why.
Trying to centralize all of that in one place can actually make things much, much harder, not easier. Here, hybrid becomes less about compromise and more about control.
See also: What Does the Power of Hybrid Cloud Actually Mean?
The Business Side Shifts Too
What’s interesting is how this changes the MSP business itself.
If you’re no longer just “putting someone in the cloud,” your role gets a lot more… involved. You’re helping shape how their systems behave. How they scale. How they stay available. How their data moves. How their costs stay predictable. That naturally leads to deeper relationships, more strategic conversations, and ultimately repeat business. More strategic conversations.
One MSP said something to me that I haven’t really been able to shake:
“I don’t sell cloud or on-prem. I sell confidence.”
That’s exactly it.
It is because, from the customer’s perspective, they don’t actually care where something runs. They care that it works, that it performs, that it doesn’t surprise them on cost, and that it won’t break when they need it most.
See also: Hybrid Cloud Optimal For Businesses
The Questions That Actually Matter Now
If you zoom out a bit, the conversation has shifted. It’s not “Should we be in the cloud?” It’s more like:
- Can our systems handle real-time workloads without slowing down at the worst possible moment?
- Do we actually understand what our costs will look like as data keeps growing?
- Where does our data live, and can we move it if we need to?
- Are we designing for occasional uptime, or for systems that are expected to always be on?
Those are harder questions. But they’re also more honest ones.
Where This All Lands
What hybrid gives you, if you approach it thoughtfully, is a kind of balance that’s hard to get any other way. You’re not locked into one model. You’re not overexposed to one provider’s pricing or limitations. You can adapt.
In a world where everything is becoming more real-time, more data-heavy, more distributed… that ability to adapt quietly becomes the most important thing.
That’s why the best MSPs aren’t making big announcements about changing strategy. They’re just… doing it.
Rethinking Workload Placement in a Real-Time World – Cheat Sheet
Stop treating infrastructure as a single decision
- There is no one “right” environment anymore – design for a mix.
Match the workload to the environment
- Performance-sensitive systems need proximity and control.
- Resilience-driven workloads benefit from being off-site.
- Regulated or high-touch data may require more specialized environments.
Design for data in motion, not at rest
- Real-time analytics, AI, and IoT workloads change how and where data should live.
Prioritize flexibility over commitment
- Architectures should allow workloads and data to move as needs change.
Watch the hidden costs
- Data movement, latency, and egress can outweigh compute savings.
Think in terms of control, not location
- The goal isn’t cloud vs. on-prem – it’s predictable performance, cost, and governance.
Failing to operationalize hybrid is no longer neutral – it’s a liability
- Organizations that remain centralized or fragmented will struggle with rising costs, performance bottlenecks, and loss of control, while leaders deliberately distribute workloads to stay competitive and win.
