PylonMon
Server monitoring

Keep your infrastructure
healthy and online.

Monitor your servers, containers, and infrastructure in real time. Get instant alerts when something isn’t right — before it becomes a bigger problem.

No credit card required.

All servers healthy12 of 12 servers online
web-010.2%
web-020.1%
db-010.3%
cache-010.1%
worker-010.2%
CPU usage (last 24 hours)18%
Servers
Stay Healthy!
Buddy, the PylonMon mascot
Monitor everythingPhysical servers, VMs, containers, and cloud instances.
Instant alertsGet notified via email, Slack, Discord, SMS, and more.
Track key metricsMonitor CPU, memory, disk, network, and custom checks.
Reduce downtimeCatch issues early and keep your systems running.
Built for modern infrastructure
LinuxWindowsDockerKubernetesProxmoxAWSGoogle CloudAzure
Be proactive

Spot problems before
they impact your users.

Get real-time visibility into your infrastructure and resolve issues faster with actionable alerts and historical data. pylon-beacon pushes CPU, memory, disk and temperature out through one outbound connection — no open ports.

Learn more about server monitoring →
Your first 3 machines are free.

Install the agent, watch a machine appear within a minute, and get paged the moment it goes quiet.

Get Started Free →
No credit card required.
More about server monitoring

How the server monitoring works

1 · PUSH

The agent reports out

One small static binary pushes vitals over outbound HTTPS every 20 seconds. No listener, no open ports, nothing to firewall — it works behind NAT, CGNAT, and networks you don't control.

2 · WATCH

Thresholds + the clock

Set vital rules like disk > 90% or temp > 80°C. PylonMon watches from outside your infrastructure — so a dead host can't take its own alarm down with it.

3 · PAGE

You hear about it

Email, Slack, Google Chat, Discord, SMS, voice calls, webhooks and more — with escalation ladders that keep climbing until someone acknowledges.

THE SERVER IS UP. CAN A CUSTOMER STILL BUY?

Customer journeys

Vitals say the box is healthy; a journey proves the business is. A real browser signs in, adds to cart and checks out on a schedule, and pages you with the failing step and a screenshot when it can't. Written in plain lines — no code, no selectors to maintain.

Checkout monitoring →

Why push-based beats scraping

The classic server performance monitoring stack — Prometheus, exporters, a dashboard to babysit — means running more servers to watch your servers, opening ports, and maintaining scrape configs. A push agent inverts it: the machine reports out, so there's nothing to reach, nothing to expose, and nothing extra to host. And because the monitoring expects a heartbeat rather than answering a poll, a machine that dies takes exactly one push interval to be noticed — the dead-man's-switch per host that a scraper structurally can't give you when the network path is the thing that failed.

What the agent watches

  • CPU, memory & load — sustained-breach rules, not single-spike noise.
  • Disk, per mount — catch the log partition at 90% before it's at 100%.
  • Temperature — fanless boxes, closets and Raspberry Pis included; native ARM builds.
  • Custom metrics — one config line each: a queue depth, a battery %, anything a command can print.
  • SNMP devices on the LAN — the agent can poll a switch or UPS with no internet route and push its stats out for it.

The agent is open source (MIT), standard-library Go, a single static binary for Linux and Windows — small enough to read before you run it. Source on GitHub →

And the same account covers what agents can't reach: website & API uptime, HTTP/S, TCP, ping, DNS, TLS-certificate and domain-expiry checks, attack-surface exposure, AI model APIs, plus heartbeats for cron jobs and backups — one system, one place that pages you.

PylonMon vs. self-hosted monitoring: a monitoring stack that lives in your rack shares fate with the rack. When the power, the switch, or the hypervisor goes, it goes too — and nobody gets paged. Off-site is the point: PylonMon still has eyes when your infrastructure doesn't.

Common questions

Do I have to install an agent?

Only for inside-the-box vitals. Uptime, HTTP/S, TCP, ping and DNS checks run from our side with nothing installed. The agent is optional, open source, and takes about a minute per machine (Linux one-liner, or a PowerShell installer on Windows).

What's the overhead?

Nearly none — it's a single small binary with no runtime and no dependencies, sleeping between 20-second pushes. It runs happily on a Raspberry Pi.

What does it cost?

The free plan includes 3 agent-monitored servers with vital-threshold alerting, plus 20 monitors overall with 1-minute intervals. Paid starts at $9/mo — 30-second intervals, agent coverage up to your full monitor cap, SMS, and more monitor types. See pricing →

My servers are behind NAT / a corporate firewall.

That's the normal case, not the exception. The agent only makes outbound HTTPS requests — if the machine can reach the internet, it can report in. Nothing inbound, ever.

Watch your first 3 servers free →

About a minute per machine. No credit card.