Probes see the outage.
Our agents see the cause.
External probes plus internal host agents — catch outages and their causes before your customers do.
Everything you need to stay online
Global probes, private agents, alerting and status pages — one platform, no duct tape.
Global uptime checks
HTTP, TCP, DNS, ping and more from multiple regions — down to 15-second intervals.
Private network agents
Lightweight agents inside your infrastructure watch internal APIs, databases and hosts no outside probe can reach.
Game server monitoring
Query Minecraft, CS2, Source and more — players, map, version, uptime.
Alerts that reach you
Email, SMS, voice calls, Discord and webhooks — with on-call schedules and escalation chains.
Status pages & incidents
Public and private status pages with incident timelines, maintenance windows and custom domains.
SLA & reliability reporting
Uptime, latency and SLA tracking built in — per monitor, per group, per status page.
Request & error tracing
Follow a request end to end — HTTP handler, cache and database calls in a single trace waterfall — while errors land in one dashboard with severity and resolution status.
MCP & AI-agent API
A built-in MCP endpoint lets Claude, Cursor and other agents create monitors, manage incidents and configure alerting through your API token — no copy-paste ops.
Webhooks & integrations
Push events to any endpoint — plus Discord, Slack-style webhooks, Telegram and status page subscriptions out of the box.
Two different networks. Only one is visible from outside.
Simple, transparent pricing
Early access is open — start on the free plan and grow into paid tiers.
For personal projects and basic monitoring.
- 15 monitors, 5-minute checks
- Game server monitoring included
- 2 status pages
- Community support
For professional applications and small businesses.
- 50 monitors, 1-minute checks
- Custom domain, 5 status pages
- 2 login seats + 10 notify seats included
For growing infrastructure and teams.
- 250 monitors, 15-second checks
- All 27 check types, 15 status pages
- Priority support
Three steps to full coverage
Enroll an agent
One install command per host. The agent registers itself, reports metrics, and starts listening for checks and commands.
Assign what to watch
Point monitors at public URLs or internal targets. Group them, set intervals, attach maintenance windows.
Let rules act
Event rules escalate, annotate, open incidents — or restart a service on the agent that saw it fail.
Same uptime checks. A second engine underneath.
Questions, answered
›Why would I install an agent?
External probes only see what is publicly routable. The agent sits inside your network and checks what actually matters — databases, internal APIs, cron jobs — and reports host metrics no probe can reach.
›Is remote execution on my servers safe?
Privileged commands — restarts, scripts, updates, reboots — can only be created after a step-up 2FA check, execute through an agent token scoped to your account, and land in a command history only editors can read. Agents can run with remote commands fully disabled.
›What happens during an outage?
Regions confirm the failure first, then the incident engine classifies it: public post, team-only alert, or critical escalation. Notifications, webhooks, on-call chains and status page updates all fire from the same event.
›Where does my data live?
Core infrastructure runs in Hetzner datacenters in the EU, operated by a German company. GDPR by design, not by checkbox.
›What does early access cost?
Early access starts free — the Free plan is included with every account. Paid plans run at launch pricing and stay fixed as long as you keep them.
The probe sees your front door. The agent sees the building.
Agents enroll in one command. Early access perks below.