Linux • open-source • networks • servers • programming and scripting
This is not just about installing technology. What matters is that people can work, data stays safe, outages do not last longer than necessary and operating costs make sense. The solution may include servers, networks, backups, monitoring, security, CCTV, access control and purpose-built web or intranet tools. When data, reports or operational tasks are still processed manually, suitable automation can speed up the work, reduce errors and gradually repay the development cost. The key is to understand the real operational problem first - and only then choose the technology that solves it.
A server should not be a black box that stops the organization for days when it fails. I design environments so services can be separated, backed up, versioned and restored quickly when something goes wrong.
Technical stack: Proxmox VE, Proxmox Backup Server, snapshots, incremental backups, HA scenarios, VMs and containers.
Learn moreUsers should not deal with ten passwords, and administrators should not manage access separately in every place. The goal is clear management of accounts, permissions and business data.
Technical stack: Samba AD, LDAP, shared data, file recycle bins, file versions and user/group permissions.
Learn morePeople expect cloud convenience: web access, mobile access, file sharing and document editing. This can also be built on your own storage and connected to existing accounts, permissions and network shares.
Technical stack: Nextcloud, OnlyOffice, external Samba storage, mobile access, a web UI and integration with the existing environment.
Learn moreE-mail should deliver messages reliably, filter unwanted mail and avoid ending up in spam because of poor configuration. A properly built mail server requires ongoing management, checks and updates, not only a one-time installation.
Technical stack: Postfix, Dovecot, Rspamd, Sieve, DKIM, SPF, DMARC, ARC, SRS, antivirus checks and domain management.
Learn moreWhen the network misbehaves, users usually only see that “the internet” is down, the system is slow or Wi‑Fi drops out in some areas. The cause may be unsuitable cabling, weak coverage, an overloaded connection or poorly separated parts of the network.
Technical stack: MikroTik, UniFi, switches, VLANs, routing, firewalling, QoS, wireless and fibre routes.
Learn moreA problem detected in time usually costs less than an operational outage. Monitoring helps identify full disks, unavailable services, degraded connectivity and other unusual conditions.
Technical stack: Nagios, custom plugins, logging, graphs, service maps, automated checks and scripts.
Learn moreWell-designed network protection is not only about blocking traffic. It should prevent unauthorized access, separate sensitive parts of the operation and protect important services without making everyday work harder for users.
Technical stack: nftables, fail2ban, MikroTik firewall, service rules, network segmentation, VPN and monitoring of suspicious traffic.
Learn moreSensitive data should not remain unprotected simply because someone can access a disk or obtain incorrectly configured permissions. I handle encryption, permissions, secure data storage and a sensible balance between protection and convenient work.
Technical stack: LUKS, native ZFS encryption, user/group permissions, separated storage and secure backups.
Learn moreSometimes an off-the-shelf system is not enough and a small tool tailored to real operations is needed: a register, overview, form, data import, log check or service integration. I build smaller web and intranet applications and helper scripts so they solve a concrete job without unnecessary complexity.
Technical stack: PHP, HTML, JavaScript, MySQL/MariaDB, Bash and Python depending on the purpose.
Learn moreIT should serve operations, not the other way around. I use open-source where it reduces cost, improves data control and makes operational sense. If a Linux/Windows hybrid solution is the right path, I design a hybrid solution. The goal is not a fashionable label, but a working result, regular care and a system that does not collapse at the first serious incident.
Commercial products are not automatically wrong, but many organizations pay for licences, modules or complexity they do not really need. A sensible design can reduce cost significantly.
The ideal state is one account, one password and clear permissions across services. Even when perfect unification is impossible, chaos can usually be reduced.
A backup has value only when it is verified that data and services can actually be restored within an acceptable time. The design must therefore cover not only storing copies, but also returning the whole operation to service.
IT is similar to health: neglected prevention comes back expensive later. Long-term supervision, updates, restore tests and log checks cost less than emergency work when users can no longer work.
Sometimes a full open-source transition is possible. Sometimes the right answer is to keep part of the Windows world and build the rest more openly and efficiently.
A proprietary modular web platform for business operations, client access and standalone applications. Individual modules share users, permissions, organizations, documents, audit trails and other core services, so the same data does not need to be created and maintained separately in every application.
The goal is to make work more efficient. Users enter only the information the system genuinely cannot determine on its own. Related values are calculated or pre-filled automatically from available data, so people review and confirm them instead of repeatedly retyping the same details. Less routine work means faster processing, fewer errors and more output from the same team.
The platform can be expanded gradually around real operational needs. A new module does not become an isolated island, but can securely use data and functions from other parts of the system. This makes it possible to develop the solution over time without layering unrelated applications, duplicate records and manual data transfers.
Management needs to know what is necessary, what is unnecessarily expensive and where the risks are. I map what you really use, what is critical and what can be replaced with open-source, a simpler operating model or a more sensible licence option.
In daily operations this creates confusion. During a failure it can mean losing years of work and starting from zero. I design central storage, clear access permissions, change history, recovery of deleted files and secure access from office, web and mobile.
I build a backup and recovery plan that makes sense after server failure, user error or an attack. The goal is not just to have a backup, but also to restore operations quickly.
Connect from a normal computer, notebook or tablet without complicated installations. Open a web browser, sign in and work with data or a remote desktop almost as if you were sitting in the office.
The network has gradually grown around immediate needs, and it is no longer clear what is connected where, which rules are still required or where risk is accumulating. I can map it, divide it into logical parts, document it and add monitoring so future changes can be made in a controlled way.
I have experience from internet service provider environments, with servers, networks, users and non-standard operational requirements. I know IT not only from theory, but also hands-on: I studied automation technology, have overlap into electrical and mechanical environments, and hold professional electrical qualification under § 7 of Czech Regulation 194/2022. I do not solve only ideal lab conditions.
The stack can be built from proven components. The important part is that they work together, can be monitored, backed up and restored.
Contact me through the form. You do not need to know technology names - briefly describe the problem, current situation or your idea. I will get back to you and we will agree on a suitable next step.
