Skip to main content

Converging our DevOps platforms

A diagram illustrating the DevOps process

We published our Home Office Digital, Data and Technology (DDaT) Strategy in July this year. We have committed to becoming more user-centred by reshaping the organisation to become product-centric and data driven, and by removing as much duplication as possible.

Part of our efforts to eliminate duplication involves converging our technology estate and creating more shared platforms. This post is about the work we are doing to converge our DevOps platforms.

DevOps platforms in the Home Office

The Home Office relies on its DevOps platforms to build and operate hundreds of products and services that help keep citizens safe and our country secure.

DevOps platforms bring together tools, processes, automation capabilities and technology that development teams need to deliver better products faster. They help teams follow a continuous delivery approach and support continuous testing and vulnerability scanning.

We are making it easier for teams to deliver by developing a single, overarching DevOps framework that promotes collaboration, consistency and transparency.

Converging platforms means responding more effectively to challenges

The Home Office has more than 10 DevOps platforms. These have been developed for a variety of use cases and built using different technologies, which means they are not managed in a consistent way.

We have platforms that rely on the same core components such as containers, code scanning and cloud hosting solutions. Instead of using a single, shared instance of these, they each use their own bespoke version.

Some platforms are also used in more than one business area, but the teams using them follow different support processes.

Our ambition is to converge these capabilities. Converging to a unified DevOps platform or framework will remove the need for bespoke solutions and allow teams to focus on users rather than underlying technology issues.

We will be able to respond more effectively to emerging challenges and change.

Sharing DevOps technology: learning from our EBSA reuse

Our largest platform, Environment Build Support Administration (EBSA), demonstrates the benefits of sharing our DevOps technology. EBSA is our strategic and borders and immigration-focused platform, with many users and applications, and a mature support model.

EBSA is cloud-native which means it’s easily scalable and can support changing demands of applications. Its containerisation capability means it can quickly deploy new code and applications. Common test frameworks and patterns further help speed up application deployments and recovery.

A number of programmes have recently migrated from their existing DevOps platforms to EBSA. They've been able to migrate in a matter of months and have benefitted hugely from the maturing of the platform. This reuse demonstrates the benefits of sharing DevOps capabilities in allowing teams to build and deploy applications quickly so we can deliver services faster.

Continuous improvement

To improve our products and services we’ve started a programme of discovery, including user research with platform users and teams, to learn the best approach to converging platforms and sharing technology across all areas of DevOps.

We’re reusing technology, patterns and support models to enable teams to start building and deploying applications quickly and help us deliver services faster.

We’ve learned what to adopt, change and optimise from our experiences running EBSA and our Application Container Platform (ACP). We have been able to quickly onboard users to our new law enforcement platform, which is built on EBSA’s foundations and is designed to meet national policing security and network requirements through multi-tenancy cloud capabilities.

This DevOps platform features enhanced security and newer monitoring and error logging tools, which help ensure high availability for the platform and the services that rely on it.

Benefits of DevOps convergence in the Home Office

We want to continue to converge our DevOps platforms and capabilities. This will ensure we:

  • streamline our technology estate, reducing duplication
  • align to industry best practice, for instance on platform security and tools
  • align with key government strategies, including our Cloud First policy and Technology Code of Practice
  • monitor platform risk across our DevOps solutions
  • offer consistent support to users through onboarding and technical documentation
  • speed up delivery, progressing new projects to minimum viable product stage quickly

We’d be interested to hear from other Departments who have converged their DevOps platforms and capabilities. Please get in touch in the comments below.

Sharing and comments

Share this page


  1. Comment by Kieran Smith posted on

    Really interesting article. I wonder if the author would be open to having a discussion on how they became a DevOps organisation? I work for the Greater Manchester Combined Authority and am looking for examples of the successful application of DevOps across public sector organisations.

  2. Comment by Jane Frith posted on

    Hi Kieran. Thanks for getting in touch. We're glad you found the article interesting.

    One of our DevOps colleagues is going to reach out to you.


Leave a comment

We only ask for your email address so we know you're a real person

By submitting a comment you understand it may be published on this public website. Please read our privacy notice to see how the GOV.UK blogging platform handles your information.