HeyOnCall vs Piro

HeyOnCall combines website and API monitoring with incident management and on-call paging. Checks cover HTTP and HTTPS availability and performance, response assertions, redirects, and request or response inspection. SSL monitoring validates certificates and chains and can warn before expiration; heartbeat and cron monitoring are also included. Teams can set timezone-aware rotations, change or trade shifts, and sync Google Calendar, Outlook, or iCalendar feeds. Unacknowledged incidents can escalate to another user, a rotation, or everyone in a rotation. Its iOS and Android Critical Alerts can bypass Do Not Disturb, silent or vibrate modes, and volume settings, and repeat until acknowledged. Alert sources include Datadog, Prometheus Alertmanager, Uptime Kuma, and other webhook-capable tools; notifications can be sent through Slack, email, Telegram, or webhooks. The API supports custom triggers, incident resolution, and custom payloads. Plans are billed monthly: Free Trial for evaluating is free, Solo is $3 a month, and Pro is $32 a month. The evaluation plan limits users and triggers, while paid plans are limited to 1000 triggers of each listed type.

Piro is a self-hosted status page, uptime monitoring and incident-response platform for engineering teams. Its checks cover HTTP, DNS, SSL, TCP, Ping, gRPC, sandboxed JavaScript and inbound heartbeats. Public status pages can show uptime history, latency trends, incidents and scheduled maintenance. Incident tools include on-call schedules, escalation policies, verified alert channels, incident records and postmortems. Teams can declare services, checks and alert rules in YAML, then manage them through the Piro CLI or REST API. A single-region setup can run checks in-process; standalone workers support monitoring across regions. Integrations include Google Chat, Jira, GCP Cloud Monitoring, email, Telegram, Twilio SMS, ntfy and outbound webhooks. Android and iOS apps provide end-to-end encrypted push notifications. Piro supports OIDC and SAML 2.0 sign-on and Owner, Admin, Member and Viewer roles. The maker says credentials and secret fields are encrypted at rest and that the product has no telemetry, tracking or phone-home. Piro is open source under AGPL-3.0; offering it as a paid or public managed service for others requires making modifications available under the same license.