Engineers who own the health of your servers: updates, security, backups, monitoring and fast recovery when something breaks.
Most outages are preventable: a disk that filled up, a certificate that expired, a patch that was never applied, a backup nobody tested. Server management is the routine work that stops those things becoming incidents.
We manage Linux servers on your own cloud accounts, on our VPS platform and on other providers. For the technical detail of the Linux side, see Linux server management.
Security updates applied on a schedule, with reboots planned around your business.
SSH, firewall, brute-force protection and access control kept to a known baseline.
Backups monitored for success and restored on a schedule to prove they work.
Checks on the server and on the services that matter, alerting a person.
Trends reviewed so you upgrade before you hit a limit, not after.
A defined process from alert to fix to follow-up.
What is installed, how it is configured and what to do when it fails.
Named accounts and SSH keys, so every change is attributable and leavers lose access.
These are example checks. Thresholds are tuned to each server and workload.
| Check | Example trigger |
|---|---|
| Disk usage and inodes | Above 80 percent used |
| Memory and swap | Sustained swap activity |
| Load average | Sustained load above the number of CPU cores |
| Service availability | Web, application or database check fails |
| SSL certificate expiry | Fewer than 14 days remaining |
| Backup status | A scheduled backup did not complete |
| Authentication failures | A spike in failed SSH logins |
An alert reaches an engineer, who acknowledges it, finds the cause, restores service, then works out why it happened and how to prevent a repeat. You receive a short write-up. The first minutes are usually the same few commands.
uptime # load average
free -h # memory and swap
df -h && df -i # disk space and inodes
ss -tulpn # what is listening
journalctl -p err -b --no-pager | tail -50 # recent errorsWe document what is running, how it is configured and where it is exposed.
We close security gaps, set up backups and agree what good looks like.
Checks and alerts go live and are routed to our team.
Patching, backup checks, log review and housekeeping on a regular schedule.
We use incidents and trends to remove the causes of repeat problems.
Something else on your mind? Message us and an engineer will answer.
Ask a QuestionLinux distributions commonly used for hosting, such as Ubuntu, Debian, AlmaLinux and Rocky Linux. If you have other requirements, ask us.
Named administrative accounts and SSH keys, so every change can be traced to a person.
Updates that need a restart are planned with you for an agreed window.
Routine database care, such as backups, tuning and health checks, is part of server management. Larger database projects are scoped separately.
Tell us what you run and where, and we will scope a management plan.