Server monitoring & management
Your servers, watched by something that explains itself.
Onserva is server monitoring and management for people who do not want to become system administrators. It watches 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.
Coolify
Coolify 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 a real server. Not a mock-up.
The things your server is trying to tell you
Practical explanations for the alerts that otherwise send people down a search rabbit hole at the worst possible time.
Your server has started swapping
What high swap usage means, why everything slows down, and what to check first.
Your disk is filling up
Where Docker disk space goes, which clutter is safe to clear, and what needs care.
Your app keeps restarting itself
What a restart loop means, how to distinguish an OOM kill from an app crash, and what to read next.
Your site is slow after a deploy
Why deploys make everything sluggish for a while, what recovers on its own, and what doesn’t.
Your server ran out of memory
What the out-of-memory killer is, how to read its tracks, and what to do about the victim.
You can’t SSH into your server
The four usual causes, in order of likelihood, and the honest back door every provider gives you.
Your site is showing 502 Bad Gateway
What the error means, why your proxy is the one reporting it, and the three usual causes.
Your SSL certificate has expired
Why browsers block the site outright, why automatic renewal fails silently, and how to stop it recurring.
Your server’s processor is pinned at 100%
When a busy processor is a server doing its job, when it is a runaway, and how to tell them apart.
How it works
Four steps, and only one of them is yours.
- 1
Paste one command
It installs a small agent that reads what the operating system already publishes about itself. No dependencies, no configuration, no reboot.
- 2
We watch, every twenty seconds
Processor, memory, disk, network, response times — judged on a sustained trend, not a passing spike, so you are not woken by a server doing its job.
- 3
You get told what and why
A message on Telegram or by email within a minute: what is happening, the most likely cause, and what to do — in words you can act on.
- 4
You press Authorise
Where a known, tested fix applies, one button does it and tells you what happened. Where none does, we say so plainly rather than guessing.
Six rules we build to
These are not marketing lines. They are the constraints the software is written under, and the reason it can be trusted near a production machine.
It runs somewhere else
Onserva watches from outside your servers, never on them. A machine that dies cannot switch off its own alarm — silence is itself something we tell you about.
The AI is never given the keys
It reads your readings and explains them. It can only ever suggest an action from a short, pre-tested list, and if nothing on that list fits, it says the problem needs a person.
Nothing happens without you
Every fix waits for you to press Authorise, every time — with what it will do, and what it costs if it goes wrong, written above the button.
Nothing is opened up to let us in
The agent only ever makes outbound connections. No port is opened on your machine, so installing Onserva does not add a new way in for anybody, including us.
Every server is set up the same way
New machines are built by a version-controlled recipe: hardened, firewalled, key-only sign-in, and the temporary access we were given destroyed at the end.
Your data is walled off in the database
Separation between customers is enforced by Postgres itself, not by our code remembering to filter. A bug on our side still cannot show your servers to somebody else.
Stop finding out from your customers.
Most people discover a server problem when someone tells them the site is down. Onserva tells you first, and tells you what to do.
