Operations | Monitoring | ITSM | DevOps | Cloud

Over the past five years, one of the most consistently tracked figures in the UK business technology sector has been the flight from public cloud. Barclays' 2021 CIO survey revealed that 43% of enterprises plan to shift workloads away from public cloud. By 2024, that had grown to 83%. Research for Pulsant in 2025 found that 87% of UK businesses planned to repatriate data away from the public cloud within the next two years.

Most teams first adopt policy as code (PaC) in their delivery pipelines. If something breaks a rule, the system stops it before it goes live. That is useful as it helps catch problems early but in real world environments, the hardest issues to resolve do not come from changes that fail validation. They come from changes that happen later, elsewhere, or outside the pipeline entirely.

Power networks (DSOs, TSOs and generation) are under pressure from every direction. They need to improve reliability and sustainability, deliver real-time customer insight, and meet increasingly stringent regulations. In response, power generation has evolved from a simple centralized model, through to a decentralized model with generation from a mix of diverse sources such as centralized generation from carbon-based, nuclear and renewable generation plants, through DERs even located at people premises.

Our On-call product has a lot of great features: configuring escalation paths, viewing rotas and schedules, requesting cover, etc. However, when framing its reliability, we reduce it down to two critical pieces of functionality: It’s not that we’re happy if only these parts are working, but they are the most important parts. In this post, I'll go into more detail on how we think about their reliability.