Operations | Monitoring | ITSM | DevOps | Cloud

The CloudZero VS Code Extension 2.0 adds a sidebar that brings CostFormation namespace management directly into your editor, so you never have to break flow for a browser tab.

For years, vendor lock-in has been discussed as a theoretical risk. A concern to acknowledge in architecture reviews. A box to tick in compliance frameworks. A future problem that might need addressing. Our latest research reveals something more urgent. For UK organizations, lock-in isn't theoretical anymore. It's structural. It's measurable. And it's preventing organizations from acting on their own strategic priorities.

If you've read our previous piece on the 8 stages of AI engineering maturity, you know where your team sits. Turns out adopting AI is the easy part; adapting to its consequences is where most organizations struggle. For more than a decade, software organizations optimized around a single assumption: implementation capacity was scarce.

CI/CD pipelines do four things: it builds code, runs tests against mocked dependencies, lints for style violations, and scans for known vulnerability patterns. What it cannot do is validate how that code behaves under real users, real service responses, and real runtime constraints that staging was never configured to reproduce. That entire class of failure clears every gate cleanly and surfaces only in production.

Subsea cables have long been the invisible backbone of the internet, carrying more than 95% of global data traffic beneath the ocean’s surface. Today, they are no longer just background infrastructure, they sit at the centre of an increasingly complex digital and geopolitical landscape. The rise of artificial intelligence, alongside continued cloud expansion and hyperscale data centre growth, is driving unprecedented demand for high-capacity, low-latency connectivity.