Server monitoring & management
Server monitoring built for Hetzner.
Hetzner gives you honest hardware at an honest price — and stays out of your way. Which means nobody is watching your server but you. Onserva watches it around the clock and tells you, in plain English, when something is wrong, why it is happening, and what to do about it.
Built and run in the UK by No Fear Tech Ltd. Watching production servers today.
Hetzner’s deal is the machine, not the watching. The console graphs don’t phone anyone.
Hetzner looks after the hardware and the network, and does it well. Everything above that line — the operating system, the disk slowly filling, the process quietly leaking memory — is yours to notice. The graphs in the console will show the story afterwards, but reading them is a job, and interpreting them is a skill.
So most people still find out one of three ways: a deploy fails, a customer emails, or the whole box stops answering. All three are too late.
Onserva watches from outside the server, around the clock, and tells you before any of those happen.
What Onserva watches on a Hetzner box
Memory pressure and swapping
A cheap box with generous RAM still runs out — a leaking process, a build burst, a database cache that grew. When the machine starts parking memory on disk, everything slows down long before anything crashes. We watch the trend, not the spike.
Disk filling up
Logs, backups, Docker layers and package caches grow silently until something fails with "no space left on device". We forecast from the trend — "full in about 19 days at this rate" — so it never becomes urgent.
Sustained load
A processor pinned for an hour is not a processor doing its job. Every reading is judged on a sustained trend, so you are never woken by a busy minute.
Your sites, from the outside
Hetzner’s network can be fine and your site still down. We check your sites the way a visitor reaches them — from outside the box — with certificate and domain expiry watched on the same clock.
Databases, without credentials
PostgreSQL, MySQL, Redis and more, recognised automatically and watched for memory and health. The agent holds no passwords — it could not read a row of your data if it tried.
Silence
Onserva runs somewhere else. A machine that dies cannot switch off its own alarm — silence is itself something we tell you about, within a couple of minutes.
What an alert actually looks like
Production server
The server has begun shifting some of its working data onto the disk because it ran short of fast memory, and the amount moved there has grown from about a fifth to just over a quarter in the last hour.
Why: something on the server asked for a lot of memory at once recently, and rather than run out, the machine parked the least-used data on disk. The readings cannot show which of the three applications caused it.
What to do: no urgent action is needed, but this is worth keeping an eye on over the next day or two. If the amount parked keeps climbing, a restart of the applications would return the server to a clean state.
A real message from one of our own production servers. Not a mock-up.
How it works
Four steps, and only one of them is yours.
- 1
Paste one command
It installs a small agent that reads what Linux already publishes about itself. No dependencies, no reboot, no configuration files to edit.
- 2
We watch, every twenty seconds
Processor, memory, disk, network, per-container figures, response times — judged on sustained trends.
- 3
You get told what and why
A message on Telegram or by email within a minute, in words you can act on.
- 4
You press Authorise
Where a known, tested fix applies — clearing reclaimable disk space, restarting a struggling service — one button does it and tells you what happened. Where none does, we say so plainly rather than guessing.
The agent only ever makes outbound connections — no port is opened on your machine. The AI can read your readings and suggest actions from a short, pre-tested list; it is never given the keys. Every fix waits for you, every time. How this is enforced, in detail
Questions Hetzner owners actually ask
Does Hetzner monitor my server for me?
Hetzner looks after the hardware and the network — that's the deal, and it's a good one. What happens inside your server is yours: the Cloud console shows CPU, traffic and disk graphs, but nobody is reading them for you, nothing explains them, and nothing messages you at 2am. Onserva is the layer Hetzner deliberately leaves to you: around-the-clock watching, explanations in plain English, and fixes you approve with one press.
Why is my Hetzner server so slow?
The usual suspects, in order: the machine has started swapping because memory ran short; the disk is nearly full and everything that writes is struggling; or a process is holding the processor at sustained high load. All three build gradually, which is why the site felt fine last week. Onserva's readings show which one it is and what changed — and its alerts say it in sentences, not chart lines.
My Hetzner server stopped responding — how do I find out first?
The only honest answer is: from outside the machine. Anything running on the server dies with it, including monitoring agents that report from inside. Onserva runs elsewhere and treats silence itself as the alarm — if your server stops checking in, you hear about it within a couple of minutes, along with the last readings before it went quiet.
Do I need to open a port or give you SSH access?
No port is ever opened; the agent only makes outbound connections. Fixes you authorise are carried out through the agent’s outbound channel, from a short, pre-tested list — never by anyone signing in to your machine.
Will this work on a Hetzner dedicated server as well as Cloud?
Yes. The agent is a single static Linux binary with no dependencies — it reads /proc, which every Linux machine has, so a dedicated box, a Cloud VPS and an auction server all look the same to it.
Stop finding out from a failed deploy.
Your first server is monitored free, forever. One command, two minutes, nothing to configure.