Operations | Monitoring | ITSM | DevOps | Cloud

Two-thirds of UK IT leaders say they would switch cloud providers to take back control. Fifteen percent have actually done it. That is the headline from Civo's Digital Sovereignty Revolution 2026, a survey of 1,000 UK IT leaders. The intent is loud and getting louder. The movement is almost silent. It would be easy to call that apathy. It is not. UK organizations are staying on hyperscale infrastructure they no longer fully trust for four very specific reasons. Three of them are structural.

Four in five UK teachers now use artificial intelligence for work. That is an extraordinary level of adoption for a technology that, just a few years ago, most people outside the technology industry had barely encountered. But there's another figure from the same research that I find considerably more interesting. Only 35% of teachers using AI say they're actually working fewer hours because of it.

Every age has had its spark, the moment an idea stops being an idea and becomes something a whole country can build on. Steam, electricity and the web all began with people who could see what was possible, but each one only changed the world once someone built the infrastructure to make it real. Britain has never been short of those people. Our universities produce world-leading AI research, our engineers are among the best anywhere, and our founders build companies the rest of the world wants to buy.

First previewed on stage at Civo Navigate London, the new Civo dashboard is now in beta, and getting to it just got a lot easier. Starting today, you'll see a Try it now banner at the top of your current dashboard at dashboard.civo.com. Click it to head to the new dashboard, sign in with your usual Civo account details, and you're in. You can also go directly to dashboard-manager.civo.com. Look for the Try it now banner in your current dashboard.

The conversation around sovereign cloud in India is getting louder, which is welcome, but as more providers enter the space, I keep seeing the same architectural pattern, and it's worth being direct about what it misses. The pattern is familiar... take a cloud platform, host it in India, manage it end to end, call it sovereign, and let data residency carry the rest of the argument. That works for web apps and standard enterprise workloads.

This week marks the end of our fourth Civo Navigate London event, and it feels like a good moment to say that this one had a slightly different energy from the ones before it. Over the past four years, we have hosted 10 Civo Navigate events across North America, India, and Europe, and each one has taught us something new about what this community actually wants from a day like this. London 2026 was no exception, and I think this year's lineup pushed that a little further than usual.

The Civo Community Slack has become home to over 35,000 engineers, platform teams, students, and practitioners. It’s one of the things we’re most proud of, a genuine space where the people who use Civo and the people who built Civo are in the same room. Since starting the Civo Community Slack, we’ve shipped an entirely new brand, launched Konstruct, and expanded our AI infrastructure.

If you've ever inherited a cluster that nobody fully understands, or watched two teams solve the same infrastructure problem in completely different ways, you've already felt the cost of not having a template strategy. It's not always dramatic; it starts with a different CNI here, a missing cert-manager version there, but it compounds. Six months later, cluster configuration is tribal knowledge, and the platform team has become the bottleneck.

London has spent decades establishing itself as one of the world’s major technology hubs. Its strength comes from the concentration of AI and technology startups, financial services and fintech, highly regulated industries, universities and research institutions, international businesses and technology companies, alongside a large community of developers and engineers.

The sovereign cloud conversation has been dominated by physical location and legal jurisdiction. Both matter. But there's a third leg most discussions skip: the software stack itself. If the platform running a sovereign cloud is proprietary code controlled by a company in another country, its sovereignty has a soft underside.