Get paged on Telegram when your bot goes silent.
DeadManPulse is a dead man's switch for trading bots, webhooks and APIs. Your process checks in on a schedule. When the check-ins stop, or an endpoint stops answering, you get a Telegram push.
Free plan: 1 monitor. No card, no email, no KYC.
An open port is not a running strategy.
A frozen loop can keep its port open and return 200 OK while it places no orders and manages no risk. Uptime checks miss that. Heartbeats do not.
Probe we call you
We hit your endpoint from the edge on your plan's interval. Suited to webhook receivers, APIs and bots that expose an HTTP port. A secret query token or custom header keeps your handler closed to everyone else.
Heartbeat you call us
Your process calls us. If the calls stop, you are alerted. Suited to the loop itself: strategies, schedulers, cron jobs, anything that should keep running.
# your heartbeat URL comes from the bot HEARTBEAT_URL = "https://deadmanpulse.pages.dev/hb/<your-token>" def beat(): try: requests.get(HEARTBEAT_URL, timeout=5) except requests.RequestException: pass # a failed ping must never stop the strategy while True: run_strategy_tick() # fetch, decide, place or cancel orders beat() # reached only if the tick completed time.sleep(10)
// your heartbeat URL comes from the bot const HEARTBEAT_URL = "https://deadmanpulse.pages.dev/hb/<your-token>"; const beat = () => fetch(HEARTBEAT_URL, { signal: AbortSignal.timeout(5000) }) .catch(() => {}); // a failed ping must never stop the strategy while (true) { await runStrategyTick(); // fetch, decide, place or cancel orders await beat(); // reached only if the tick completed await new Promise(r => setTimeout(r, 10_000)); }
# every minute, but only if the job itself succeeded * * * * * /opt/bots/run_check.sh && curl -fsS -m 5 "https://deadmanpulse.pages.dev/hb/<your-token>" > /dev/null
Ping at the end of each tick, after the exchange call succeeds. A hung request or a dead loop stops the pulse, and the silence is the signal.
Set up in 30 seconds.
Everything happens inside Telegram.
- 1Open the botStart @DeadManPulseBot. There is no signup form.
- 2Add a monitorSend
/heartbeat grid-bot-01to start a dead man's switch, or/add https://your-endpoint.comto probe a URL. - 3Wire it in and leavePoint your bot at the URL the bot gives you, or let the probe run. Alerts arrive in the same chat.
What it does, precisely.
The full feature list, without adjectives.
- Check interval
- 5 min on Free, 1 min on Pro, 30 s on Agency.
- Alert channel
- Telegram push, in the chat where you created the monitor.
- Noise control
- Consecutive-failure detection, so one dropped packet does not page you at 4 AM.
- Probe auth
- Secret query token or custom header, so only DeadManPulse reaches your handler.
- Data handling
- Stateless probes. Request payloads are not logged.
- History
- Incident history on every plan, including Free.
- Runs on
- Cloudflare edge.
- Billing
- USDT through @CryptoBot, inside Telegram. No card, no KYC.
What it will not do.
Read this before you rely on any monitor, ours included.
It cannot close your positions.
DeadManPulse tells you the bot is silent. It does not trade. It is an alarm, not a risk manager, so keep stop-losses on the exchange side.
It never needs your keys.
No exchange API keys, no wallet connection, no request payload logging. It only needs to know whether something answered.
Free until you outgrow it.
Upgrades are handled inside the bot and paid in USDT.
| Plan | Monitors | Interval | Price |
|---|---|---|---|
| Free | 1 | 5 min | $0 |
| Pro | 20 | 1 min | $9 USDT / mo |
| Agency | 50 | 30 s | $25 USDT / mo |
Pro adds a weekly report every Monday. Agency adds multi-workspace alerts, team notifications and custom alert thresholds.
Questions from people who run bots.
What if DeadManPulse itself goes down?
The probes run on Cloudflare's edge rather than on a single server of ours. Even so, no monitor is infallible, and that is why exchange-side stop-losses stay your last line of defense.
How fast will I be alerted?
Detection is bounded by your plan's check interval: 5 minutes on Free, 1 minute on Pro, 30 seconds on Agency. Consecutive-failure detection avoids false alarms at the cost of a slightly later alert. Once an outage is confirmed, the Telegram push goes out immediately.
Does it read my bot's data?
No. Probes are stateless and request payloads are not logged. It does not ask for exchange API keys or wallet access.
Which bots does it work with?
Anything that can make or receive an HTTP request: Python and Node scripts, CCXT bots, Hummingbot, Telegram and Discord bots, webhook receivers, cron jobs.
Do I need a card?
No. The Free plan needs nothing. Paid plans are billed in USDT through @CryptoBot inside the bot.
Create your first monitor in 30 seconds.
Free plan: 1 monitor. No card, no email, no KYC.