Network automation and monitoring

Know what your network is doing before your customers tell you.

Cooee puts a small sensor at each of your sites. It checks the internet link, finds what's plugged in, watches the hosts you care about and tells you the moment something drops off.

Raspberry Pi or Docker Connects out to Cooee, no inbound ports Email alerts
Brisbane Site
Raspberry Pi sensor · last seen 12 seconds ago
Online
Reachability
100%
Latency
12.3ms
Hosts
10
Internet latency, last 24 hours
192.168.0.1Edge Router Online
192.168.0.5File Server Online
192.168.0.12Manager Laptop Offline

A cooee is the call you send out across the bush so the others know where you are, and that you're alright.

That's the job of every Cooee sensor. Each one checks in with home, says what it can see, and goes quiet only when something's wrong. Which is exactly when you hear about it.

Features

Turn on what each site needs

Everything is an integration you switch on per site. Turn one on and its checks are scheduled on that site's sensor for you, with sensible defaults you can change later.

Internet

Reachability and latency checked every minute, graphed over the last 24 hours, with your provider, circuit ID and support numbers kept alongside.

Hosts

Give it a subnet and it finds what's there. Name the devices that matter, see their open ports and services, and wake them with Wake on LAN from a Raspberry Pi sensor.

Basic networking

Point it at a gateway, a server or a peer on the far side of a VPN and it'll keep pinging, so you know when the path breaks.

HTTP status

Check that the portals, intranets and web apps your people rely on are answering with the status code you expect, from inside the site.

WireGuard

Group sites together and Cooee builds and syncs the WireGuard configs between their sensors, then keeps checking every peer can reach the others.

Alerts that reach you

When a sensor, a site or a watched host goes quiet, the right people get an email, with the time in that site's own timezone. You'll hear when it's back, too.

How it works

Up and running in an afternoon

1

Put a sensor on site

A Raspberry Pi in the comms cupboard or a Docker container on a box you already have. It connects out to Cooee, so there's no firewall hole to punch just to manage it.

2

Choose what to watch

Switch on the integrations that site needs. The sensor picks up its new checks and schedules on its next check-in. Nothing to configure on the device itself.

3

Get on with your day

Results come back to one dashboard across every site. If something drops off, you get the email. If it doesn't, you don't.

Who it's for

Made for networks that can't just be rebooted and forgotten

Carriers

See the service the way the customer sees it, from the customer's end of the link, not just from your core.

Enterprises

Every branch, warehouse and office on one page, each in its own timezone, with alerts going to the people who look after that site.

MSPs

Each customer is its own organisation with its own sites, sensors and users, so their data stays theirs.

Already running Cooee?

Your sites are checking in. Come and see what they've been saying.