Summary

• The Home Office has published plans for cloud services with an estimated value of £881,621,007 excluding VAT, or £1,057,945,209 including VAT.
• The latest planning records indicate a contract from December 2027 to December 2029, with a possible extension until December 2031, although an earlier notice lists different dates.
• The procurement follows an existing £450m AWS agreement and raises questions about expenditure, infrastructure requirements, and the department's ability to maintain competition between suppliers.

The Home Office is preparing a cloud hosting procurement with an estimated value of £881.6 million before VAT, potentially increasing the scale of its infrastructure spending as the department reviews arrangements for its current and future digital services.

Planning notices published through the government’s Find a Tender service put the proposed value at £881,621,007 excluding VAT, or £1,057,945,209 including VAT. The earlier notices describe the requirement as a renewal of Amazon Web Services hosting, while the latest procurement material uses the broader description of public cloud services.

The newer timetable provides for a two-year agreement beginning on 1 December 2027 and ending on 1 December 2029, with a possible extension until December 2031. However, one of the initial notices published on 30 October lists December 2026 to December 2028, leaving the precise contractual transition requiring clarification.

The procurement remains at the planning stage. A supplier engagement event is scheduled for 8 December 2026, with a further notice expected in January 2027. Neither the estimated value nor the publication of those notices establishes that the department has awarded a new contract or committed to spending the full amount.

Cloud services account for substantial expenditure

The Home Office uses digital systems to support immigration and border operations, policing-related functions, identity services, and internal administration. The infrastructure underpinning those activities requires computing capacity, storage, networking, security controls, and continuous operational support.

Cloud services allow organisations to obtain many of those capabilities without directly owning the physical infrastructure. Spending can nevertheless become substantial as more applications are hosted externally and existing systems consume additional computing or managed services.

The planned procurement follows a three-year AWS agreement valued at approximately £450 million, signed in 2023. Comparing the headline values suggests a considerable increase in the potential spending envelope, particularly if the proposed £881.6 million is considered against the shorter initial period identified in the latest notices.

Such comparisons require care because procurement values are not necessarily equivalent to actual expenditure. An estimated contract ceiling may include allowances for future demand, service changes, or requirements that are not ultimately purchased.

The earlier and proposed agreements may also differ in the services covered, how consumption is charged, and whether optional extensions are reflected in the estimate. The available notices do not provide a detailed allocation of expenditure between computing, storage, networking, managed platforms, and supporting services.

Without that breakdown, the figures establish the possible scale of the procurement rather than a reliable measure of unit-price increases. A larger contract value could reflect greater demand, higher prices, changes in the services purchased, or a combination of those factors.

Framework purchasing shapes the competition

The department intends to engage suppliers through the government’s G-Cloud 15 framework, with the planned December event directed towards organisations registered under Lot 1A.

Framework agreements provide a structured route for public bodies to obtain technology services from suppliers that meet the relevant purchasing conditions. They can simplify procurement, although the available competition and award mechanisms depend on the rules of the particular framework.

The latest planning notice describes a competitive award under a framework, while the engagement notice is intended to gather information from potential suppliers before the next procurement stage.

The material does not identify a successful bidder or establish that an existing supplier will necessarily receive the new agreement. AWS is named in the earlier renewal descriptions, but the subsequent generic public cloud wording should not be treated as confirmation of a completed selection.

Supplier engagement may help the department clarify requirements, assess available services, and determine the scope of its future purchasing. Those activities can influence the final specification, although the available notices do not establish how many suppliers will participate or whether particular requirements will be divided into separate contracts.

The published records also need to be read together rather than added as separate spending commitments. The initial AWS planning notices and the subsequent November records carry overlapping procurement information and the same estimated value. The preliminary market engagement notice relates to the wider requirement, not an additional confirmed £881.6 million award.

Different notices leave the timetable uncertain

The most recent planning information gives a contract period from December 2027 to December 2029, with possible extensions for a further two years. That timetable is consistent with the department’s November procurement material and the planned January 2027 publication of a further notice.

However, an earlier 30 October record gives a December 2026 commencement and December 2028 expiry for what appears to be the same proposed value and procurement exercise. A separate initial record also shows the later 2027 dates.

The discrepancy may reflect a correction or revision during the planning process, but the documents available do not establish the reason. Until the department confirms the intended dates, it would be inappropriate to treat the older and newer records as evidence of two separate contracts with identical estimated values.

The earlier AWS agreement has been reported as expiring in November 2026, adding another point requiring clarification in relation to the later proposed commencement date. The notices do not establish how services would be covered during any intervening period, so a gap in the reported dates should not be interpreted as a gap in operational hosting.

The December supplier engagement and subsequent procurement documentation should provide a firmer basis for determining the contract period, transitional arrangements, and precise services required.

Supplier dependence remains an operating consideration

Large cloud contracts introduce questions extending beyond the initial purchasing decision. Applications may depend on a provider’s databases, identity systems, storage services, monitoring tools, and development interfaces, making a future change of supplier more complicated than transferring files between computing environments.

Those dependencies can be commercially acceptable where an established platform offers reliability, specialist functionality, and suitable contractual terms. A replacement exercise may nevertheless require substantial engineering and testing before services can operate in a different environment.

Public sector workloads can also involve demanding requirements for security, continuity, and accountability. Migration plans need to preserve access controls, data integrity, recovery arrangements, and operational performance while avoiding disruption to essential government services.

A competitive procurement can help test pricing and service options, although the ability to change supplier depends partly on how portable the existing workloads are. Contractual exit provisions are important, but the practical effort required to replace infrastructure services also needs to be understood.

Cloud spending presents a related management problem. Services purchased according to consumption can provide flexibility, but costs depend on how resources are configured, utilised, monitored, and retired when no longer required.

Departments can therefore reduce unnecessary expenditure through technical management as well as supplier negotiations. Identifying unused resources, reviewing storage policies, and measuring the performance of applications against their infrastructure costs can be important in managing a large cloud estate.

Final scope awaits the procurement process

The proposed arrangement reflects the continuing operational costs of digital government. Large technology programmes require hosting, security, maintenance, and resilience after their initial development work is complete, while new services can increase demand for infrastructure capacity.

The Home Office’s estimated contract value indicates the possible financial commitment involved, but more detailed documentation will be needed to assess whether it represents greater consumption, changed technical requirements, or different commercial terms.

Its latest planning records also leave questions about the intended relationship between the existing AWS services and the future procurement. The broader wording could accommodate a revised specification, although it does not by itself demonstrate that the department intends to change its principal supplier.

Following supplier engagement in December, the planned January notice should clarify the scope and timetable ahead of any eventual award. The £881.6 million estimate establishes a substantial potential commitment, while the final contract value, supplier selection, and transition arrangements remain undecided.