Piro
heva-co.github.io
- Windows
- macOS
- Linux
- Web
- iPhone and iPad
- Android
- API
- Self-hosted
What Piro is
Piro is a self-hosted status page, uptime monitoring, and incident-response platform for engineering teams. It checks 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 and manage them with the Piro CLI or REST API. Monitoring can run in-process for a single-region setup or use standalone workers across different regions. Integrations listed include Google Chat, Jira, GCP Cloud Monitoring, email, Telegram, Twilio SMS, ntfy, and outbound webhooks. Its Android and iOS apps provide end-to-end encrypted push notifications. Piro supports OIDC and SAML 2.0 single sign-on, with 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; hosting it as a paid or public managed service for others requires making modifications available under the same license.
Who it suits
Piro suits engineering teams able to run self-hosted monitoring and incident-response software. Its configuration options and alerting workflows may suit teams managing services across one or multiple regions.
Good to know, and what to watch
- Checks cover HTTP, DNS, SSL, TCP, Ping, and gRPC
- Public pages show uptime history and incidents
- YAML configuration with CLI and REST API management
- Supports OIDC and SAML 2.0 sign-on
- Android and iOS encrypted push notifications
- Self-hosted deployment required
- AGPL-3.0 obligations apply to paid or public managed hosting
The verdict
Piro brings uptime checks, public status pages, and incident workflows into a self-hosted platform with mobile alerts and several configuration paths. Teams considering managed hosting for others should account for the AGPL-3.0 condition.
What the maker publishes
- Access controls
- Piro supports OIDC and SAML 2.0 single sign-on and Owner, Admin, Member, and Viewer roles. source
- Access controls
- Piro lists OIDC and SAML 2.0 single sign-on and Owner, Admin, Member, and Viewer roles. source
- Alert channels
- Personal paging channels include email, Telegram, Twilio SMS, and ntfy, with channel verification before paging. source
- Configuration
- Services, checks, and alert rules can be declared in YAML and managed with the Piro CLI or REST API. source
- Configuration
- Services, checks, and alert rules can be declared in YAML and managed with the piro CLI, which supports plan, apply, and export commands. source
- Deployment
- Piro can run checks in-process for single-region setups or use standalone workers for multi-region monitoring. source
- Headquarters
- New York, NY, USA source
- Incident response
- It includes on-call schedules, escalation policies, verified alert channels, incidents, and postmortems. source
- Incident response
- The platform supports on-call schedules, escalation policies, incidents, postmortems, and maintenance windows. source
- Integrations
- Listed integrations include Google Chat, Jira, GCP Cloud Monitoring, email, Telegram, Twilio SMS, ntfy, and outbound webhooks. source
- Integrations
- Listed integrations include Google Chat, Jira, generic outbound webhooks, and Google Cloud Monitoring. source
- License
- Piro is released under the GNU Affero General Public License v3.0. source
- License and hosting limit
- Piro is AGPL-3.0 software; hosting it as a paid or public managed service for others requires making modifications available under the same license. source
- Maker
- The repository identifies heva Inc. as Piro's maker and shows a 2025 copyright notice. source
- Mobile alerts
- Piro offers Android and iOS apps with end-to-end encrypted push notifications. source
- Mobile push
- The maker says its Android and iOS apps support end-to-end encrypted push notifications. source
- Monitoring
- It supports HTTP, DNS, SSL, TCP, Ping, gRPC, sandboxed JavaScript, and inbound heartbeat checks. source
- Monitoring
- Checks include HTTP, DNS, SSL certificate expiry, TCP, Ping, gRPC, sandboxed JavaScript, and inbound heartbeats. source
- Product
- Piro is a self-hosted status page, uptime monitoring, and incident-response platform for engineering teams. source
- Purpose
- Piro is a self-hosted status page, uptime monitoring, and incident response platform for engineering teams. source
- Regions
- Standalone workers can run in different regions, while single-region setups can run checks in-process. source
- Security
- The maker states that Piro encrypts integration credentials and secret fields at rest and has no product telemetry, tracking, or phone-home. source
- Security
- 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. source
- Status pages
- Its public status pages can show uptime history, latency trends, incidents, and scheduled maintenance. source
Checked against the maker's pages on 8 Oct 2026.