Skip to content
SPECIFICTION
Get listed

Piro

heva-co.github.io

WebWindowsmacOSLinuxiOSAndroid
Visit heva-co.github.io
Spec score 7.2 #21 of 25 in On-Call Scheduling Software

What it is

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.

Spec sheet

Purpose
Piro is a self-hosted status page, uptime monitoring, and incident response platform for engineering teams.Read 7 Oct 2026 · github.com
Product
Piro is a self-hosted status page, uptime monitoring, and incident-response platform for engineering teams.Read 8 Oct 2026 · github.com
Deployment
Piro can run checks in-process for single-region setups or use standalone workers for multi-region monitoring.Read 7 Oct 2026 · github.com
Integrations
Listed integrations include Google Chat, Jira, generic outbound webhooks, and Google Cloud Monitoring.Read 8 Oct 2026 · github.com
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.Read 8 Oct 2026 · github.com
Support
The security policy asks users to report vulnerabilities by email and says the team aims to respond within 48 hours.Read 8 Oct 2026 · github.com
License
Piro is released under the GNU Affero General Public License v3.0.Read 7 Oct 2026 · github.com
Headquarters
New York, NY, USARead 28 Sep 2026 · heva-co.github.io
Maker
The repository identifies heva Inc. as Piro's maker and shows a 2025 copyright notice.Read 8 Oct 2026 · github.com
Access controls
Piro lists OIDC and SAML 2.0 single sign-on and Owner, Admin, Member, and Viewer roles.Read 8 Oct 2026 · github.com
Alert channels
Personal paging channels include email, Telegram, Twilio SMS, and ntfy, with channel verification before paging.Read 8 Oct 2026 · github.com
Configuration
Services, checks, and alert rules can be declared in YAML and managed with the piro CLI, which supports plan, apply, and export commands.Read 8 Oct 2026 · github.com
Incident response
The platform supports on-call schedules, escalation policies, incidents, postmortems, and maintenance windows.Read 8 Oct 2026 · github.com
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.Read 8 Oct 2026 · github.com
Mobile alerts
Piro offers Android and iOS apps with end-to-end encrypted push notifications.Read 7 Oct 2026 · github.com
Mobile push
The maker says its Android and iOS apps support end-to-end encrypted push notifications.Read 8 Oct 2026 · github.com
Monitoring
Checks include HTTP, DNS, SSL certificate expiry, TCP, Ping, gRPC, sandboxed JavaScript, and inbound heartbeats.Read 8 Oct 2026 · github.com
Regions
Standalone workers can run in different regions, while single-region setups can run checks in-process.Read 8 Oct 2026 · github.com
Status pages
Its branded public status page includes uptime history, latency trends, incidents, and scheduled maintenance.Read 8 Oct 2026 · github.com

Strong points and limits

Strong points

  • Checks cover HTTP, DNS, SSL, TCP and gRPC.
  • Includes on-call schedules and escalation policies.
  • Supports OIDC and SAML 2.0 sign-on.
  • Mobile apps provide end-to-end encrypted push alerts.

Limits

  • Requires self-hosting.
  • AGPL-3.0 applies to paid or public managed services.
  • No product telemetry or tracking is stated.

Who it suits

Piro suits engineering teams that want to self-host monitoring, status pages and incident response. Its YAML configuration, CLI and API may suit teams managing checks programmatically.

Verdict

Piro combines monitoring, public status pages and incident workflows in self-hosted software. Teams considering a managed service should account for the AGPL-3.0 requirement to make modifications available under the same license.

Where Specifiction places it

Alternatives to PiroAll alternatives →