All systems operational

Monitoring
and incident response
in one product.

Checks run from 10 online geo locations across Europe and North America — then on-call, incidents and war rooms happen in the same place. Most tools do one half of that.

live dashboard
syschecks.com
api.production
12ms
db.primary
3ms
redis.cache
1ms
smtp.relay
89ms
cdn.edge-eu
24ms
agent.us-west
142ms
dns.resolver
8ms
7 services monitored
99.97% uptime

How it works

From a failing check to a handled incident

1

Add a check

Point it at a URL, host, DNS record, mail server or cron job. It starts running from every geo location within a minute.

2

It fails from more than one place

Two locations have to agree before anything fires, so one flaky route does not wake anybody up. A failed HTTP check also runs an MTR, so the network path arrives with the alert.

3

The response starts on its own

An incident opens, the on-call schedule decides who is paged, a war room is created and your status page tells customers — without anyone opening a second tool.

10
Global Locations
16+
Alert Channels
21,000+
Checks / 24h
5s
Min Check Interval

Geo monitoring

10 online locations

Public and private checks can be run from Europe and North America, so regional failures show up before users report them.

EU-FR
Roubaix, France
EU-PL
Warsaw, Poland
EU-DE
Frankfurt, Germany
EU-IT
Arezzo, Italy
EU-GB
London, United Kingdom
US-TX
Dallas, Texas
US-WA
Seattle, Washington
US-CA
San Jose, California
US-NY
New York
US-VA
Ashburn, Virginia

Detect

Detect finds it from every location before your users do.

Geo checks

HTTP/S from 10 locations, with certificate expiry and HSTS checked on the same run.

DNS and domain

Record changes, propagation across resolvers, glue records, and domain expiry before it bites.

Mail and heartbeats

SMTP, IMAP and POP3 reachability with DNS mail security, plus heartbeats for cron jobs that must run.

Respond

Respond puts the right person on it, with the room already open.

On-call and escalation

Rotations, overrides and escalation policies decide who is paged, without anyone maintaining a spreadsheet.

Incidents with a timeline

Every check result, acknowledgement and status change lands on one timeline you can read afterwards.

War rooms

A room opens with the incident: native chat, attachments, and a Zoom or Meet call created for you.

Communicate

Communicate tells your customers before they ask you.

Public status pages

Your own domain, incident history, uptime, subscribers, SVG badges and Atom feeds.

Private status pages

The same page restricted to the people you choose — for internal systems or a single customer.

Notification channels

Slack, Teams, Discord, Telegram, webhooks, e-mail, SMS and push, routed per check or per team.

The things behind your firewall get the same checks

Databases, internal APIs and appliances that no hosted monitor can reach are watched by a small Go agent you run yourself. It connects outbound only, so nothing internal has to be exposed, and its results sit next to your public checks.

One command on the target host and it registers itself.

Run on the target server as root

curl -sSL https://syschecks.com/api/agent/install.sh | bash -s -- \
  --token "<token>" --name "My Agent"

There is more than the three above

Multi-tenant organizations, role-based access, audit logs, and integrations with the tools you already use.

  • Cloud provider status for 40+ vendors, with early warnings before they announce
  • SLO tracking with error budgets and burn-rate alerts
  • API scenarios — multi-step flows with assertions, not just a status code
  • Maintenance windows that keep planned work out of your incident history
  • Prometheus and OTLP export, SVG badges, Atom feeds, PDF/CSV reports
  • Mobile app with push, swipe-to-ack and on-call management
Real-time
SSE live updates
Distributed
10 global locations
Secure
MFA + SSO + 2FA
Observable
Prometheus + OTLP
IaC / GitOps-first

Declare your whole monitoring as code

Checks, on-call schedules, escalation policies, status pages, services, and multi-stage incident playbooks — all managed declaratively, reviewed in pull requests, and rolled out through your pipeline. No click-ops.

TerraformOpenTofuPulumiAnsibleSaltCrossplane · soon
Get started with Infrastructure as Code
# main.tf
resource "systeam_check" "api" {
 name = "API health"
 type = "uptime"
 url = "https://api.example.com"
}

resource "systeam_playbook" "sev1" {
 name = "SEV1 response"
 trigger_type = "inbound_incident_created"
 step { action_type = "setup_war_room" ... }
}
Free during beta

Syschecks is currently in beta and available completely free of charge. We do our best to ensure reliability, but we provide no SLA guarantees at this stage. Your data is backed up daily and retained for seven days. See our Terms of Service.

Switching from another tool?

Syschecks replaces four tools teams usually buy separately — geo monitoring, on-call, incident response and status pages. See how it compares to what you already use.

Ready to monitor?

Set up your first check in under a minute. Free during beta.