The Capture agent reports CPU, memory, disk, network and temperature from your machines through a small REST API. The data lands in your database and nowhere else.
Per-core CPU usage, load averages and memory pressure, charted over time. A box that creeps from 60 to 95 percent over a month is a capacity decision you get to make early, instead of an outage that makes it for you.
The dashboard shows current gauges with the history behind them, so a spike and a trend look different at a glance.
Capacity and I/O tell you when a disk is filling or struggling. S.M.A.R.T. health indicators tell you when it is dying. Checkmate reports both, for spinning drives and solid-state alike.
Full disks remain one of the most preventable outages in self-hosted setups. This is the prevention.
Inbound and outbound bandwidth per interface, with historical charts that make a saturated uplink or a chatty backup job easy to spot.
Temperature readings round out the picture, which matters when your servers live in a closet instead of a climate-controlled datacenter.
Set thresholds on hardware metrics and get paged when a machine crosses one. The alert arrives on the same 12 channels as your uptime alerts, so infrastructure and availability page the same way.
No second alerting stack to configure, no second place to check.
Watch temperatures, disks and load on the hardware in your house without sending any of it to someone else's cloud.
One dashboard for a fleet's health, with thresholds that page the on-call channel before capacity problems become incidents.
Per-host pricing on hosted monitoring adds up fast. Capture is open source, so another server is another container, not another line item.
Capture is its own open-source project (bluewave-labs/capture on GitHub). It runs on the machines you monitor and exposes readings over a small REST API that your Checkmate instance polls.
The agent talks to your Checkmate server, results land in your database and no telemetry goes anywhere else. Air-gapped and compliance-sensitive environments stay that way.
Agents are a trust decision: this one ships its source. You can read what Capture collects before you put it on a production box.
Infrastructure monitors sit in the same dashboard as uptime, Docker and page speed monitors. When a service goes down, the host's CPU, memory and disk history is one click away.
CPU per core with load averages, memory pressure, disk capacity, I/O and S.M.A.R.T. health, network throughput per interface and temperature. Docker container state is reported alongside the host metrics.
Yes, for hardware metrics. The Capture agent runs on each machine you want to watch and reports through a small REST API. It is open source, so you can audit exactly what it collects.
No. Capture reports to your own Checkmate instance and the data stays in your database. There is no SaaS backend and no telemetry pipeline.
Yes. Set thresholds on hardware metrics and Checkmate alerts on the same 12 channels used for uptime monitoring, so your whole alerting story lives in one place.
Yes. Container status, health checks and per-container resource usage are covered, through Docker monitors as well as the host metrics Capture reports.
Yes. Checkmate and Capture are both open source under AGPL-3.0. Monitor as many machines as you like with no per-host pricing.
Websites and APIs checked from 6 continents.
Certificate expiry caught before browsers complain.
Container status, health checks and resource usage.
More than 100 game types over native protocols.
Branded public pages served from your own instance.
12 native channels, from email to PagerDuty.
All featuresCheckmate is open source under AGPL-3.0. Self-host it and this feature ships free, on your servers, with your data.