The Slovak government cloud is turning into reality after years of discussion: the first projects are running, others are being prepared, and the architecture is shifting toward a standardized hybrid model. Alongside the private part under the aegis of the Ministry of Interior, the use of the public (commercial) cloud through centralized procurement is also ramping up. The main themes are containerization, a service catalog, and measuring operating costs.
Where we are: hybrid government cloud in practice
MIRRI has launched a dynamic purchasing system for cloud and allocated funds from the Recovery Plan to the public part of the government cloud. Currently, nine organizations have projects in the public cloud implemented or underway, and roughly 25 further requests are in advanced negotiation. Meanwhile, the Ministry of Interior has expanded the private part with the first PaaS services and is piloting a container platform for “cloud-ready” applications.
NASES acts as an operator and onboarding partner—building DevOps competencies, standardizing new systems on containers and Kubernetes, and focusing on the renewal of the central components of ÚPVS. The goal is greater scalability, security, and reduced dependence on a single supplier in the 24/7 operation of key services.
How to get services into the cloud: finances, standards, catalog
A strong motivating factor is the money from the Recovery Plan, which MIRRI uses for migrations as well as new solutions in the public cloud. Proper classification of information systems is key—it determines whether deployment should be private, public, or combined. At the same time, the cloud services catalog and bundle assessments are being improved so that institutions “buy on their own” less and make greater use of central services.
The panel also pointed out the need to define the lifecycle of state IT systems. MIRRI, together with the Ministry of Finance, is launching an analysis of operating costs to enable rational decisions about where operation is cheaper and safer. In new projects, containers and Kubernetes are preferred; PaaS and automation accelerate deployment, but moving older, robust systems is gradual and requires refactoring.
Experience, security, and the long haul
The Czech eGovernment cloud model combines state and commercial parts with strict security requirements, confirming the hybrid trend. Here too, emphasis is placed on continuity of operations, geographic backups, and readiness for crisis situations; at the same time, the need is growing to provide AI platforms centrally instead of building small islands in each ministry. However, the cloud is not a one-off project—in the optimistic scenario it is a five- to ten-year managed transformation.
The discussion also opened dilemmas: vendor lock-in, the degree of “open” vs. “enterprise,” moving back from the cloud to on‑prem, and the extent of standardization. There was agreement that the state should build on standard, widely adopted technologies, develop competence centers, and focus on a catalog of usable services, not on “reinventing the wheel.” The result should be faster delivery of services to residents, measurable economies of scale, and higher data security.