Incido vs Piro
Incido
incido.appPiro
heva-co.github.ioSide by side
| Figure | Incido | Piro |
|---|---|---|
| Price from | €19/mo | — |
| Free plan | — | — |
| Free trial | Yes | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| iOS | — | Yes |
| Android | — | Yes |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 4 | 0 |
| Spec score · On-Call Scheduling Software | 8.1 (#11) | 7.2 (#21) |
| Headquarters | Luzern, Switzerland | New York, NY, USA |
| Integrations | The integrations page lists Grafana alerts, Pingdom checks, inbound and outbound webhooks, and REST API; Slack notifications are marked beta. | Listed integrations include Google Chat, Jira, generic outbound webhooks, and Google Cloud Monitoring. |
| Maker | The imprint identifies Firstech AG at Hirschengraben 33, 6003 Luzern, Switzerland. | The repository identifies heva Inc. as Piro's maker and shows a 2025 copyright notice. |
| Product | Incido combines incident management, on-call paging, and status pages in one workflow. | Piro is a self-hosted status page, uptime monitoring, and incident-response platform for engineering teams. |
| Security | The privacy policy says Incido uses TLS encryption, encryption at rest, role-based access control, and regular security monitoring. | The maker says integration credentials and secret fields are encrypted in the database and that the self-hosted product has no telemetry, tracking, or phone-home. |
| Status pages | Status pages support branding, real-time updates, subscriber email notifications, component health, and scheduled maintenance. | Its branded public status page includes uptime history, latency trends, incidents, and scheduled maintenance. |
Plans
Incido
- Starter€19 a month
- Pro€89 a month
- Business€249 a month
- EnterprisePriced on request
In their own words
Piro
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.