Product / How it works
One signal in. A clear response out.
MonoDuty turns incoming system signals into owned incidents: receive the alert, route it through the right policy and notify the person on call.
Free signup · no credit card required
01 / The path
Three steps, one operational thread.
Start with a simple HTTP request, then add team routing and escalation without changing the source that sends the alert.- 01 / Connect
Create a Webhook
Create an endpoint, map the sender to the documented JSON fields, and POST the result to https://mndty.com.
- 02 / Route
Define who is responsible
Connect the service to your team, on-call schedule and escalation policy so each incident has a clear owner.
- 03 / Respond
Notify, acknowledge, resolve
MonoDuty sends the incident through the configured channels and keeps the response state in one workflow.
02 / Send a signal
If it speaks HTTP, it works.
The source can be a monitoring platform, a scheduled job or your own application. The first request stays intentionally small.Explore Webhooks documentationcurl -X POST https://mndty.com/YOUR_WEBHOOK_TOKEN \
-H "Content-Type: application/json" \
-d '{"title":"CPU High","severity":"critical"}'03 / Signal sources
Different inputs. The same response system.
Use the product that matches the signal you have; all three lead into incident ownership and notification.Webhooks
Accept alerts from monitoring tools, applications and scripts that can send an HTTP request.
↗02Heartbeats
Watch scheduled jobs for missing check-ins and turn silence into an actionable incident.
↗03Monitors
Check websites and APIs, then route availability failures into the same response workflow.
↗04 / Start