DevOps Tenders and Contracts

Search live DevOps tenders on Stotles, or move earlier: read a buyer's technology or digital transformation strategy for signs of a platform rebuild or a DDaT bench refresh before it opens. Platform-wide, 2,140 tenders are open on Stotles right now, DevOps contracts included.

This page covers DevOps engineering, infrastructure automation, cloud engineering and site reliability work: CI/CD pipeline builds, cloud platform support, deployment tooling and the run-and-maintain services that keep a digital platform live. It is a different discipline from Software Development Tenders, which covers building the software itself rather than automating how it ships and runs.

A software development contract pays for building or rebuilding an application: architecture, coding, testing. A DevOps contract pays for the pipeline and platform work around that build: continuous integration and deployment, infrastructure automation, cloud engineering and the site reliability work that keeps a service running once it is live. Buyers often run both as separate lots on the same digital programme.

The most common codes in the corpus are 72000000 (IT services: consulting, software development, Internet and support) and 72222300 (Information technology services). Both are broad IT buckets rather than DevOps-specific codes, since CPV has no dedicated DevOps classification, so buyers file this work under general IT services headings.

Central government departments, NHS bodies and regulators run most of the DevOps work in the corpus, frequently through Crown Commercial Service frameworks such as the DDaT bench models or G-Cloud call-offs rather than standalone open tenders. Scottish public bodies also run interim DevOps engineer placements through their own IT staffing frameworks.

Contract lengths vary widely in the corpus, from short interim engineer placements of a few months to multi-year platform support deals. Some of the largest DevOps call-offs run three to four years with extension options, particularly where they sit under a DDaT bench framework.