MonoDuty
EN
Get Started

Voice • SMS • Email • Escalations

Incident alerting for
an owned response path.

Route incidents by email, SMS or voice using on-call schedules and escalation policies. Start free without a credit card, then test your route.

Start Free — No Credit CardSee how it works
Release-gated channels
Email · SMS · Voice
Monitor worker
Helsinki
Pro trial
14 days

Illustrative incident route

EXAMPLE

An HTTPS check fails.

See a product walkthrough, not a measured delivery timeline.

Example routeSequence · illustrativeScroll to playSkip replay ↓
Monitors
Production APIHTTPS check failed
  1. Monitor result recordedThe Helsinki worker records the HTTPS result.
  2. Trigger evaluatedConfigured trigger conditions determine whether an incident opens.
  3. Notification queuedThe selected email, SMS or voice route is queued.
  4. Escalation evaluatedA configured policy can move responsibility to the next step.
  5. Responder action recordedMonoDuty records acknowledgement when a responder acts.

Test the route before you depend on it.

Timing and delivery vary with configuration, providers and network conditions.

How it works

One webhook in. Configured channels out.

HTTP-capable senders can use MonoDuty after mapping to the documented Webhook payload.

  1. Your system fires an alert

    Send the documented JSON fields to the service-specific Webhook URL.

  2. MonoDuty routes it

    Escalation policies and on-call schedules decide who gets woken up.

  3. MonoDuty queues notifications

    Email is available on Free; paid plans add SMS and voice allowances.

Documented Webhook

Connect an HTTP-capable sender.

Map the sender to MonoDuty’s documented JSON contract, use an idempotency key for retries and test the route.

  • Documented JSON
  • HTTPS endpoint
  • Idempotent retries
  • Controlled test

View documentation →

# Send a mapped test alert
curl -X POST https://mndty.com/YOUR_WEBHOOK_TOKEN \
  -H "Content-Type: application/json" \
  -d {"title": "CPU High", "severity": "critical"}

# Then test the configured email, SMS or voice route

Works with tools you already use: Universal HTTP Webhook

Everything you need

Built around an owned incident response path.

01 / DELIVERY

Email, SMS and voice delivery

Configure the channels included in your plan and validate each destination before production use.

02 / ROUTING

On-Call Scheduling

Create rotation schedules and overrides so incident responsibility follows your operating policy.

03 / HEARTBEATS

Heartbeats

Detect a missed check-in after the configured interval and grace period.

04 / MONITORS

Monitors

Run HTTP or HTTPS availability checks from the Helsinki worker and route failures into the incident workflow.

05

Webhooks

Send the documented MonoDuty JSON payload from an HTTP-capable monitoring tool or script.

06

Escalation Policies

On Pro and Business, define the next responsible step when an incident remains unacknowledged.

Features →

Ready to test your incident route?

Start with a 14-day Pro trial without a card. Paid activation is sales-assisted.

Start Free — No Credit CardSee pricing →