Monitor your VPS fleet without Prometheus.
PulseNode is a hosted dashboard with a one-command agent. CPU, RAM, disk, network, Docker containers and open ports — live in under a minute, with alerts in Telegram and email. No exporters, no YAML, no Grafana to babysit.
outbound-only agent · single Go binary · linux amd64/arm64
Single static binary · outbound-only · systemd-hardened · reports in under a minute.
curl -fsSLo /tmp/server-monitor-install.sh .../install.sh && sudo bash /tmp/server-monitor-install.sh agent▍
The exact command — with your dashboard URL and a one-time token — is generated when you add a server.
From zero to first metric in one minute.
Run one command.
Paste the install line into your server. The agent is a single static Go binary, set up as a hardened systemd service. Nothing to configure, nothing listening.
Watch metrics arrive.
Within a minute the server appears on your dashboard: per-core CPU, load average, RAM and swap, every disk mount, every network interface, uptime. Live over SSE — no refresh, no polling.
Get alerted where you live.
Set threshold rules like cpu > 85% with cooldowns. When a line is crossed, PulseNode pings you in Telegram or by email — one signal, not a wall of noise.
Your whole fleet on one screen. Breathing.
Every server card updates the moment the agent reports: CPU per core, RAM and swap, disk per mount, network per interface, uptime, Docker containers, open TCP/UDP ports with the process that owns them. Online, stale, offline — you watch state change in real time, not on the next refresh.
- per-core CPU + load averages
- disk usage per mount
- network per interface
- open ports with process names
Yesterday's spike, explained.
Zoom from the last hour out to seven days. CPU, memory, disk and network charts answer "what happened at 3 a.m." without SSHing in and squinting at top.
- 1h · 6h · 24h · 7d chart windows
- 7-day history on Hobby, 30-day on Pro
- live updates over SSE — no refresh
Alert rules in plain numbers.
Set a threshold like cpu > 85% and get a notification when it's crossed — and again when it recovers. Per-rule cooldowns mean one bad night doesn't turn into forty pings. Delivered to your Telegram and email, plus a heads-up when an agent goes silent.
Know what's actually running.
Every Docker container with status, image and uptime. Every open TCP/UDP port with its process name. When something dies — or something unexpected starts listening — you'll see it.
The view from outside.
External HTTP(S) checks show status, latency and TLS-certificate expiry for your public endpoints — see what your users see, right next to what your servers feel.
The right size of monitoring.
Prometheus is brilliant — for a platform team. Uptime checkers are great — for a status page. PulseNode sits in between: real server metrics, hosted for you.
| PulseNode | Prometheus + Grafana | Uptime checkers | |
|---|---|---|---|
| Setup time | One command, under a minute | Hours — exporters, scrape configs, dashboards | Minutes |
| CPU / RAM / disk / network | ✓ per-core, per-mount, per-interface | ✓ after you build the dashboards | ✗ external ping only |
| Docker & open ports | ✓ built in | extra exporters + panels | ✗ |
| External HTTP checks | ✓ status, latency, TLS expiry | blackbox_exporter, more config | ✓ |
| Alerting | Thresholds + cooldowns → Email, Telegram | Alertmanager, its own config language | ✓ basic |
| Cost on your servers | One lightweight static Go agent | Prometheus server + exporters to run and feed | None |
| Who maintains it | We do — it's hosted | You do — upgrades, storage, retention | They do |
If you already run Prometheus happily, keep it. PulseNode is for the rest of us. Full Prometheus comparison →
Fair questions.
Does the agent open ports or need SSH access?
No. The agent is outbound-only: it sends metrics over HTTPS to PulseNode and never listens on any port. We never connect to your server — no SSH keys, no inbound firewall rules, nothing to expose.
What exactly runs on my server?
A single static Go binary installed as a systemd service with hardening options enabled. It reads system stats (and the Docker socket, if present) and posts them out.
What data leaves my server?
Metric values only: CPU, RAM, disk and network numbers, listening ports with process names, container names and states. No file contents, no environment variables, no logs. History is queryable for your plan's window — 7 days on Hobby, 30 on Pro.
Which systems are supported?
Linux on amd64 and arm64. Any mainstream distro with systemd works with the one-line installer. The dashboard is hosted — there's nothing else for you to run.
What are the plan limits?
Hobby covers 5 servers with 7-day history; Pro covers 20 servers with 30-day history. Add and remove servers anytime; upgrading is one click.
Can I cancel anytime?
Yes. Billing runs through Lemon Squeezy — cancel from your receipt email in one click. See the refund policy for specifics.
What does "founder beta" mean?
PulseNode is young and run by one person. The core is stable and watches real production servers (the founder's own) around the clock — but you'll see rough edges, fast fixes, and features landing mid-week. Seats are limited so support stays personal.
I run my own projects on a handful of cheap VPSes. I didn't want to operate a Prometheus stack to watch them — and uptime pingers couldn't tell me a disk was quietly filling up. So I built PulseNode: first for my own servers, then for people like me.
It's a founder beta — small, honest, improving every week. If something's missing, email me. There's no support tier between you and the person who wrote the code.
— xaenox, founder · support@pulsenode.space
Two plans. No tiers-of-tiers.
Hobby
€5 /month
- Up to 5 servers
- 7-day history
- Live dashboard + charts
- Alert rules → Email + Telegram
- External HTTP(S) + TLS-expiry visibility
Pro
€15 /month
- Up to 20 servers
- 30-day history
- Everything in Hobby
- Founder support — direct line
Payments via Lemon Squeezy · VAT handled at checkout · Cancel anytime · Founder beta — seats limited