Know the second a server
goes quiet.
PylonMon watches your websites, APIs, servers, cron jobs, and backups from outside your network — the dead-man's-switch for everything you can't afford to lose. When the whole thing goes dark, you still get the alert.
# drop one line at the end of your backup / cron job: curl -fsS https://pylonmon.com/hb/your-mon-id # miss your window, and PylonMon pages you: nightly-backup missed check-in — silent for 14m · SLA 10m
From signup to your first alert in under 60 seconds
Every way to watch anything
Whether a job checks in with us or we reach out to it, you find out the moment an SLA slips.
It pings us
Your cron jobs, backups, and devices curl a unique URL when they finish — they reach out to us. Miss the window and you're alerted — the silence is the signal.
We reach out
We poll a URL, open a TCP port, or ICMP-ping a host on your schedule, from off-site. Unreachable or non-200 trips an alert with the exact status. Paid tiers add DNS & UDP monitors, TLS-certificate & domain-expiry warnings, slow-response alerts, and Prometheus metric thresholds (push or pull).
What the internet sees
Monitors ask “is it up?” — Exposure asks “what is it showing?” Add a domain and we watch its public surface and tell you when it changes: a TLS certificate expiring, served with a broken chain — or a chain that quietly changed — nameservers or mail records that moved, SPF/DMARC that stopped protecting you, an IP that landed on a blocklist. Verify you own a host and we watch its open ports too, flagging anything that opens that shouldn’t. Nothing to install.
You get paged
Email, rich Discord cards, Slack, Teams, Webex, Telegram, ntfy.sh, web push, SMS, WhatsApp, voice calls, Zapier, or any webhook — with escalation ladders on every plan, incidents, public status pages, and on-call rotations on Team. One alert per state change. No 2am nag loops.
See it in action
Your monitors, attack-surface exposure, incidents, and a public status page — all in one clean console.
Every monitor, the live event feed, open incidents and every alert channel on one screen — with response time, CPU, memory, disk and temperature history you can point at when someone asks what happened at 3am.
PylonMonBreak something on purpose
Don't take our word for it — see your first alert in about 5 minutes, without risking anything real.
Create a heartbeat
Sign up free, add a heartbeat monitor called my-first-alert, set it to alert if silent for 5 minutes. You get a private ping URL.
Ping it once
curl https://pylonmon.com/hb/… — the monitor goes green. That's the whole integration.
Now stop
Just… don't ping it again. That's the "outage." When the deadline passes, your phone lights up. Nothing real broke — but now you know exactly what the real thing feels like.
We don't sell you an AI SRE. We page yours.
Every monitoring vendor is bolting on a hosted AI that wants credentials to your infrastructure. We went the other way: bring your own agent.
Your agent gets paged
Add an AI agent alert channel and every alert POSTs a structured envelope to your agent — monitor state, the open incident, write-back URLs, machine-readable instructions. Or let your agent drive PylonMon natively over our MCP endpoint.
On your infra, with your keys
Your agent already has the access you chose to give it — we never hold your credentials, run your models, or touch your instances. Agent-scoped API keys are the leash: read state, write incident notes — never create or destroy monitoring.
Findings before you're awake
The agent acks the incident, attaches evidence as-attributed notes on the timeline, and resolves with a write-up when it's verified fixed. You open the incident and the investigation is already done — or well underway.
How BYO-AI works — envelope, MCP tools & agent keys → · Enterprise plan
Simple pricing
Everything you need to run on-call for production — flat monthly pricing, never per-seat.
The price on this page is the price on your invoice. No per-host meters, no per-GB surprises, no usage tiers that spike the month something goes wrong. Your bill is boring on purpose — the alerts are where the excitement belongs.
- 20 monitors
- Log search — 1-day retention, 50 MB/day
- 1 alert channel — email, Discord, Slack, webhook, ntfy or web push
- 1-minute check intervals
- Heartbeat, HTTP/S, TCP & ping monitors
- pylon-beacon — 3 nodes (CPU/mem/disk/temp, open source)
- Escalation ladders
- 24-hour event history
- 75 monitors
- 10 alert channels
- Multi-region confirmation — an outage is verified from a second region before we page you, so a one-region routing blip never wakes you
- Log search — 7-day retention, 1 GB/day
- 30-second check intervals
- pylon-beacon nodes up to your monitor cap — with vital threshold alerts
- Prometheus & Alertmanager — metric monitors (push or pull) + your alerts as monitors (up to 25 alert streams)
- SMS allowance each month
- + DNS, UDP, TLS-cert & domain expiry, slow-response monitors
- Incidents, public status page & API
- Custom webhook payloads & maintenance windows
- Scrape your monitors into your own Prometheus
- 30-day event history + CSV export
- Priority email support
- 250 monitors
- 200 alert channels
- Everything in Pro
- On-call rotations — shifts, overrides, page-whoever-is-on
- Company-scale Prometheus — up to 200 inbound alert streams (Pro caps at 25)
- Bigger SMS allowance
- Telegram alerts · WhatsApp (planned)
- Teammates & roles (up to 5)
- 90-day event history
- Log search & live tail — 30-day retention, 5 GB/day
- 1000 monitors
- Unlimited alert channels
- Log search — 90-day retention, 20 GB/day (soft — talk to us past that)
- Everything in Team
- Bring-your-own-AI — alerts page your agent (MCP endpoint + agent-scoped keys); it writes findings back to the incident
- Voice-call alerts & on-call voice paging
- Up to 50 teammates
- Enterprise SSO (OIDC)
- Largest SMS allowance
- 24/7 priority support — round-the-clock, ahead of every other queue
Questions, answered
The things people ask before signing up.
Is there a free plan?
Yes — Free is free forever: 20 monitors, 1-minute checks, and heartbeat, HTTP/S, TCP and ping monitors with one alert channel. No credit card required.
What is heartbeat (dead-man's-switch) monitoring?
Your cron jobs, backups, and scripts send a quick HTTP ping to a unique URL when they finish. If PylonMon doesn't hear from a job inside its expected window, it pages you — the silence is the signal, so you catch jobs that die quietly.
Do I need to install an agent?
No. PylonMon watches from off-site: heartbeats are a single curl line, and HTTP, TCP and ping checks run from our side. There's nothing to install on your servers.
How is PylonMon different from UptimeRobot or Healthchecks.io?
It does both at once — outbound uptime checks and inbound heartbeat/cron monitoring — plus escalation ladders on every plan, multi-region outage confirmation on every paid plan, on-call rotations on Team, Prometheus and Alertmanager support, and alerts to email, Discord, Slack, SMS, WhatsApp and voice.
What alert channels are supported?
Email, Discord, Slack, Teams, Webex, Telegram, ntfy.sh, web push, SMS, WhatsApp, voice calls, Zapier and any webhook — with escalation on every plan and one alert per state change, no 2am nag loops.
Can it monitor cron jobs and backups?
Yes — heartbeat monitors are built for exactly that. Add one curl line to the end of your job; miss the schedule and you're alerted with how long it's been silent.