Government IT often runs into slow processes and unclear specifications. Peter Lukáč, former Director General of NCZI and author of iCity hub, presents a platform designed to help authorities develop services faster and more transparently. The goal is to unify work in one place and reduce dependence on expensive external solutions.
How it works: prototypes and shared documentation
The platform integrates tools that make it possible to quickly turn business requirements into concrete screens. It uses, for example, Figma to create clickable prototypes that the client can click through without any programming knowledge. A Monday discussion is enough, and by Tuesday the team can show the first working simulation of part of the system. It is not about the entire solution at once, but about incremental, understandable steps that speed up decision-making.
At the same time, iCity hub serves as a central record of analyses and changes. Every stakeholder involved works with the current version; it is clear who modified what and when, and changes can be safely merged from different branches. This creates a transparent history of decisions and documentation that evolves along with the project. Authorities therefore do not have to wait months for a finished output, but can continuously monitor the direction.
Deployment, operations, and security
The platform is already running in practice: the Government Office uses it for part of the financial module of the Recovery Plan to administer applications and payments. The team also works with several hospitals, demonstrating that some steps can be done quickly and clearly. The client can see "into the kitchen," can add text comments directly in the system and connect via video, and the feedback is incorporated almost immediately. Such a feedback cycle reduces the risk of misunderstandings and unnecessary costs.
From an operational standpoint, the platform supports continuous integration and deployment, with automatic notifications in case of errors for developers and testers. It can be deployed on the client's infrastructure or in the cloud, if contracts and conditions allow. What matters is that the institution can keep its own system and accompanying documentation under control, instead of being entirely dependent on the supplier. Access is protected by user authentication and permissions, so only those who have access can get into individual parts.
