Guardian

Something changed on your network. Guardian already knows.

It watches the machines, the websites and the traffic you are responsible for — and for the routine problems, it does not just tell you, it fixes them. Built for the person who gets the call when the network breaks: one house, one office, or a hundred client sites.

Access is granted by hand right now, one deployment at a time.

What it watches

One sensor on the network, one page with everything on it. No hunting through six different admin panels to answer one question.

Who is on the network

Every device that joins, every device that goes quiet, and the ones you have never seen before. Name the ones you recognise once and Guardian stops asking about them.

Your servers

Disk, memory, load, and the updates waiting to be installed — including the ones that need a reboot before they count. You find out a disk is filling up while it is still a nuisance.

Your websites and certificates

Whether each site answers, how fast, and how many days are left on its certificate. An expiring certificate is a warning weeks out, not an outage on a Sunday.

Where the traffic goes

The names your devices look up, which ones were blocked, and which device asked. Useful when a smart TV is chatting to somewhere odd, and useful when something is broken and you need to know what it reached for.

What is exposed, and who is knocking

The ports actually reachable from outside, and the addresses trying them — where they are from and what they went after.

Who is around

Which phones and laptops are home, when they usually are, and how long they have been on today. The same signal answers "is anyone in the office?" and "how much screen time was that?".

How it works

Three steps, and you are looking at your own network.

  1. Install the sensor

    One command on any machine that stays on — a spare Pi, a NAS, a server you already run. It watches from the inside, which is the only place a network is honest.

  2. It reports to the hub

    The sensor sweeps on a schedule and sends up a summary of what it found. Nothing else leaves the network: no packet captures, no file contents, no traffic tunnelled anywhere.

  3. You get a dashboard and an alert

    A single page for the whole picture, and a notification when something actually changes — a new device, a site down, a certificate running out, a port that opened.

curl -fsSL https://my.guarder.io/install | sh -s -- --code YOUR-ENROL-CODE

The enrolment code comes from your own dashboard and is good for one sensor. Add a second network later and it gets its own.

Most tools tell you. Guardian fixes it.

An alert is only useful if someone acts on it, and at 2am nobody does. This is the part of Guardian that is not a dashboard.

A fixed list of repairs, not a shell

Guardian can restart a service that died, clear a log directory that filled a disk, renew a certificate that is about to lapse, re-block a DNS rule that fell off. That list is fixed and allow-listed: if a repair is not on it, Guardian cannot perform it, however it is asked.

Every repair has a cooldown

A fix runs, then that fix is locked for a while. A service that dies every ninety seconds gets restarted once and then escalated to you — because the second restart was never the answer, and a tool that keeps trying hides the real fault.

Tell it what to do, in words

There is an assistant on the dashboard that can read everything Guardian knows and run those same repairs. Ask it why the office internet was slow last night, or tell it to restart the thing that is stuck.

It asks first when it matters

Anything disruptive — a reboot, cutting a device off the network — is proposed, not performed. You see exactly what it intends to do and say yes. Every action, automatic or asked for, is written down with who or what triggered it.

Pricing

Per site, monthly. There is no card form yet — access is granted by hand and we agree billing with you directly.

Home

$9/mo

One home network: the devices on it, who is around, and what your gear is talking to.

Request access

Business Essentials

$49/site/mo

One office or shop: the network plus your servers, websites and certificates, with alerts that reach the right person.

Request access

Business Pro

$149/site/mo

For a site you cannot afford to have down: automatic repairs, the assistant, deeper history and scheduled reports.

Request access

Partner / MSP

$99/site

Many client sites in one place, white-labelled — your name and your colours on the dashboard and the reports.

Request access

Questions worth asking first

What can the sensor actually see?

What a device on your network can see by asking politely: which addresses answer and what hardware they claim to be, which ports on them are open, whether your sites and servers respond, and — if you point your DNS at Guardian — the names that were looked up and by which device. It does not read your traffic, capture packets, or open files. On servers you connect it over your own SSH access and it runs read-only checks, plus exactly the repairs you allow.

Where does the data live?

In the hub for your account, and nowhere else — it is not sold, not pooled with anyone else's, and not used to train anything. What leaves your network is the sensor's summary of what it found, over HTTPS. Self-hosting the hub on your own machine is possible, and today it is something we set up with you rather than a download.

What happens on my network if the hub is unreachable?

Nothing. The sensor is not in the path of your traffic — it watches from the side, so if it stops, or the hub is down, or your uplink is out, your network carries on exactly as before. The sensor keeps sweeping and sends what it collected once it can reach the hub again. The one exception is DNS filtering, which is opt-in and only in the path if you choose to point your devices at it; it keeps answering from its own cache and lists, without the hub.

How do I cancel?

Tell us and it stops at the end of the month you have paid for — no notice period and no exit call. Uninstalling the sensor is one command, and it leaves nothing behind. Ask and your data is deleted; ask and you get an export of it first.

Request access

Tell us what you are looking after and we will come back to you. No card, no automated trial — each deployment is set up by hand at this stage.