Procurement & Deployment Model

Clear responsibility, flexible deployment, and long-term public control

Government cloud infrastructure must be procured, deployed, and operated within strict public sector frameworks. These frameworks require transparency, accountability, legal clarity, and long-term sustainability.

A sovereign cloud must therefore support multiple procurement and deployment models, without compromising governance or public control.

This page outlines how a government cloud built on whitesky can be procured and deployed in line with public sector requirements.

Separation of roles and responsibilities

Public accountability requires explicit responsibility boundaries.

In a government cloud context, responsibilities are typically divided between:

  • the platform (cloud technology and control plane)
  • the operator (entity responsible for day-to-day operation)
  • the public authority (data owner and policy authority)

whitesky is designed to support this separation explicitly, enabling governments to choose operational models without losing architectural control.

Deployment models supported

Managed service deployment

In a managed service model:

  • whitesky provides and operates the cloud platform
  • infrastructure is deployed in government-approved locations
  • operational procedures are transparent and auditable
  • public authorities retain policy and data ownership

This model is often used to accelerate initial deployment while maintaining governance.

Software-based deployment (planned)

A software edition of the whitesky platform for self-operation is planned, at the earliest in 2027. Until then, whitesky is delivered as a managed service.

This model will enable:

  • governments or trusted public partners to operate the platform themselves
  • full control over operations and lifecycle
  • continued alignment with sovereign cloud principles

The software-based model is intended to support long-term autonomy and internal capability development.

Build–Operate–Transfer (BOT) program

For governments seeking full operational independence over time, whitesky supports a Build–Operate–Transfer (BOT) model.

Under the BOT program:

  • a government cloud is built in cooperation with public authorities
  • whitesky operates the platform during an initial phase
  • government personnel are trained in both operation and development
  • operational responsibility is transferred to public institutions

As part of the BOT program, governments receive access to the whitesky platform source code for internal government use only, supporting long-term sovereignty.

Three deployment models, one platformManaged service: whitesky operates the whitesky platform in government-approved locations. Software edition, planned for 2027 at the earliest: the government or a trusted public partner operates it. BOT program, five years: whitesky operates first, then government institutions, who also receive the source code. In every model the public authority keeps policy authority and data ownership, and there are clear exit paths between the models.PlatformOperatorPublicauthorityManaged servicein approved locationswhitesky platformwhiteskySoftware editionplanned, 2027at the earliestwhitesky platformGovernment or atrusted public partnerBOT programfive-year programwhitesky platformplus source codewhitesky first,then governmentKeeps policy authority and data ownership in every model↔ Clear exit paths between deployment models
Three deployment models, one platformManaged service: whitesky operates the whitesky platform in government-approved locations. Software edition, planned for 2027 at the earliest: the government or a trusted public partner operates it. BOT program, five years: whitesky operates first, then government institutions, who also receive the source code. In every model the public authority keeps policy authority and data ownership, and there are clear exit paths between the models.Managed servicein approved locationsPlatformOperatorwhitesky platformwhiteskySoftware editionplanned, 2027 at the earliestPlatformOperatorwhitesky platformGovernment or a trustedpublic partnerBOT programfive-year programPlatformOperatorwhitesky platform,plus source codewhitesky first, thengovernment institutionsPublic authority keeps policyand data ownership in every model↔ Clear exit paths between models
Three deployment models on the same platform: what changes is who operates it, while the public authority keeps policy authority and data ownership.

Procurement alignment

The procurement and deployment models supported by whitesky are designed to align with:

  • public procurement law
  • transparency and accountability requirements
  • multi-year budgeting and planning cycles
  • audit and oversight processes

The platform can be procured as part of:

  • infrastructure modernization programs
  • national digital strategies
  • sector-specific public cloud initiatives

Avoiding structural dependency

Sovereign procurement requires avoiding irreversible dependency.

whitesky supports:

  • clear exit paths between deployment models
  • separation between platform and operator
  • skills transfer to public sector personnel
  • long-term sustainability without forced vendor dependency

These characteristics support policy-driven decision-making over the full lifecycle.

Deployment across multiple authorities

Government cloud deployments may involve:

  • multiple ministries or agencies
  • regional or federal structures
  • shared service organizations

whitesky supports:

  • federated governance models
  • delegated administration
  • consistent policy enforcement across entities

This enables cooperation without centralization of authority.

Central policy, local executionA central policy definition applies consistently to all entities. Each agency or department has delegated administration and executes the policy locally. Oversight is a separate role from operation. The result is cooperation without loss of autonomy.Central policy definitionconsistent across all entitiesAgency Adelegatedadministrationlocal executionAgency Bdelegatedadministrationlocal executionDepartment Cdelegatedadministrationlocal executionOversightseparate fromoperational rolesCooperation without loss of autonomy
Central policy, local executionA central policy definition applies consistently to all entities. Each agency or department has delegated administration and executes the policy locally. Oversight is a separate role from operation. The result is cooperation without loss of autonomy.Central policy definitionconsistent across all entitiesAgency Adelegated administrationlocal executionAgency Bdelegated administrationlocal executionDepartment Cdelegated administrationlocal executionOversightseparate from operational rolesCooperation withoutloss of autonomy
Policy is defined centrally and executed locally: each agency or department administers its own environment, and oversight stays a separate role.

Relationship to other government cloud topics

Procurement and deployment choices are closely linked to:

  • Sovereign Cloud Foundations
  • Data Residency & Control
  • Security & Compliance
  • Hybrid & Multi-Location
  • BOT Program

Together, these define a complete sovereign government cloud framework.

Next steps

  • Identify applicable procurement frameworks
  • Define desired deployment and operating model
  • Align legal, policy, and technical stakeholders
  • Develop a phased deployment roadmap