See inside every server you run.
The Capture agent reports CPU, memory, disk, network and temperature from your machines through a small REST API. The data is stored in your database and nowhere else.
Track CPU and memory with history.
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.
- Per-core usage and load averages
- Memory pressure over time
- Instant gauges backed by history charts
Get warned before a disk fails.
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.
- Capacity and I/O per disk
- S.M.A.R.T. health indicators
- Works with HDDs and SSDs
See throughput and heat per machine.
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.
- Bandwidth per interface, in and out
- Historical network charts
- Temperature readings per machine
Get an alert when a line gets crossed.
Set thresholds on hardware metrics and get paged when a machine crosses one. The alert arrives on the same 13 channels as your uptime alerts, so infrastructure and availability page the same way.
No second alerting stack to configure, no second place to check.
- Hardware thresholds you define
- Same 13 notification channels
- One alerting pipeline for everything
From one closet server to a rack of them.
Homelabs
Watch temperatures, disks and load on the hardware in your house without sending any of it to someone else's cloud.
Ops teams
One dashboard for a fleet's health, with thresholds that page the on-call channel before capacity problems become incidents.
Cost-conscious teams
Per-host pricing on hosted monitoring adds up fast. Capture is open source, so another server is another container, not another line item.
See what it covers and what it doesn't.
Covered
- Per-core CPU usage and load averages
- Memory pressure with history
- Disk capacity, I/O and S.M.A.R.T. health
- Network throughput per interface
- Temperature readings
- Docker container state collected by the agent
- Hardware thresholds with alerts
Out of scope
- Application performance monitoring: no code-level tracing or profiling
- Log collection and search for your applications
- Custom application metrics: Capture reports hardware, not business counters
For the technically curious.
A small open agent
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.
Nothing leaves your perimeter
The agent talks to your Checkmate server, results land in your database and go nowhere else. Air-gapped and compliance-sensitive environments stay that way.
Auditable like the rest
Agents are a trust decision: this one ships its source. You can read what Capture collects before you put it on a production box.
Uptime and hardware in one view
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.
Frequently asked questions
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 the anonymous daily heartbeat the Checkmate server sends (which you can turn off) never includes hardware metrics.
Yes. Set thresholds on hardware metrics and Checkmate alerts on the same 13 channels used for uptime monitoring, so your whole alerting story lives in one place.
Container status is covered through Docker monitors, with up and down alerts. The agent collects health and per-container usage; the dashboard views for those are upcoming.
Yes. Checkmate and Capture are both open source under AGPL-3.0. Monitor as many machines as you like with no per-host pricing.
