- Home
- On-Call Scheduling Software
- MonoDuty
MonoDuty
Tallinn, Harju County, Estonia
What it is
MonoDuty is a workspace-based incident management service for teams responding to production problems. It combines team-owned services, on-call schedules, escalation policies, Heartbeats, uptime Monitors, and email, SMS, and voice notifications. Its Universal HTTP Webhook accepts MonoDuty's documented JSON payload from systems that can send HTTP requests. Pro and Business plans can send incident lifecycle updates to Slack, Discord, and Microsoft Teams. Monitors check websites and APIs from Helsinki, tracking response times, validating responses, checking HTTPS certificates, and alerting on recovery. The REST API uses scoped, short-lived customer tokens, with documented access for incidents, services, and Monitors. Security controls include TLS 1.2/1.3, workspace roles, rate limits, and optional time-based one-time-password MFA. MonoDuty says it does not currently publish security certifications. Its production service runs on a single European virtual server without promised geographic failover, load-balanced application replicas, or provider redundancy. A free plan is available; Pro costs €9 a month per user, and a 14-day trial is listed.
For and against
For
- On-call scheduling is included in every published plan.
- Webhook accepts documented MonoDuty JSON payloads.
- Pro and Business send updates to three chat services.
- Monitors track response times and HTTPS certificates.
- Optional time-based one-time-password MFA is available.
Against
- Free incident history is retained for 7 days.
- No security certifications are currently published.
- Production runs on a single European virtual server.
- Geographic failover and provider redundancy are not promised.
The verdict
MonoDuty groups incident workflows, notifications, and monitoring in a workspace-based service, with a free plan and paid tiers. Its stated certification and infrastructure limitations are important considerations for teams assessing operational risk.
Who it suits
MonoDuty is aimed at people responsible for production systems when incidents occur. It may suit teams looking for on-call scheduling, alert routes, and website or API monitoring.
Plans and prices
Free
1 user · 3 services · 5 Monitors · 5 Heartbeats
Read 1 Oct 2026 · monoduty.com
Pro
Up to 25 users · 3 Account Admins · 50 services · 50 Monitors
Read 1 Oct 2026 · monoduty.com
Business
Unlimited users & webhooks · 10 Account Admins · 500 services · 250 Monitors
Read 1 Oct 2026 · monoduty.com
On the record
- API
- MonoDuty documents a REST API with scoped, short-lived customer API tokens and an explicit v1 allowlist for incidents, services, and Monitors.monoduty.com · read 1 Oct 2026
- Chat integrations
- Pro and Business can deliver incident lifecycle updates outward to Slack, Discord, and Microsoft Teams.monoduty.com · read 1 Oct 2026
- Compliance status
- MonoDuty states that it does not currently publish ISO, SOC, payment-card, health-data, or similar security certifications.monoduty.com · read 1 Oct 2026
- Core product
- MonoDuty provides workspace-based incident management, team-owned services, universal HTTP Webhook ingestion, on-call schedules, escalation policies, Heartbeats, uptime Monitors, and email, SMS, and voice notifications.monoduty.com · read 1 Oct 2026
- Inbound integration
- The generally available inbound integration is a Universal HTTP Webhook that accepts the documented MonoDuty JSON payload from HTTP-capable systems.monoduty.com · read 1 Oct 2026
- Infrastructure limitation
- The production service runs on a single European virtual server and does not promise geographic failover, load-balanced application replicas, or provider redundancy.monoduty.com · read 1 Oct 2026
- Monitoring
- Monitors check websites and APIs from Helsinki with response-time tracking, response validation, HTTPS certificate verification, and recovery alerts.monoduty.com · read 1 Oct 2026
- On-call workflow
- Every published Free, Pro, and Business plan includes on-call scheduling.monoduty.com · read 1 Oct 2026
- Retention
- Incident history retention is 7 days on Free, 30 days on Pro, and 90 days on Business.monoduty.com · read 1 Oct 2026
- Security controls
- The service uses TLS 1.2/1.3, one-way password and credential hashing where applicable, scoped API tokens, workspace roles, CSRF protection, rate limits, and optional time-based one-time-password MFA.monoduty.com · read 1 Oct 2026
- Support
- Support is available through a help center, support tickets, contact form, and email, with contact messages reviewed on business days.monoduty.com · read 1 Oct 2026
- Target users
- MonoDuty says it is built for people responsible when production breaks and focuses on explicit, testable alert routes.monoduty.com · read 1 Oct 2026
