Managed Linux server: what server management means

You bought a VPS because it was cheap and flexible. The first months went fine. Then an update broke the web server configuration, the disk filled up overnight, or you had to figure out why the database suddenly slowed down. And it became clear that owning a server does not mean anyone is looking after it.

That gap is what the question "managed or unmanaged server" is really about.

Short answer: an unmanaged server means the provider gives you a working machine and everything that happens on it is your problem. With a managed server, someone else is responsible for keeping the system updated, secured, backed up and monitored. Managing it yourself is fine if you have the time and skills and the server is not business-critical. If downtime costs you money or customers, management is cheaper than firefighting.

What a bare VPS actually includes

When you buy a virtual server from a hosting provider, you usually get:

• a running virtual machine with CPU, memory and disk;
• a freshly installed operating system (for example Ubuntu);
• network connectivity and an IP address;
• the provider's responsibility for hardware and the data centre.

That is where the provider's responsibility ends. Everything inside the operating system is yours: the firewall, SSH hardening, the web server, the database, certificates, updates, backups, logs, and noticing when something breaks.

This is not the host's fault. That is simply how the service is built, and it is exactly why it is cheap.

What a server manager takes over

Server management is not one task but many small recurring ones. Each is simple on its own, and each is easy to forget. When I manage a server, the work typically includes:

• Installation and configuration. New servers go on Ubuntu 26.04. The web server is Nginx or Apache2, the database PostgreSQL or MySQL/MariaDB, and where needed Docker, Tomcat, Elasticsearch or OpenSearch. Everything is documented so that someone else can later understand what is where.
• Security updates. These cannot wait "until there is time". Management means updates are applied on a schedule and services are checked afterwards.
• Hardening. Firewall, SSH keys instead of passwords, unnecessary services disabled, brute-force attempts limited. For a detailed list, see securing a Linux server: a checklist.
• Backups and restore tests. A backup that has never been restored is only a hope.
• Monitoring. Disk usage, memory, load, certificate expiry, service status. The goal is to catch a problem before a customer calls about it.
• Troubleshooting. When something goes wrong, there is a person who knows this server, not a stranger logging in for the first time.
• Release lifecycle. When support for an Ubuntu release ends, the plan has to be ready well in advance, not in the last week. I wrote about that in old Ubuntu on your server: moving to a new LTS.

What goes into the contract itself — response times, what is included and what is not — is covered in a separate post: Linux server maintenance: what the contract covers.

When you can manage the server yourself

Self-management is not a bad idea in itself. It works when:

• you or someone on your team knows Linux and has regular time for it, not only when something breaks;
• the server is a development or test machine and downtime costs nothing;
• the service is simple (for example a single static site) and can be rebuilt from scratch quickly;
• you want to learn and are prepared to make mistakes.

When it is not a good idea

Management pays off when:

• the server runs an online store, customer portal or business software, and downtime means lost sales or idle staff;
• the server was set up by someone who is no longer available, and nobody knows exactly what runs on it;
• the server holds personal data and you need to be able to show that it is protected;
• updates happen "whenever someone remembers";
• the only person who knows the server is the same person who also has to run the business.

The most expensive option is usually a third one: the server formally "belongs to someone", but in practice nobody looks at it until something happens.

How to choose

Ask yourself three questions:

1. What happens if the server is down for half a day? If the answer is "nothing much", you can manage it yourself.
2. Who notices when the disk is 95% full? If the answer is "nobody", you need monitoring — yours or someone else's.
3. Could someone else understand your server tomorrow? If the configuration lives only in one person's head, that is a risk no matter who manages it.

If your answers lean the other way, you do not have to hand everything over at once. It often makes sense to start with an audit: I go through the server and write down what runs there, what is outdated and what is risky. Based on that, you decide whether to keep managing it yourself or hand it over.

Frequently asked questions

Does a managed server mean I have to change hosting provider?

No. Management is a service that covers what runs on the server, not where the machine physically sits. I can manage a server at your current host, whether it is a VPS or a cloud server.

Which Linux distributions do you manage?

I prefer Ubuntu, and new servers are installed on Ubuntu 26.04. I also take on Debian and RHEL-family systems.

What is the difference between server management and maintenance?

The words are often used interchangeably. Maintenance usually means recurring work (updates, backups, checks); management is broader and also covers configuration, changes and troubleshooting. In practice, what matters is what the contract says, not what it is called.

Can I take the server back later?

Yes. The access credentials stay with you and the setup is documented, so someone else can take the server over as well.

Does your server need a manager?

If you are not sure whether someone should be managing your server, write to me. Describe in a couple of sentences what runs on the server and who looks after it now, here. I will reply within one working day and tell you honestly whether and how I can help. You can read more about the service on the Linux server management page.