MonoDuty
monoduty.com
- Free plan
- Web
- iPhone and iPad
- Android
- API
What MonoDuty is
MonoDuty is a workspace-based incident management service for teams responsible for production systems. It combines team-owned services, on-call schedules, escalation policies, Heartbeats, uptime Monitors, and email, SMS, and voice notifications. Systems that can send HTTP requests can submit incidents through its Universal HTTP Webhook using MonoDuty’s documented JSON payload. 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, verifying HTTPS certificates, and alerting on recovery. A 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. The free plan retains incident history for seven days; Pro and Business retain it for 30 and 90 days respectively. A free plan is available, paid plans start at €9/user/mo, and a 14-day trial is listed. MonoDuty says it does not currently publish security certifications and runs production on one European virtual server without promised geographic failover or provider redundancy.
Who it suits
MonoDuty suits people responsible for responding when production systems break and who need explicit alert routes, schedules, and escalation policies. Teams with strict failover or certification requirements should weigh its stated infrastructure and compliance limits.
Good to know, and what to watch
- On-call scheduling is included in every published plan.
- Webhook ingestion accepts documented MonoDuty JSON payloads.
- Pro and Business send updates to three chat services.
- Monitors verify HTTPS certificates and alert on recovery.
- Free incident history retention is seven days.
- No security certifications are currently published.
- Production runs on a single European virtual server.
- Geographic failover and provider redundancy are not promised.
Plans
Every plan and priceFree
Pro
Business
Free plan · 14-day trial
Getting started
- Open the MonoDuty website
- Create a workspace on the Free plan or start the 14-day trial
- Connect systems through the Universal HTTP Webhook
- Configure services, on-call schedules and escalation policies
- Add Monitors for websites or APIs
- Choose email, SMS or voice notification routes
Limits to check
The Free plan allows 1 user, 3 services, 5 Monitors, 5 Heartbeats, 1 team, 1 on-call schedule, 5 webhooks and 50 incidents per month, with 7-day retention and email alerts. Pro and Business raise or remove these quotas and add expanded notification allowances.
The Club's review
MonoDuty is a workspace-based incident management service that combines on-call response with website and API monitoring. It is best suited to teams that want scheduling and escalation included from the free tier, with a clear per-user path to SMS and voice alerts. Its single-server infrastructure and lack of published security certifications make it a poor fit for deployments that require formal assurances or provider redundancy.
Overview
MonoDuty organizes incidents around workspaces and team-owned services. Teams can bring events in through a universal HTTP webhook, then coordinate response with schedules, escalation policies, and handoffs. Because scheduling is included in Free, Pro, and Business, even a small team can start with a basic on-call rotation rather than outgrowing an intake-only free tier immediately.
Monitoring is part of the same service: website and API checks run from Helsinki, track response time, validate responses, verify HTTPS certificates, and send recovery alerts. That makes MonoDuty a practical option for teams that want monitoring tied closely to incident response. Checks from a single location, however, do not provide geographic monitoring coverage.
Key features
Incident intake and coordination
The inbound integration is a universal HTTP webhook that accepts MonoDuty's documented JSON payload from HTTP-capable systems. It offers a straightforward route for compatible tools, but teams should confirm that their systems can produce the expected payload. Pro and Business can send incident lifecycle updates to Slack, Discord, and Microsoft Teams; these outbound chat integrations are unavailable on Free.
On-call and alerting
Rotation scheduling, escalation policies, and handoff tools support the core response workflow across the plans. Free sends email alerts only, while Pro adds monthly allowances of 500 SMS messages and 200 voice calls per user plan, and Business raises those allowances to 2,000 SMS and 500 voice calls. The paid tiers therefore suit teams that need more than email, though the message and call quotas matter if alert volume is high.
API and security
The REST API uses scoped, short-lived customer tokens, with a v1 allowlist covering incidents, services, and Monitors. TLS 1.2/1.3, hashed passwords and credentials where applicable, workspace roles, CSRF protections, rate limits, and optional time-based one-time-password MFA provide concrete security controls. MonoDuty does not currently publish ISO, SOC, payment-card, health-data, or similar security certifications, so organizations with formal certification requirements should choose a service that meets them.
The production service runs on one European virtual server and does not promise geographic failover, load-balanced application replicas, or provider redundancy. That is a material risk for teams whose incident-response service must itself remain available through infrastructure failures. Support is available through a help center, tickets, a contact form, and email; contact messages are reviewed on business days.
Pricing
MonoDuty uses a freemium model, with a free plan, a 14-day trial, and paid plans from €9/user/mo. Free is billed forever at no cost. It includes 1 user, 3 services, 5 Monitors, 5 Heartbeats, 1 team, 1 on-call schedule, 5 webhooks, and 50 incidents per month, plus email alerts and 7-day incident history retention. This is a useful starting point for an individual or a very small team, but the one-user limit and short retention restrict its usefulness for shared operational ownership.
Pro costs €9 a month, billed per user monthly, or €90/user/year charged once a year with annual billing. It supports up to 25 users, 3 Account Admins, 50 services, 50 Monitors, 100 Heartbeats, 10 teams, 10 schedules, 50 webhooks, and 5,000 incidents per month. Incident history lasts 30 days. The larger quotas, chat updates, and SMS and voice allowances make it the natural step up for growing teams that need shared response coverage.
Business costs €19 a month, billed per user monthly, or €190/user/year charged once a year with annual billing. It includes unlimited users and webhooks, 10 Account Admins, 500 services, 250 Monitors, 500 Heartbeats, 50 teams and schedules, and unlimited incidents, with 90-day history retention. Its larger allowances suit substantial response operations, but the per-user charge and published SMS and voice quotas still merit checking against expected usage.
Platforms
MonoDuty is available on web, Android, and iOS, and provides an API. The mobile apps give responders a way to access the service beyond the browser, while the API supports integrations and programmatic workflows.
Who it's for
MonoDuty is aimed at people responsible for production incidents and teams that value explicit, testable alert routes. The Free plan suits an individual evaluating a basic monitoring and on-call workflow; Pro is a better fit for teams that need multiple schedules, chat updates, and phone or SMS alerts. Business is aimed at larger operations with higher service, team, and incident limits. Organizations that need published security certifications, geographic failover, or provider redundancy should look elsewhere.
Pros and cons
- Pro: On-call scheduling is included at every plan level, so the free tier can support a real rotation.
- Pro: Monitoring combines response-time tracking, response validation, HTTPS certificate checks, and recovery alerts with incident management.
- Pro: Pro and Business add outbound chat updates and SMS and voice alerts for teams that need more than email.
- Con: Free is limited to one user, one team, one schedule, and 50 incidents per month, with only 7 days of history.
- Con: Monitoring checks run from Helsinki, and the production service has no promised geographic failover or provider redundancy.
- Con: The service does not publish major security certifications, which may rule it out for regulated or procurement-constrained organizations.
Alternatives
For a broader shortlist, compare On-Call Scheduling Software and On-Call Management Software.
- PagerTree is another freemium option with web and mobile apps and a free Basic plan for up to five users and two teams.
- PagerDuty is a freemium alternative available on web, mobile, API, and self-hosted platforms, with a free incident-management tier.
- TaskCall is worth comparing if unlimited global SMS and voice notifications are a priority; its Starter plan is $9 a month.
- incident.io offers a free Basic plan centered on native Slack or Microsoft Teams incident response, single-team on-call, and a status page.
- OpsKnight is a free, self-hosted, AGPL-3.0-only option with one status page per installation.
- MangoApps is a paid alternative with a Communications & Intranet plan priced at $9 a month from 200 employees.
- IncidentRelay is a free, open-source, self-hosted alternative.
- HeyOnCall offers a free trial for evaluating its service, with a 10-user trial plan.
Verdict
MonoDuty is a sensible choice for small and growing teams that want monitoring, on-call scheduling, escalation, and multiple alert channels in one service, with a usable free starting point. Its main advantage is the breadth of response workflow available across tiers; its main reason to look elsewhere is the single-server infrastructure and absence of published security certifications, especially where uptime guarantees or formal controls are essential.
The verdict
MonoDuty brings incident intake, monitoring, and on-call response into a workspace-based service. Its stated infrastructure and certification limitations are important considerations for production-critical deployments.
Questions people ask
Is there a free plan?
Yes. The Free plan costs nothing and is billed forever.
What do paid plans cost?
Pro is €9 a month per user, or €90/user/year when billed annually. Business is €19 a month per user, or €190/user/year annually.
Does MonoDuty offer a trial?
Yes. A 14-day trial is listed.
Which platforms are available?
MonoDuty offers Android, iOS, web and API access.
Can it send updates to team chat?
Pro and Business can deliver incident lifecycle updates to Slack, Discord and Microsoft Teams.
How long is incident history retained?
Retention is 7 days on Free, 30 days on Pro and 90 days on Business.
What the maker publishes
- API
- MonoDuty documents a REST API with scoped, short-lived customer API tokens and an explicit v1 allowlist for incidents, services, and Monitors. source
- Chat integrations
- Pro and Business can deliver incident lifecycle updates outward to Slack, Discord, and Microsoft Teams. source
- Compliance status
- MonoDuty states that it does not currently publish ISO, SOC, payment-card, health-data, or similar security certifications. source
- 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. source
- Headquarters
- Tallinn, Harju County, Estonia source
- Inbound integration
- The generally available inbound integration is a Universal HTTP Webhook that accepts the documented MonoDuty JSON payload from HTTP-capable systems. source
- 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. source
- Monitoring
- Monitors check websites and APIs from Helsinki with response-time tracking, response validation, HTTPS certificate verification, and recovery alerts. source
- On-call workflow
- Every published Free, Pro, and Business plan includes on-call scheduling. source
- Retention
- Incident history retention is 7 days on Free, 30 days on Pro, and 90 days on Business. source
- 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. source
- Support
- Support is available through a help center, support tickets, contact form, and email, with contact messages reviewed on business days. source
- Target users
- MonoDuty says it is built for people responsible when production breaks and focuses on explicit, testable alert routes. source
Checked against the maker's pages on 1 Oct 2026.