Checkmate checks your websites and APIs from 6 continents, validates what they return, then pages the person who owns the monitor. All of it runs on your own servers.
A site that loads fine from Frankfurt can be unreachable from Sydney. Checkmate runs distributed checks through the GlobalPing network, so a regional outage shows up as a regional outage instead of a mystery.
Every check location is plotted on an interactive map with its latest result, which makes 'is it just me?' a question you can answer in one glance.
Your API can return an empty body, a stale cache or an error page with a cheerful status code. Checkmate goes past the status line: match keywords in the response, or query JSON bodies with JMESPath or a regex and fail the check when the answer is wrong.
That turns uptime monitoring into a basic correctness check for every endpoint your customers depend on.
One dropped packet should not wake anyone up. A monitor can require that the last n of m checks fail before it flips to down, so alerts fire on real outages instead of blips.
When a monitor does go down, Checkmate opens an incident with a timeline you can acknowledge and reviews later. Notifications go out on any of 12 channels, from email to PagerDuty.
Response time charts span a day, a week or a month, so a dependency that got 40 percent slower on Tuesday is visible on Wednesday, not after the postmortem.
Uptime percentages are tracked to two decimals per monitor. SSL certificate expiry sits on the same page, so one view covers most of what you ask about an endpoint.
Watch the services on your own hardware without shipping availability data to a third party. One compose file and the dashboard is yours.
Downtime costs revenue and trust. Validate the endpoints your checkout and API customers hit. Failures reach you before support tickets do.
Monitor every client site from one dashboard with no per-monitor pricing. Tags keep a large fleet sorted by client or project.
Set the polling schedule per monitor, from short intervals to custom schedules. Smart throttling backs off when a monitor has been stable, so a large fleet stays cheap to run.
Configure a monitor to flip only when the last n of m checks agree. Flappy networks stop producing flappy alerts, in both directions: down needs proof and so does recovered.
Route checks through a proxy, globally or per monitor. Useful when your instance sits behind strict egress rules or when a target only admits traffic from known addresses.
Checks run from your instance and results land in your database. There is no phone-home, so the list of what you monitor is nobody's business but yours.
Uptime monitoring sends regular requests to a website or API and alerts you when it stops responding correctly. Checkmate runs these checks from your own server, records the results and notifies you the moment a monitor goes down.
Each check sends a request, then inspects the status code, optionally the response content and how long it took. You can require several failed checks in a row before the monitor flips to down, so a single network blip doesn't page anyone.
Yes. Beyond status codes, a monitor can match keywords in the response or query JSON bodies with JMESPath or a regex. If the shape or content of the answer is wrong, the check fails even when the status code is 200.
From your own Checkmate instance by default, with optional locations on 6 continents through the GlobalPing network. The distributed results are plotted on a map so regional problems are easy to spot.
Two tools. n of m confirmation flips a monitor only when the last n of m checks agree. Maintenance windows suppress alerts on a schedule while you deploy or patch.
Not for uptime monitoring. Checks run from the Checkmate server itself. The Capture agent is only needed if you also want hardware metrics like CPU, memory and disk from your machines.
Yes. Checkmate is open source under AGPL-3.0. Self-host it and every feature is included, with no monitor limits or per-check pricing.
Certificate expiry caught before browsers complain.
CPU, memory, disk and network via the Capture agent.
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.