pricing

Simple, transparent pricing

Start free with 20 monitors. Scale up when your infrastructure demands it. No hidden fees.

Free

$0/month

Perfect for side projects and personal servers.

✓20 monitors
✓Email alerts only
✓24-hour history
✓1KB output capture
✓1 status page
✓API & MCP access

Get Started Free

Pro

$12/month

For production workloads that can't afford silent failures.

✓100 monitors
✓Slack, Discord, Teams, PagerDuty & OpenClaw
✓90-day history
✓100KB output capture
✓Progress tracking & output search
✓Bulk import & cron scheduling
✓Anomaly detection (duration, frequency & error rate)
✓5 status pages
✓Priority support

Start Pro

Business

$39/month

For teams running critical infrastructure at scale.

✓200 monitors
✓Everything in Pro, plus:
✓365-day history
✓1MB output capture
✓Alert grouping & incidents
✓Incident summaries & postmortems
✓10 status pages

Start Business

Frequently asked questions

Can I try Pro or Business for free?

Start on the free plan with 20 monitors and upgrade anytime. Your monitors and history carry over. No trial period needed.

What happens if I downgrade?

You keep your existing monitors, but if you exceed the lower plan’s limit you’ll need to remove some before creating new ones. Integration alerts (Slack, Discord, etc.) will be disabled on Free.

How does the ping endpoint work?

Each monitor gets a unique URL. Send any HTTP request (GET, POST, or HEAD) to that URL after your job runs. If DeadPing doesn’t receive a ping within the expected window + grace period, it alerts you.

What is output capture?

Your cron jobs can send stdout/stderr in the request body when they ping DeadPing. Free captures up to 1KB, Pro up to 100KB, and Business up to 1MB per ping. Pro and Business can also search across captured output.

What’s the difference between Pro and Business?

Pro adds all alert channels (Slack, Discord, Teams, PagerDuty, and OpenClaw), anomaly detection, 90-day history, output search, and 5 status pages. Business adds alert grouping with incident management, post-incident summaries, a full year of history, 1MB output capture, 200 monitors, and 10 status pages. It’s built for teams managing critical infrastructure.

What is MCP and how does the MCP server work?

MCP (Model Context Protocol) lets AI assistants like Claude, Cursor, and Windsurf manage your monitors directly. Install the DeadPing MCP server as an npm package or connect to our hosted remote server, and your AI assistant can create monitors, check status, and investigate incidents on your behalf. MCP server access is included on all plans.

How does alert grouping work?

When multiple monitors fail around the same time (e.g., during a database outage that affects several jobs), DeadPing groups them into a single incident instead of flooding you with individual alerts. You get one clear notification listing all affected monitors. Alert grouping is available on the Business plan.

What’s included in incident summaries?

When an incident resolves, DeadPing generates a summary covering which monitors were affected, how long they were down, what output they captured during failure, and a timeline of events. Use these as starting points for postmortems. Available on the Business plan.

How does anomaly detection work?

DeadPing learns your job’s normal behavior from its last 50 pings. It then flags three types of anomalies: duration spikes (job taking significantly longer or shorter), irregular frequency (pings arriving at unexpected intervals), and error rate surges (sudden increase in non-zero exit codes). No thresholds to configure. It adapts to each monitor automatically. Respects your configured schedule and grace period to avoid false positives. Pro plan and above.