Public Administration and Public Sector
We design secure and independent IT infrastructure for public administration and public-sector organisations — from servers, Private Cloud and backup to monitoring, identity management, cybersecurity and Open Source solutions.
Public Sector • Security • Open Source • Digital Sovereignty
IT infrastructure in public administration and public-sector organisations needs to combine security, service availability, control over data and predictable long-term development.
We design and modernise environments for public-sector organisations — from servers, virtualisation and Private Cloud to backup, monitoring, identity management, cybersecurity and Open Source solutions.
Public-sector infrastructure should be designed so that the organisation retains control over its data, access and the future direction of the environment.
Infrastructure for services that need to remain available
Systems used by public administration and institutions support employees, residents, citizens and processes whose unavailability can have consequences far beyond a temporary interruption at a single workstation.
This is why infrastructure design should consider not only server specifications, but also end-to-end service availability, system dependencies, backup, security and the ability to recover after a major failure.
Infrastructure and Private Cloud
We design virtualisation environments and private clouds for systems that organisations want to keep under their own control.
Cybersecurity
We design segmentation, secure administrative access, security monitoring and centralised identity management.
Backup and Business Continuity
We build independent backup copies, off-site protection and Disaster Recovery procedures for critical systems and services.
Modernising infrastructure without creating another technology island
Many public-sector environments evolve over many years. New applications, servers, storage systems and network devices are added at different times, by different suppliers and according to different assumptions.
Over time, this can create an environment where dependencies, responsibilities and single points of failure are difficult to identify.
We therefore begin modernisation by understanding the existing environment:
- which systems are genuinely critical,
- what they depend on,
- where data is stored,
- how backup is implemented,
- how administrative access is managed,
- what is currently monitored,
- which components are unsupported or create unnecessary risk,
- which technologies should remain and which should reasonably be replaced.
Modernisation should not mean replacing everything simply because something newer exists. The first step is understanding what actually needs to change and why.
Private Cloud and infrastructure under organisational control
Not every service needs to run in a public cloud. In many cases, keeping selected systems on owned infrastructure, in colocation or in a Private Cloud can be a reasonable choice.
We design Infrastructure and Private Cloud environments using technologies such as Proxmox VE and Ceph.
This model can provide greater control over:
- data location,
- system architecture,
- administrative access,
- backup policies,
- integration with existing networking and IAM,
- update and change schedules,
- future platform development.
This does not mean that Private Cloud is the right model for every service. Infrastructure should be selected according to technical requirements, security, availability and total lifecycle cost.
Technological independence without dogma
Long-term dependency on a single vendor can make future architecture changes more difficult, increase migration costs and limit the organisation's ability to choose alternative solutions.
We therefore prefer architectures where individual layers can be developed or replaced without requiring a complete rebuild of the entire environment.
Open Standards
Where possible, we use standard protocols, formats and interfaces that simplify integration and future migration.
Vendor-neutral
We select technology according to project requirements rather than designing the environment exclusively around a single vendor.
Organisational Control
We design environments so that architectural knowledge, data access and future development do not depend exclusively on one supplier.
Technological independence does not mean rejecting commercial solutions. It means preserving the ability to make a conscious technology choice several years from now.
Open Source where it provides a real advantage
Open Source can be one element of building greater control over infrastructure and data, but using open software alone does not solve security or operational challenges.
Depending on requirements, we use technologies such as:
- Proxmox and Ceph for infrastructure and storage,
- Zabbix for monitoring,
- Wazuh for security monitoring and event analysis,
- Authentik and FreeIPA for identity and authentication,
- Nextcloud for data storage and collaboration,
- Mattermost or Zulip for team communication.
We use Open Source where it provides a real advantage — not as an objective in itself.
Private collaboration and communication
Control over infrastructure can extend beyond server systems to the tools employees use every day.
We design self-hosted collaboration environments based on technologies such as Nextcloud, Mattermost and Zulip.
This makes it possible to build platforms where the organisation can define:
- where data is stored,
- who has administrative access,
- how backup is implemented,
- how the platform integrates with user identity,
- how long information is retained,
- how service availability is monitored.
We do not treat these platforms as automatic replacements for every SaaS service. We first analyse the real requirements and existing dependencies.
Centralised identity and access management
In a larger organisation, access to systems should not be managed separately inside every application.
We design central IAM and SSO mechanisms that can include:
- centralised user accounts,
- SSO,
- MFA,
- roles and groups,
- application integration with a central IdP,
- separation of standard and administrative accounts,
- access control for infrastructure services,
- processes for removing access after a role change or end of cooperation.
Depending on the environment, we use solutions such as Authentik and FreeIPA.
Access security starts with knowing who has an account, what they can access and whether they still need that access.
Segmentation and secure networking
An institutional network should not be one shared trust zone where every device has unrestricted access to all other systems.
Depending on the architecture, separate zones may include:
- user workstations,
- servers,
- administrative systems,
- management infrastructure,
- backup,
- technical and IoT devices,
- guest networks,
- Internet-facing services.
Communication between zones should reflect the actual needs of systems and users.
For networking and security, we use technologies such as Fortinet and MikroTik.
Backup independent from production infrastructure
A backup is useful only if it can be used in the exact situation it was intended to protect against.
We therefore design Backup and Disaster Recovery as a separate infrastructure layer rather than simply an additional function of the primary storage system.
Local Backup
Enables fast recovery after common failures, user errors and loss of individual data.
Off-site
A copy stored outside the primary infrastructure reduces the impact of failures or incidents affecting the main environment.
Recovery
We test not only whether backups complete successfully, but also whether systems and data can actually be restored.
Depending on the infrastructure, we use solutions such as Veeam and backup technologies for Proxmox environments.
Backup should be designed from the perspective of restoring a service, not merely completing a backup job successfully.
Disaster Recovery and loss of an entire location
A major failure can involve much more than a single server. It may affect storage, networking, power, the server room or the organisation's primary location.
For critical systems, it is therefore worth defining:
- RPO — acceptable data loss,
- RTO — required service recovery time,
- recovery order of individual systems,
- backup location,
- required replacement resources,
- network and identity dependencies,
- people responsible for individual recovery stages.
A second location or recovery environment should reflect actual business continuity requirements rather than simply the desire to maintain another copy of the infrastructure.
Monitoring instead of reacting only after users report a problem
Infrastructure health should be visible centrally. Problems with resources, storage, networking, certificates or backup can often be detected before they cause service unavailability.
We build monitoring environments based on technologies such as Zabbix, covering:
- physical and virtual servers,
- storage,
- firewalls, routers and switches,
- network links,
- backup systems,
- critical services,
- certificates,
- selected applications,
- hardware infrastructure parameters.
Monitoring should help detect a problem, understand its impact and identify where troubleshooting should begin.
Security monitoring and centralised event collection
Logs distributed across servers, devices and applications are difficult to analyse only after an incident has already occurred.
We build centralised security monitoring environments based on technologies such as Wazuh.
They can support:
- centralised security event collection,
- endpoint and server monitoring,
- detection of selected changes and anomalies,
- analysis of authentication events,
- integrity monitoring of selected components,
- work related to security and compliance requirements.
NIS2 and the Polish National Cybersecurity System
The amended Polish National Cybersecurity System Act implementing NIS2 significantly expanded the range of organisations subject to cybersecurity requirements, including public-sector entities.
The specific obligations depend on the organisation's legal status and type. It should therefore not be assumed that every public-sector institution has exactly the same requirements.
Where the regulations apply, technical infrastructure should support areas such as:
- risk management,
- access control,
- security monitoring,
- incident handling and analysis,
- backup security,
- business continuity,
- vulnerability and update management.
More information is available on our NIS2 and KSC page.
Cybersecurity as part of the architecture
Security should not be treated as a separate product added after the infrastructure project is complete.
During architecture design, we already consider:
- network boundaries and segmentation,
- administrative access to systems,
- MFA and SSO,
- privilege control,
- central logging,
- security monitoring,
- protection of backup infrastructure,
- update procedures,
- recovery after a security incident.
Infrastructure security comes from multiple cooperating layers — not from a single firewall, SIEM platform or security document.
Documentation and knowledge retained by the organisation
Infrastructure should not be understandable only to the company that implemented it.
A project should document and organise areas such as:
- infrastructure topology,
- networking and addressing,
- roles of individual systems,
- dependencies between services,
- backup and recovery procedures,
- administrative access model,
- monitored components,
- operational responsibilities.
This reduces the risk that a change of employee, administrator or contractor results in the loss of critical knowledge about how the environment works.
Supporting the existing IT team
Public-sector institutions often have their own administrators or IT teams who understand local systems and the organisation's daily requirements best.
We do not need to replace that team. We can support it where additional infrastructure expertise or an independent assessment is required.
New Architecture
Design of virtualisation, Private Cloud, storage, networking, backup, monitoring or security.
Modernisation
Assessment of the existing environment and preparation of a change plan without unnecessarily replacing infrastructure that still meets requirements.
Technical Problem
Independent analysis of availability, performance, backup, storage, networking or security issues.
Migrations and technology changes
A change of infrastructure platform should be preceded by an assessment of existing dependencies.
Migration can involve much more than moving virtual machines:
- storage,
- networks and VLANs,
- backup,
- identity,
- monitoring,
- security systems,
- application integrations,
- maintenance windows,
- rollback planning.
In migration projects, we can also support transitions from existing virtualisation platforms to environments based on Proxmox VE.
When can we be a good fit?
Working with sLogic Group may be particularly useful when:
- you are modernising a server or virtualisation environment,
- you want to reduce single points of failure,
- you are planning a Private Cloud or infrastructure consolidation,
- you need to improve backup and Disaster Recovery,
- you want to implement centralised infrastructure monitoring,
- you need SIEM or security monitoring,
- you are planning central IAM, SSO or MFA,
- you are evaluating Open Source solutions as alternatives for selected parts of the current stack,
- you need an independent assessment of the existing architecture,
- you are preparing the environment for new cybersecurity requirements.
How do we work?
01. Analysis
We analyse the existing infrastructure, systems, requirements, dependencies and areas of risk.
02. Architecture
We design the target environment with availability, security, backup, monitoring and future growth in mind.
03. Implementation
We introduce changes in stages, perform testing and prepare the environment and documentation for ongoing operations.
If the infrastructure has evolved over many years and needs to be structured before the next modernisation project, we can start with an IT Audit and Architecture.
Secure infrastructure without unnecessary dependency
The goal is not to replace every existing technology with Open Source or move every service into an organisation's own server room.
The goal is to build infrastructure where decisions about data, security, availability and future development remain as conscious and predictable as possible.
We choose technology to fit the requirements — not the requirements to fit the technology.
Modernising IT infrastructure in a public-sector organisation?
We can assess the current environment and help design secure, predictable and technologically independent infrastructure aligned with the organisation's requirements.