How It Works

One script in, a fully-watched server out — and plain-English answers when something breaks.

The Short Version

You run one short bash script on your server. It reads what the box is doing — CPU, memory, disk, the services running — and reports home. From there CleverUptime works out what else is worth watching and sets up the right checks on its own, probing your server from the outside the way the internet sees it. When something looks wrong, you get an alert that names the likely cause and the fix — not just a red light. Let's walk through each part.

The Script You Read First

Running someone else's code on your server is a real risk, and there's only one honest way to make it safe: you read it first. So we kept the script short and plain — just standard commands any admin would recognise, reading from sources like the proc filesystem the kernel already exposes. No compiled agent, no background daemon, nothing you can't see.

That raw data goes to the nearest CleverUptime server, where it's parsed into a picture of the machine:

  • hostname, machine id, hardware vendor and board serial
  • OS and kernel version, uptime, timezone
  • CPU info, load, and iowait
  • memory and swap usage
  • disk usage, performance, and SMART health
  • partitions, mounts, and RAID arrays
  • network interfaces, open ports, and IP addresses
  • users and groups

Why a script and not an agent

A persistent agent is a second program to keep patched, secured, and trusted on every box. A short, readable script you can audit in one sitting is the opposite of that — less to run, and nothing you can't see.

The Monitors Set Themselves Up

Here's the part people don't expect: you don't configure anything. Because the script already saw what's running on the box, CleverUptime knows what to watch. Detect a web server like Apache or Nginx, and it creates checks that confirm ports 80 and 443 are reachable from the internet, that the homepage returns a healthy 200, and that things which should not be public — a stray .git directory leaking your source, say — aren't.

Detect a database like MariaDB or PostgreSQL, and it watches that 3306 or 5432 is not open to the world — because a database answering the open internet is the classic way data gets stolen. You start the script; the right checks appear. The kinds CleverUptime runs:

  • ICMP ping — is the host reachable at all?
  • port scan and port connect — the right ports open, nothing surprising
  • HTTP / HTTPS connect — the site answers, and answers correctly
  • SSL test and certificate — valid, and not about to expire
  • DNS and domain — the records that point the world at you

When Something Breaks, It Tells You Why

All of this is watched continuously, and CleverUptime keeps looking for trouble in the data. Say it spots a high load average — the box is being asked to do more than it has cores for, and to your customers the site feels slow or stuck. The obvious question is why, and that's where most tools leave you. CleverUptime takes the next step.

There's no hand-wavy “AI” here — it reasons the way an experienced admin does, using what's known about how Linux machines actually break. Maybe the load is really iowait: the CPU is sitting idle waiting on a slow disk, so the answer is the disk, not a bigger server — and a failing drive would show in the SMART data too. Or maybe the disks are fine but memory is nearly gone, the kernel is swapping RAM out to disk, and the whole machine has gone treacle-slow. More RAM would help — but first, who's eating it?

CleverUptime finds a mysql process eating 90% of memory. There's the culprit. And the good news it can tell you: this often isn't “your server is too small” — it's frequently just a configuration default left untuned. One cause, one fix, instead of five red tiles and a guess. That's root-cause analysis.

Every Alert Carries the Fix

When that happens, the alert lands in your inbox, Slack, or by SMS — with what was detected, which process is behind it, and a link into the knowledge base article that explains the tool and the fix in depth. Not a one-line patch to paste blindly, but the why behind it — so the second time it happens, you already know the move. Start the script, and otherwise forget about it until there's genuinely something worth knowing.

Curious what CleverUptime would make of your own server?

Run one command and watch it read your server, set up its checks, and flag what to fix — the whole flow above, on your own box.

Check your server →