Server maintenance & security

Patched within 24 hours. Watched every day.

We look after Linux servers for companies that don't want to learn about a vulnerability from the people exploiting it. Security updates, firewall, bot protection, backups, monitoring and speed tuning, from €50 per month per server.

auth.log · new server, first hour online
00:04:11 Failed password for root from 185.***.***.17
00:04:13 Failed password for admin from 45.***.***.203
00:04:19 Invalid user oracle from 103.***.***.88
00:04:22 Failed password for root from 218.***.***.5
00:04:30 Invalid user postgres from 91.***.***.140
firewall › blocked · SSH accepts keys only
In its first hour online, a client's new server had login attempts from more than 250 different IP addresses, all trying to guess or steal credentials.

The count is real. The log lines are an illustration, IPs masked.

Why 24 hours

Security fixes now come every week.

In October 2026 more than 900 CVEs were published for the Linux kernel alone. That's one component. PHP, NGINX, Java, OpenSSL, MySQL and every library your site uses get their own on top.

Most of those are minor. A few each month are not, and the time between a fix being published and attackers using the bug has shrunk to days. AI tools find and weaponise bugs faster than before, which is why a server that gets updated "when someone has time" is the easiest target on the internet.

Our rule: critical security fixes go on your server within 24 hours of being released. Here's what the last four weeks looked like.

CVE-2026-109618 · CVE-2026-109619 PHP2Shell

Two PHP flaws that let an attacker run code on the server without logging in. Fixed on 21 October. Five days later CISA listed the first one as actively exploited, and Palo Alto Networks counted over 22 million exposed PHP installs that could be affected.

CVE-2026-114938 Java4Shell

A memory bug in Java's Base64 decoding that can lead to remote code execution. It affects Java 17, 21, 25 and 27, including the Corretto, Temurin and Zulu builds. Oracle shipped the fix on 17 November.

CVE-2026-123633 · CVE-2026-123007 NGINX HTTP/2

Two critical bugs in how NGINX handles HTTP/2, both allowing remote code execution without a password. One goes back to NGINX 1.9.5, released in 2015. F5 patched them on 18 November, and a public proof of concept was on GitHub the same day.

What's included

What we do on your server.

Every server gets the same base routine. The extras depend on what runs on it: an online store needs different protection than an internal app.

01

Updates within 24 hours

We follow the security advisories for your operating system and everything installed on it. Critical fixes go on within a day, the rest in a planned maintenance window, with a backup taken first.

02

Locked-down access

SSH with keys only, no password logins for root, only the ports you need open, and automatic bans for IPs that keep guessing. This alone stops the 250-IPs-an-hour traffic.

03

Bot protection

Rate limits and firewall rules against credential stuffing on login pages, fake sign-ups, scrapers and AI crawlers that ignore robots.txt and slow your site down.

04

AI defence

Attackers use AI, so we do too. AI models read the server logs, link attempts from hundreds of IPs into one campaign and block it, while real customers, Google and your payment provider keep getting through.

05

Speed tuning

PHP-FPM, MySQL and NGINX settings matched to your traffic, caching, compression and a look at the slowest database queries.

06

Backups and monitoring

Daily backups stored off the server, uptime checks, and alerts before a disk fills up or an SSL certificate expires. If something does go wrong, we restore it, find out how it happened and close the hole.

Critical infrastructure

We look after Electrocentrale București's servers.

Electrocentrale București is Romania's largest producer of heat and part of the National Critical Infrastructure. Under NIS 2, which Romania applies through GEO 155/2024, an energy company of its size is an essential entity, with the strictest security obligations in the law.

24h

NIS 2 gives essential entities 24 hours to send an early warning about a serious incident. You can only do that if someone is reading the logs.

Incident reporting
1h

The time it took a client's freshly installed server to draw login attempts from more than 250 IP addresses.

From our own logs
€50

Per server per month, as a starting price. Smaller companies get the same patching routine we run for critical infrastructure.

Starting price
How it starts

From first look to monthly routine.

You get a fixed monthly price after we've seen the server, not before.

Have your server checked
01

Audit

We log in and list what's running, what's out of date, which ports are open to the internet and who has been trying to get in. You get the findings in writing, in plain language.

Fixed price follows
02

Fix and harden

We apply the missing updates, lock down access, set up backups, monitoring and bot protection. Anything that needs downtime is scheduled with you.

03

Monthly maintenance

From then on we watch the advisories and the logs, patch within 24 hours when it's critical, and tell you when something needs a decision from your side.

From €50/month per server
FAQ

Fair questions.

Something we haven't covered? Ask us directly.

What does the €50 cover?
It's the starting price for one Linux server with a standard web setup: security updates, firewall and SSH hardening, backups and monitoring. Servers with several sites, a store under heavy traffic or stricter compliance needs cost more, and you'll know the exact price after the audit.
Our server isn't hosted with you. Is that a problem?
No. We maintain VPS and dedicated servers at any provider, as long as we get SSH access. If you'd rather move, we also run our own hosting in Europe.
Can an update break my website?
It can, which is why we back up first and know which updates need a restart. Critical fixes go on within 24 hours; bigger upgrades, like a new PHP version, are tested and scheduled with you.
Why does a new server get attacked so fast?
Bots scan the entire IPv4 internet continuously. A new server gets found within minutes, and the bots immediately try common usernames and leaked passwords. They don't care who you are; they care that port 22 answers.
We fall under NIS 2. Can you help?
Yes. We already work under those rules for Electrocentrale București. We keep the logs and procedures you need to spot an incident and report it within the 24-hour window.
What if we've already been hacked?
Call us. We isolate the server, find out how they got in, clean it or rebuild it from a known-good backup, and close the hole so it doesn't happen again.

Have a website that should be selling more?

Tell us what you sell and who buys it. We'll tell you honestly what would help, even if that means a smaller project.

Book a free consultation