Madar Ops
Know the moment your node has a problem — before your users do. Madar Ops watches your Substrate / Polkadot SDK nodes every few seconds and sends one clear alert to your phone when something goes wrong, a reminder while it lasts, and one message when it is fixed.
🔴 Node down
RPC stops answering. Reported only after several failed checks in a row, so a single hiccup never wakes you up.
⛔ No new blocks
The best block has not moved for longer than you allow — the chain or your node is stuck.
🧭 Finality behind
The finalized block falls too far behind the best block. Critical for validators, a warning for RPC nodes.
🔗 Too few peers
Peer count below your minimum. Zero peers is always critical.
⏳ Validator syncing
A validator that is still syncing cannot author or vote — you hear about it.
💾 Disk almost full
Free space on the disk holding your database drops below your limit. A full disk stops a node.
Alerts where you are
- Phone push with the free ntfy app — no account needed.
- Telegram through your own bot.
- Webhook (JSON) for Slack / Discord bridges or your own systems.
Every problem: one alert when it starts, a reminder while it is open, one “resolved” when it ends. No flapping spam.
Safe by design
- Runs on your server, next to your node. We never see your nodes.
- Read-only: it asks your node standard RPC questions only. It never holds keys and never signs anything.
- The status page listens on 127.0.0.1 only.
- No telemetry. The only thing that leaves your machine is the alert text, sent to the channel you chose.
- The Telegram token is never written to logs. Alert URLs must be https.
- The systemd service runs as its own user inside a locked-down sandbox.
Quick start (Linux)
- Install — downloads the right binary for your CPU, verifies its SHA-256 and creates the service.
curl -fsSL https://madar-network.com/downloads/ops/install.sh | sudo sh
- Put your settings in
/etc/madar-ops/madar-ops.toml— the config builder below writes it for you. - Test, then start:
sudo madar-ops check /etc/madar-ops/madar-ops.toml sudo madar-ops test-alert /etc/madar-ops/madar-ops.toml sudo systemctl enable --now madar-ops
Status page on the server: http://127.0.0.1:9620/ — open it from your computer through an SSH tunnel: ssh -L 9620:127.0.0.1:9620 user@server. Prefer to read the installer first? install.sh is short and plain.
Config builder
Add your nodes and at least one alert channel. Everything stays in your browser — nothing is sent anywhere.
Download
On Linux the installer does this for you. Manual downloads, with SHA-256:
| System | File | SHA-256 |
|---|---|---|
| Loading… | ||
To verify a file, sha256sum madar-ops-linux-x86_64 (Linux) or Get-FileHash madar-ops-windows-x86_64.exe (Windows) must print the same value. Full list: SHA256SUMS.
FAQ
Which chains does it support?
Any node built with Substrate / Polkadot SDK that exposes the standard JSON-RPC over HTTP (default port 9944): Polkadot, Kusama, parachains and solochains.
Does my RPC have to be public?
No. Run Madar Ops on the same server and use http://127.0.0.1:9944. To watch several servers from one place, point it at private addresses or a VPN.
Does it need “unsafe” RPC methods?
No. It uses only safe methods: system_health, chain_getHeader, chain_getFinalizedHead, system_version and system_chain.
How much does it cost?
It is free. Running a Polkadot or Kusama validator and want it watched from outside your servers too? See Madar Ops Pro — hosted monitoring by stash address, 7-day free trial.
Windows?
Download the .exe, run madar-ops-windows-x86_64.exe init, edit madar-ops.toml, then run check and run. Use Task Scheduler to start it at boot.
How do I upgrade?
Run the install command again. It replaces the binary and keeps your configuration.