Then the cloud happened, and the pitch was compelling: get rid of the box, stop worrying about hardware failures, access your stuff from anywhere. For most businesses, it was the right call. We moved hundreds of clients onto cloud platforms over the years, and the vast majority of them ended up in a better spot.

But something interesting is happening now. The same technology wave that made the cloud feel inevitable (AI, specifically) is creating reasons for some of that infrastructure to come back in-house. Not all of it. Not for everyone. But the pendulum is swinging, and it’s worth understanding why.

The cloud era made real sense

Let’s be clear about why businesses moved to the cloud in the first place, because those reasons haven’t disappeared.

Cloud platforms like Microsoft 365, Google Workspace, and AWS gave small businesses access to infrastructure that used to require a full-time IT person and a room full of equipment. Email, file storage, collaboration tools, backups. All of it handled by someone else’s data centre, updated automatically, accessible from a laptop at home or a phone on a job site.

For a 15-person office in Surrey, that was genuinely transformative. No more worrying about whether the backup ran last night. No more drive failures taking down the whole office for a day. The cloud solved real problems, and for most everyday business tasks, it still does.

So why is anything coming back?

Two things changed: AI got useful enough that businesses actually want to run it, and people started paying closer attention to where their data goes when they do.

When you use a cloud AI tool (ChatGPT, Copilot, Gemini, whatever your team has started playing with), your prompts, your documents, and your questions are typically being processed on someone else’s servers. For a lot of use cases, that’s fine. Asking an AI to help draft a marketing email isn’t a data sensitivity issue. (If you’re weighing those tools against each other, we compared the privacy implications of ChatGPT and Copilot here.)

But the moment you start feeding it client contracts, financial records, employee files, or proprietary business processes, the picture changes. That data is leaving your environment. It’s being processed on infrastructure you don’t control, in a jurisdiction you may not have thought about, under terms of service that can change without much notice.

This is where the on-premise conversation is coming back, and it looks nothing like the old server-in-the-closet days.

What “on-premise AI” actually looks like in 2026

When we say on-premise now, we’re not talking about going back to a noisy rack in the back room. The hardware has gotten remarkably small and quiet.

A Mac Mini sitting on a shelf can now run a capable AI model locally. Open-source language models (think of them as private versions of ChatGPT that run entirely on your own hardware) have gotten good enough that for many business tasks, they’re genuinely useful. Your team can ask questions, summarize documents, draft communications, and analyze data, all without anything leaving your office network. We wrote a deeper dive on what one of these setups actually looks like in practice.

The setup runs quietly, costs a few dollars a month in electricity, and once it’s configured, your team interacts with it the same way they’d use any other AI tool. The difference is that the data stays on your hardware, in your office, under your control.

We’ve been setting these up for clients who have specific data sensitivity requirements, and the reaction is usually the same: “Wait, this runs here? On that little thing?”

The data sovereignty angle (especially in Canada)

This matters more for Canadian businesses than a lot of people realize.

American companies control roughly 60% of Canada’s cloud market. AWS, Microsoft Azure, and Google Cloud dominate. Even when your data is stored in a Canadian data centre, if the provider is headquartered in the US, it may still be subject to American laws like the CLOUD Act, which can compel disclosure of data stored abroad.

Canada’s privacy framework is also shifting. PIPEDA, the federal privacy law, was written before cloud computing was a thing most people had heard of. New federal privacy legislation is expected soon, potentially with fines up to $25 million or 5% of global revenue. And here in BC, we have PIPA, our own provincial privacy law that’s stricter than what most other provinces require, particularly relevant for healthcare, legal, and financial services businesses.

For a law firm in Langley handling sensitive client files, or a medical clinic in Surrey processing patient records, where your AI processes data isn’t an abstract question. It’s a compliance question with real consequences.

This isn’t about abandoning the cloud

The important thing to understand is that this isn’t an either/or situation. Almost nobody is ripping out their cloud infrastructure entirely, and that wouldn’t make sense for most businesses.

What’s happening instead is a hybrid approach. Your email, your collaboration tools, your everyday file storage: those stay in the cloud, where they work well. But for AI workloads that touch sensitive data, for processes where you need to know exactly where information lives and who can access it, some of that is moving back onto local hardware.

Industry analysts are seeing this play out broadly. A recent Barclays CIO Survey found that 86% of chief information officers planned to move at least some cloud workloads back to on-premise or private cloud, the highest number on record. Gartner is projecting that 40% of enterprises will adopt hybrid compute architectures for critical work, up from around 8% previously. And organizations that have made strategic moves back are reporting 30% to 60% reductions in infrastructure costs for those specific workloads.

These are enterprise numbers, but the pattern filters down. When the tools get simpler and the hardware gets cheaper (and both are happening fast), small businesses start making the same calculations.

What this means if you run a small business

You don’t need to become a technology expert to navigate this. But there are a few things worth thinking about:

• Know where your data goes when you use AI tools. If your team is using ChatGPT or similar tools with client data, understand that information is being processed externally. That may be fine for some tasks and not fine for others.
• Understand your industry’s requirements. If you’re in healthcare, legal, financial services, or any field that handles personal information in BC, your obligations under PIPEDA and PIPA are real. AI doesn’t get an exemption from privacy law.
• Ask about local options. Private AI running on local hardware is no longer a big-company-only solution. The cost has dropped to the point where it’s realistic for a business with 10 or 15 people.
• Think hybrid, not binary. The goal isn’t to pick a side. It’s to put the right workloads in the right place. Cloud for what makes sense in the cloud. Local for what needs to stay local.

The pendulum keeps moving

Technology tends to swing back and forth like this. Mainframes gave way to personal computers. Personal computers gave way to cloud. And now cloud is giving way to something more nuanced: a mix of cloud and local that depends on what you’re actually doing with the data.

The businesses that handle this transition well won’t be the ones who pick one approach and stick with it out of habit. They’ll be the ones who actually understand what they’re working with and make deliberate choices about where things run and why.

We’ve been helping Lower Mainland businesses navigate these kinds of infrastructure decisions since 2006, from the server closet era through the cloud migration and now into this hybrid AI world. If you’re starting to think about where AI fits into your business and want to understand your options (cloud, local, or some combination), we’re happy to walk through it with you. Book a free consultation with Raxxos and we’ll take a look at what makes sense for your setup.

The post Your Business Moved to the Cloud. AI Might Be the Reason Some of It Comes Back. appeared first on Raxxos Technology Inc..

Five months later, a lot of businesses are still running it.

We’re not going to tell you that’s automatically catastrophic. But we are going to tell you what we actually tell our clients — which is a more nuanced conversation than most of what you’ll read about this.

What “end of life” actually means

When Microsoft stops supporting an operating system, it stops patching security vulnerabilities. New ones get discovered all the time, and attackers find out about them just as fast as anyone else. The difference is that on a supported OS, there’s a fix coming. On Windows 10 right now, there isn’t.

That doesn’t mean your computers will immediately get hacked. It means the risk profile is different, and it will keep getting worse over time as more unpatched vulnerabilities pile up.

Where things actually stand with our clients

Georgy Johnson on our team has been tracking this closely. “Right now we’re down to 3 clients and a total of 16 computers still on Windows 10,” he says. “Most of those computers are still getting updates because we applied the Extended Security Updates — ESU — so they are protected.”

The ESU program is worth knowing about if you’re in a position where upgrading right now genuinely isn’t possible. Microsoft offers paid extended security updates that keep the patches flowing for a limited period while you plan and execute a proper migration. It is not a permanent fix — but it buys time without leaving machines completely exposed. If you have a managed IT provider, they should already know whether this applies to your situation.

Why most businesses haven’t upgraded yet

We talk to a lot of businesses across the Lower Mainland who are still on Windows 10, and the reason is almost never cost or complexity. It’s that they don’t fully believe the risk applies to them.

And honestly, that’s understandable. If you’ve never been through a ransomware incident, it’s genuinely hard to feel the weight of one. You can read statistics but they tend to bounce off. The mental math of “this probably won’t happen to me” feels more real than the math of “if it does happen, here’s what it costs.”

The businesses we see take security seriously are almost always ones that have been through something. A colleague got hit. Their own files got encrypted once. They lost a week of work to a breach. That kind of experience changes how you think about risk in a way that statistics don’t. So when we’re having this conversation with a skeptical prospect, we try to make it concrete rather than just citing numbers.

Georgy put it plainly: “I have not seen a security incident occur because a client was still on Windows 10 — but only time will tell.” That is the honest answer. The risk is real and it grows over time, but it hasn’t bitten every business yet. The question is whether you want to wait until it does.

The honest advice: it depends on your risk tolerance

Here’s what we actually tell businesses who are still on Windows 10.

What would it cost your business if your computers were inaccessible for three days? A week? What if your files were encrypted and you had to decide whether to pay a ransom or rebuild from backup? Add up the realistic number. Then compare it to the cost of upgrading. That’s not rhetorical — it’s a real calculation, and it’s different for every business.

If you’d lose serious revenue from a few days of downtime, the answer is pretty clear. Upgrade now.

If you think your business could absorb it — or if the timing genuinely doesn’t work right now — there are ways to reduce your exposure in the meantime. A robust firewall, a decent third-party antivirus solution, and regular security awareness training for your team can meaningfully lower the chances that a vulnerability gets exploited. None of that makes Windows 10 safe. But it’s better than nothing while you plan. And if ESU applies to your situation, that’s worth exploring too.

What the upgrade actually looks like

The assumption most businesses have is that it’s going to be painful and disruptive. It doesn’t have to be.

We’ve been doing Windows migrations for 15-20 years across our clients here in the Lower Mainland, through every major version release. When it’s planned properly, it’s smooth. For businesses that need high uptime, we can migrate machines over a weekend or overnight. For most, a tiered approach works well — a few computers at a time, working through the fleet over a few weeks without disrupting day-to-day operations. Every client we’ve taken through this has said the process was painless.

The thing that makes upgrades complicated is when they’re reactive. Waiting until something goes wrong and then urgently migrating 20 computers while also dealing with an incident is a genuinely bad situation. Doing it on your schedule, with some lead time, is a completely different experience.

A note on managed IT relationships

For businesses with a managed IT provider, transitions like this should be largely a non-event. Keeping clients ahead of end-of-life deadlines is a core part of what a managed IT relationship is supposed to do. Most of our clients are already on Windows 11 or have a migration scheduled.

If you’re a managed IT client somewhere and your provider hasn’t brought this up, it’s worth asking why.

The short version: running Windows 10 isn’t automatically a crisis, but the risk grows over time and the upgrade is easier than most businesses expect. If you’d like to know which of your machines are still on Windows 10, whether they can run Windows 11, and what a realistic migration looks like for your business, we’re happy to take a look.

The post Windows 10 End of Life: What BC Businesses Should Do Now appeared first on Raxxos Technology Inc..