Area 03 · Operations and infrastructure

Systems administration

Good administration is boring on purpose. Updates go in during the Monday window, a filling disk shows up in a report rather than at four on a Friday, and a leaver's account is shut the same afternoon. We bring that kind of calm to your company entirely remotely, over encrypted access to your servers, cloud tenant and domain.

4
services grouped here
24/7
of automatic checks on every server
Windows
plus Linux, one team for both
PLN 190
per hour excl. VAT, no contract needed

A calendar we stick to

Outages are seldom bad luck. Usually they trace back to a chore that kept getting postponed because the week was busy. So each chore has a fixed slot in our calendar.

Services and event logs

Daily. A stopped print spooler or sync service turns up in the morning check, well before anyone reports that nothing works.

Free space and CPU load

Daily. The aim is that your Comarch ERP Optima or Symfonia database does not freeze halfway through month-end because a log volume quietly filled up.

Security patches

Monthly. After Patch Tuesday, fixes land on test machines first and reach production in the window agreed with you.

Trial restore

As set in the contract. We bring back a chosen file or whole machine from the copies. A green job status alone proves nothing about getting your data back.

Who can access what

Quarterly. We catch former staff, interns from two summers ago and service logins that no one can tie to any system.

Before we take responsibility, we write the environment down. A network diagram, a list of servers and services, where data lives, which system relies on which, and credentials stored in a password vault all go into documentation owned by your company. As a bonus, GDPR and NIS2 questions get easier, because you know where the data sits and who can reach it.

Questions and answers

Yes, and it happens a lot. We begin with an inventory: scanning the network, reading server configuration, rounding up passwords kept in someone's notebook and drawing a dependency map. A small firm usually takes a few days; a dozen or more servers take correspondingly longer. From then on we work from documents instead of guesswork.

Every change is preceded by a snapshot or a fresh backup, and patches go in during a maintenance window you approve, typically an evening or early Saturday. We also check whether the vendor of, say, enova365 or Subiekt nexo has flagged issues with a particular release. If something misbehaves, we roll back, ideally before your staff log in.

Both. Many companies run a mix: users and policies in Active Directory or Entra ID, with the website, shop and databases running on Debian or Ubuntu. One team looks after both sides, so there is no finger-pointing between a Windows crowd and a Linux crowd.

We spot the fault remotely, identify exactly which part has gone and raise the warranty claim with the manufacturer. The physical swap is done by a member of your staff following our step-by-step guide, by the vendor's field engineer or by the data centre's technicians. We stay on the call throughout and watch the array rebuild.

That depends on the business. With many in-house systems and processes that change constantly, someone on the premises who knows the people and paperwork is invaluable. In that case we split the work: servers, monitoring, patching and specialist knowledge sit with us, while your colleague concentrates on users and business applications.

Tell us about your servers

Let us know how many servers you run, what lives on them and who looks after them today. We will read it through and point out the first things worth fixing.

Hours
Mon-Fri 8:00-18:00 CET, reply within one working day
Meetings
Online via Teams or Google Meet

We set strictly necessary cookies only: they keep the site running and remember the city you chose. Nothing here is used for advertising or tracking. More in our privacy policy.