Linux server setup and management

Yes. We review the server's configuration, fix the security risks and take over management if needed.

It is. We configure and optimise the server for the expected load so it holds up at peak times too.

Automatic backups let us restore data and services quickly, so data loss is minimised.

Maintenance is the recurring work of keeping the server running: updates, security patches, checking backups and monitoring. Management is broader — alongside maintenance it also covers changing configurations, adding new services, optimising performance and taking responsibility for the environment working as a whole. Our management package includes both.

A one-off server installation and configuration starts at €290; ongoing management with round-the-clock monitoring is €99 a month. For multi-server environments with SLA requirements we make a separate quote.

For a new server we prefer Ubuntu — currently Ubuntu 26.04. Ubuntu is widely used, has long-term support and makes it easiest to keep the environment current and secure. We also manage Debian and the RHEL family (Rocky, AlmaLinux). If your server already runs on another distribution we will review it and tell you honestly whether we can take over management or whether migrating makes more sense.

Yes. VPS, dedicated server or cloud environment — the principle is the same: secure configuration, monitoring, backups and updates. A VPS suits most websites and online stores well, because it gives full control over the configuration for only a little more than shared hosting.

Yes. Server migration runs in prepared steps: we map the existing environment, build the new server, synchronise the data and make the final switch at the quietest time of day. The outage usually stays within minutes, and the old environment is kept as a fallback until the new one has proven itself.

Yes. If your application is containerised, we set up the Docker environment, the reverse proxy and the update process. Containers pay off above all when several services have to run on one machine, or when the development and production environments need to be identical.

We set up automatic backups that go to a location separate from the server — the server itself is not a backup. We agree how often a copy is taken and how long it is kept, and we test restoring from time to time. A backup that has never been restored is a promise, not a certainty.