# FireHydrant — On-Call & Incident Management

FireHydrant by FireHydrant, Inc. holds a panel rating of 3/5 from 6 AI judges (category median 3/5), as of 2026-11-06. Provenance: Rest of world; sovereignty: 1 of 6 dimensions proven.

- Vendor: FireHydrant, Inc. (https://firehydrant.com)
- Category: [On-Call & Incident Management](https://whats-best.ai/software/incident-management.md)
- Provenance (editorial classification): Rest of world
- Canonical page: https://whats-best.ai/software/incident-management/firehydrant
- Alternatives: https://whats-best.ai/software/incident-management/firehydrant/alternatives ([markdown](https://whats-best.ai/software/incident-management/firehydrant/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-06 · oldest source captured 2026-11-06

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: FireHydrant, Inc.
- Headquarters: Incorporated in the United States [S15]
- Data hosting: Not stated on the vendor’s pages as of 6 Nov 2026
- Free plan: Yes, per the vendor’s own page [S9]

## The panel's verdict

FireHydrant scores highest on incident response and integration and administration (both 8), lowest on sovereignty; pricing transparency scores 5, on-call scheduling and alerting and routing 6-7, and reliability and compliance 5-7. The strengths are documented: incident declaration from Slack, Teams or the API, runbooks with conditional logic, internal and public status pages, retrospectives exportable to Google Docs, Confluence or PDF, integrations from Datadog and Grafana to ServiceNow and Jira, SAML SSO with SCIM, and a Signals Migrator from PagerDuty or Opsgenie. The weaknesses are structural: contracting is with FireHydrant, Inc. of New York under New York law, the published subprocessor list gives every listed provider a United States location, and we found no public information on a published data processing agreement. SMS and voice are 'available for purchase' without a price, and no per-alert rate is published for the consumption-based Signals pricing, so an annual cost is not computable. Reliability and compliance spans 5-7; SLAs are an Enterprise feature and the captured terms exclude time-critical or mission-critical use. No substantive disagreements were flagged; the widest spreads are two points.

**Speaks for it:**
- Incident response scores 8, with documented incident types, runbooks with conditional logic, internal and public status pages, retrospectives and MTTR analytics.
- Integration and administration scores 8 on named integrations from Datadog, Grafana, CloudWatch and Alertmanager to ServiceNow, Jira, Slack and Teams, plus SAML SSO, SCIM and audit logs.
- A Signals Migrator imports schedules, escalation policies and routing rules from PagerDuty or Opsgenie, and an open-source Terraform provider supports configuration as code.
- On-call scheduling is documented with layered primary and secondary rotations, stacking overrides, coverage-gap warnings at 9 am in the schedule's timezone, and escalation steps with per-step timeouts and team hand-offs.
- Alerting spans push, SMS, voice, email, WhatsApp and Slack with iOS critical alerts that bypass do-not-disturb, and routing matches any webhook body field with a default fallback route.

**Held against it:**
- Sovereignty scores 2-4, with contracting under FireHydrant, Inc. of New York and New York law and a published subprocessor list that gives every listed provider a United States location.
- We found no public information on a published data processing agreement, an EU contracting entity, or where incident and alert data is stored — the SSO documentation alone distinguishes EU-based instances.
- Pricing transparency scores 5, as SMS and voice are 'available for purchase' without a price and no per-alert rate is published for the consumption-based Signals pricing.
- Reliability and compliance spans 5-7, with SLAs an Enterprise feature and no public information on SLA credits, multi-region failover or named notification carriers.
- The captured 2022 subscription agreement (subscriptions purchased on or before March 31, 2026) excludes time-critical or mission-critical use, caps liability at six months' fees, and sets support hours at Monday to Friday, 9:00 to 17:00 Eastern.

**Best for:**
- You are migrating off PagerDuty or Opsgenie and want schedules, escalation policies and routing rules imported automatically.
- You need a documented incident process — declaration from Slack or Teams, incident types, conditional runbooks, status pages, retrospectives and MTTR analytics — for a team that runs real incidents.
- Your monitoring runs on Datadog, Grafana, CloudWatch or Alertmanager and you want routing on any webhook body field with configuration managed as code through the Terraform provider.
- You want to start on the free tier of up to ten responders, or price the Pro plan at "$25 /responder/month, billed annually", before committing.

**Avoid if:**
- Your procurement requires an EU contracting entity, a published data processing agreement, or clarity on where incident and alert data is stored — the captured pages show a New York contracting entity, and we found no public information on the rest.
- Your use is explicitly mission-critical — the captured subscription terms state the services are not licensed for time-critical or mission-critical functions.
- You must compute a full year's paging cost before signing — ask the vendor: the public pages we read do not show it
- You need vendor accountability for delivery failures before an Enterprise deal — SLAs sit in the Enterprise tier, the liability cap is fees paid in the preceding six months, and fees are non-refundable.

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The SRE Lead | The IT Operations Manager | The MSP NOC Lead | The ICT Risk Officer | The Engineering Manager | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| On-call schedules, rotations & escalation | 3.5/5 | 3/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Alert delivery, routing & noise reduction | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3/5 | 3.5/5 |
| Incident response, status pages & post-incident review | 4/5 | 4/5 | 4/5 | 4/5 | 4/5 | 4/5 |
| Integrations, API & administration | 4/5 | 4/5 | 4/5 | 4/5 | 4/5 | 4/5 |
| Platform reliability, security & compliance | 3/5 | 2.5/5 | 3.5/5 | 3/5 | 3/5 | 3/5 |
| European sovereignty | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 1/5 |
| Pricing transparency | 2.5/5 | 2.5/5 | 2.5/5 | 2.5/5 | 2.5/5 | 2.5/5 |
| **Weighted verdict** | **3.5/5** | **3/5** | **3.5/5** | **3/5** | **3/5** | **3/5** |

### The judges

- **The SRE Lead** (v1.0): Leads site reliability at a Berlin SaaS company with sixty engineers in eight product teams, Prometheus and Grafana for metrics, Sentry for errors and everything discussed in Slack. Wants an incident declared with one command, a channel with roles and a timeline, the status page updated from the same place, alerts grouped so one database outage does not page five teams, schedules kept in Terraform, and a postmortem that writes its first draft.
- **The IT Operations Manager** (v1.0): Runs IT operations for a packaging manufacturer with 900 staff and three plants running around the clock, with Checkmk and PRTG watching servers, networks and the production line. Five administrators share a weekly standby. Wants a Checkmk alert to become a phone call that the right person acknowledges by keypad, the deputy called after ten minutes, no pages during planned maintenance, and an alerting service that still works when the plant's own network is the thing that is down.
- **The MSP NOC Lead** (v1.0): Leads the network operations centre of a managed service provider in Nuremberg that looks after sixty mid-sized customers, with Zabbix, Microsoft Sentinel and Autotask in the stack. Wants alerts routed by customer and contract hours, tickets opened and closed in the PSA without anyone copying text, a separate on-call rota for the night shift and for each key account, one customer never seeing another's data, and a monthly report per customer on response times.
- **The ICT Risk Officer** (v1.0): ICT risk officer at a Frankfurt payments company supervised by BaFin, where DORA requires major ICT incidents to be classified and reported within hours. The incident tool is itself an ICT third-party service in the register. Reads the subprocessor list, asks where incident timelines and the AI summaries of the response channel are processed, wants an SLA, audit logs and a DORA addendum in the contract, and needs the timeline to hold up as evidence for the regulator.
- **The Engineering Manager** (v1.0): Engineering manager at a logistics software company in Hamburg with developers in Germany, Portugal and Poland, where the works council has agreed an on-call policy with paid standby hours and rest periods after a night call. Wants a follow-the-sun rota across three time zones, swaps from the phone, on-call hours exported to payroll each month, a warning when the same person is paged three nights running, and a price per responder that does not charge for the managers who only read along.
- **The Skeptic** (v1.0): Has seen "never miss an alert" from a pager that was down in the same cloud region as the outage it should have reported, "unlimited notifications" that meant twenty SMS a month outside the US, and an "AI incident assistant" that sent the whole response channel to a model nobody named. Asks which carriers deliver the calls, what the SLA pays, whether schedules and history can be exported when leaving — and what the plan costs once the stakeholders need seats.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: 1 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Incorporated in US | 0/2 | [S15] |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- CCPA: yes [S11]
- Coppa children: 13 [S15]
- Docs review: Documentation reviewed periodically [S11]
- DPA applicability: data processing agreement and customer's own privacy notice [S15]
- Dsr contact: support@firehydrant.com [S15]
- Enterprise admin: yes [S9]
- Infrastructure controls: Cloud Service Providers · Physical & Environment · Access Monitoring · App Security · Application Penetration Testing · Product Security · Audit Logging · Multi-Factor Authentication · Role-Based Access Control [S11]
- Security measures: yes [S15]
- Sig lite: yes [S11]
- SOC 2: yes [S11]
- SOC 2 and enterprise security: yes [S1]
- SSO SAML: SSO with SAML [S7]
- Vendor vetting: AI vendors vetted via SOC 2 Type II or ISO 27001 reports, policy documents, and penetration test reports [S25]
- Warranty: limited warranty: free from Errors during term [S14]

**Data**
- Aggregated license: yes [S14]
- Backups: yes · no [S14]
- Destruction after termination: 10 [S14]
- Export: yes [S14]
- Ownership: yes [S14]
- Post termination retrieval: 30 [S14]
- Retention marketing optout: indefinite [S15]
- Retention other: 3 [S15]
- Retention services: 6 [S15]

**Integrations**
- Alert routing alerting providers: Opsgenie · PagerDuty · Splunk On-Call (VictorOps) [S19]
- API authentication header: Bearer · fhb- [S8]
- API base endpoint: v1 · https://api.firehydrant.io/v1 [S8]
- API docs: yes [S13]
- API keys owner permission: yes [S8]
- API pagination: 200 · 20 [S8]
- API rate limit: 2023-02-07 · per account, shared across API keys · 50 · 300 [S8]
- API read only endpoint: https://api-read.firehydrant.io/v1 · yes · 30 [S8]
- API reference: yes [S3]
- API reference: yes [S6]
- API reference: yes [S9]
- API style: Bearer token · REST · JSON [S8]
- Atlassian statuspage: Integration with Atlassian Statuspage [S7]
- Calendar subscription urls: team_schedule_ics · user_shifts_calendar_url [S17]
- Conferencing: Cisco Webex Meetings · Google Meet · Zoom [S6]
- Count: page lists an all integrations catalog including AWS CloudTrail, AWS CloudWatch, Alertmanager, Bugsnag, Checkly, CircleCI, Cisco Webex Meetings, Cortex, Datadog, FHCLI, Freshservice, Giphy, GitHub, Google Cloud Stackdriver, Google Meet, Gr… [S6]
- Enterprise limit: unlimited [S9]
- Export targets: Google Docs · Confluence · PDF [S3]
- Featured: Slack · Microsoft Teams · Jira Cloud [S6]
- Fhcli: FHCLI CLI tool for CI/orchestration systems [S6]
- Free limit: 3 [S9]
- Jira: Atlassian Jira [S14]
- Jira cloud: Track proposed incident actions in Jira workflows [S6]
- Jira server: Jira Server (self-hosted) integration [S6]
- Microsoft teams: End-to-end incident management from Microsoft Teams [S6]
- Migration tool: Signals Migrator migrates PagerDuty or Opsgenie configs [S4]
- Monitoring alerting: AWS CloudTrail · AWS CloudWatch · Alertmanager · Bugsnag · Checkly · CircleCI · Datadog · Google Cloud Stackdriver · Grafana · Honeycomb · New Relic · Sentry · Site24x7 · StatusCake [S6]
- Okta: Okta SSO, MFA and provisioning integration [S6]
- Opsgenie: yes [S6]
- Pagerduty: yes [S6]
- Pagerduty opsgenie migration: PagerDuty · Opsgenie [S3]
- Pagerduty opsgenie migrator: Signals migrator for PagerDuty or Opsgenie configs [S6]
- Pro limit: 5 [S9]
- SAML: SAML 2.0 SSO integration [S6]
- SCIM available: yes [S23]
- Service now: ServiceNow ticket creation and CMDB/Service Catalog sync [S6]
- Slack: First-class Slack integration for managing incidents [S6]

**Legal**
- Controller location: United States [S15]
- Documents: Services Agreement · Privacy Policy · Cookie Policy [S13]
- Entity: FireHydrant, Inc. [S14]
- Entity name: FireHydrant, Inc. [S15]
- Export control: yes [S14]
- Governing law: federal or state courts of New York County, New York · New York [S14]
- Last updated: 2022-03-14 [S14]
- Liability cap: fees paid in preceding 6 months [S14]
- No refund on termination: no [S14]
- Not mission critical: yes [S14]
- Ownership: FireHydrant is now part of Freshworks [S11]
- Privacy notice effective date: 1.2 · 2026-03-10 [S15]
- Publicity: yes [S14]
- Services agreement: yes [S9]
- Ssa scope: SSA applies to subscriptions purchased on or prior to March 31, 2026; from April 1, 2026 Freshworks Terms of Service apply [S14]

**Pricing**
- Additional users prorated: yes [S14]
- Enterprise custom: custom · yes [S9]
- Fees nonrefundable: yes [S14]
- Free tier: Free · yes [S9]
- Free tier user limit: 10 [S23]
- Late interest: 1.5 [S14]
- Model: alerts_sent · consumption_based · no [S2]
- Pro price: 25 [S9]
- Scaling: yes [S2]
- Switch savings claim: 50 [S9]
- Taxes: yes [S14]

**Product**
- Adhoc paging: yes [S18]
- Administration features: Administration features including RBAC [S7]
- AI drafted retrospectives: AI-prepared retrospective drafts including suggested follow-ups [S22]
- AI features: AI Copilot features (per docs navigation) [S7]
- AI insights: AI generates answers, identifies key findings and contributing factors, and suggests action items and follow-ups [S3]
- AI meeting transcripts: AI context from Zoom meeting transcripts/chat [S22]
- AI org toggle: AI features can be enabled/disabled organization-wide, with per-feature settings [S22]
- AI privacy first: Privacy-first AI approach, data remains under customer control [S22]
- AI status page updates: AI-suggested status page update drafts for internal and public audiences [S22]
- AI suggested incidents: Proactive comparison of ongoing incidents to previous incidents, suggested in Command Center and Slack [S22]
- AI summaries: AI-generated incident summaries for responders [S22]
- AI vetted partners: Customer chooses which AI features to enable; AI partners vetted against security criteria [S22]
- Alert analytics: alerts_per_person · alert_to_incident_ratio · alert_conversion_by_team [S2]
- Alert log levels: Info · Warning · Error · yes [S19]
- Alert logs default filter: Warn level and above [S19]
- Alert route actions: 4 · automatically declare an incident · send alert to Slack channel · create integration log · ignore alert [S19]
- Alert route condition chaining: yes [S19]
- Alert route conditions: Summary · Priority · Impacted Infrastructure · any webhook body field [S19]
- Alert route exclusive: first matching route wins, subsequent routes not evaluated [S19]
- Alert routing: conditional routing rules for inbound alerts from alerting and monitoring providers [S19]
- Alert subscriptions: yes [S2]
- Alert triggers to ep: yes [S18]
- Alerts decoupled: ack · dismiss · start_incident [S2]
- Analytics: Analytics with incident breakdowns by components and response metrics like remediation time [S7]
- Analytics dashboard: Analytics Dashboard provides a full view of incidents for metric analysis [S4]
- Atlassian statuspage support: yes [S21]
- Auto renewal: yes · 30 [S14]
- Calendar view modes: Month · Week · List · Timeline · Current/Next Shifts [S17]
- Capabilities: Alerting & On-call · AI Enriched Incidents · Incident Runbooks · Service Catalog · Incident Retrospectives · Incident Analytics [S13]
- Cel routing: Common Expression Language (CEL) [S2]
- Change events: Change Events ingestion via API, Kubernetes, and AWS CloudTrail [S7]
- Claim shifts: yes [S17]
- Concurrent phone notification steps: yes [S20]
- Coverage gap notifications: daily · weekly · none · 9 am schedule timezone · slack · email [S17]
- Coverage request email guaranteed: yes [S17]
- Coverage requests: web_app · slack · yes [S17]
- Custom domain branding: branded status page on custom domain supported [S5]

**Subprocessors**
- AI providers: OpenAI · Anthropic · Recall.ai · AssemblyAI · AI feature providers [S25]
- Anthropic: Large language models · United States [S16]
- Assemblyai: Audio transcription · United States [S16]
- Aws: Infrastructure and supporting services · United States [S16]
- Bugsnag: Error tracking and reporting · United States [S16]
- Change notice: Subprocessor list may change; updates posted on this page [S16]
- Datadog: Performance measurement and log analysis · United States [S16]
- Fastly: Content delivery · United States [S16]
- Google analytics: Analytics · United States [S16]
- Google infrastructure: Infrastructure and supporting services · United States [S16]
- Honeycomb: Performance measurement and log analysis · United States [S16]
- Intercom: Support communications · United States [S16]
- Launchdarkly: New feature rollout and management · United States [S16]
- Openai: Large language models and text embedding · United States [S16]
- Posthog: Product usage reporting · United States [S16]
- Pusher: Real-time browser updates · United States [S16]
- Recall AI: Video transcription · United States [S16]
- Registry: Subprocessors and Data Subject Requests sections available [S11]
- Salesforce: Sales and support automation · United States [S16]
- Segment: Marketing analytics reporting · United States [S16]
- Sendgrid: Transactional email delivery · United States [S16]
- Stripe: Credit card processing · United States [S16]
- Stripe: Stripe, Inc. · payment processing [S14]
- Third party services: yes [S14]

**Support**
- Documentation: documentation · quickstart · API_reference · system_status [S2]
- Enterprise level: premium · yes [S9]
- Manage on call permissions: teams the user is a member of · Manage On Call Schedules [S17]
- Pro level: Standard support [S9]
- Rbac escalation permissions: all teams · own teams only [S18]
- Security contact: security team contact via trust center [S11]
- Support hours: Mon-Fri 9:00-17:00 ET · email support@firehydrant.io · company holidays [S14]
- Vulnerability reporting: yes [S11]

167 more facts on the canonical page: https://whats-best.ai/software/incident-management/firehydrant

## Questions

### Is FireHydrant European?

No. whats-best.ai classifies FireHydrant as Rest of world. Its vendor, FireHydrant, Inc., is incorporated in the United States, per [the vendor’s page captured 6 Nov 2026](https://whats-best.ai/evidence/19654).

### Where does FireHydrant store data?

Not stated on the vendor’s pages as of 6 Nov 2026.

### Does FireHydrant have a free plan?

Yes. FireHydrant has a free plan, per [the vendor’s page captured 6 Nov 2026](https://whats-best.ai/evidence/19624).

### What are the best alternatives to FireHydrant?

As of 18 Nov 2026, the panel rates [ilert (4/5)](https://whats-best.ai/software/incident-management/ilert), [All Quiet (3.5/5)](https://whats-best.ai/software/incident-management/all-quiet) and [OneUptime (3.5/5)](https://whats-best.ai/software/incident-management/oneuptime) highest among the other 16 On-Call & Incident Management products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is [ilert](https://whats-best.ai/software/incident-management/ilert) (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [FireHydrant alternatives](https://whats-best.ai/software/incident-management/firehydrant/alternatives).

## What this page leaves out

- 17 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 5 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 5 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 2 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown.
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement.

## Sources

- [S1] Vendor homepage: https://firehydrant.com/ (checked 2026-11-06)
- [S2] Features page (on-call and alerting): https://firehydrant.com/signals/ (checked 2026-11-06)
- [S3] Features page (retrospectives): https://firehydrant.com/incident-retrospective/ (checked 2026-11-06)
- [S4] Features page (analytics): https://firehydrant.com/incident-analytics/ (checked 2026-11-06)
- [S5] Features page (status pages): https://firehydrant.com/status-pages/ (checked 2026-11-06)
- [S6] Integrations page: https://firehydrant.com/integrations/ (checked 2026-11-06)
- [S7] Documentation: https://docs.firehydrant.com/docs/what-is-firehydrant/ (checked 2026-11-06)
- [S8] API documentation: https://docs.firehydrant.com/reference/firehydrant-api (checked 2026-11-06)
- [S9] Pricing page: https://firehydrant.com/pricing/ (checked 2026-11-06)
- [S10] Security / trust page: https://firehydrant.com/security/ (checked 2026-11-06)
- [S11] Trust centre (Freshworks): https://trust.freshworks.com/?product=firehydrant (checked 2026-11-06)
- [S12] Public status page: https://status.firehydrant.com/ (checked 2026-11-06)
- [S13] About page: https://firehydrant.com/about-us/ (checked 2026-11-06)
- [S14] Terms of service (subscriptions before April 2026): https://app.firehydrant.io/legal/ssa (checked 2026-11-06)
- [S15] Privacy policy: https://firehydrant.com/privacy-policy/ (checked 2026-11-06)
- [S16] Subprocessor list: https://firehydrant.com/security/subprocessors/ (checked 2026-11-06)
- [S17] On-call schedules, rotations & escalation — found from sitemap: https://docs.firehydrant.com/docs/signals-on-call-schedules (checked 2026-11-06)
- [S18] On-call schedules, rotations & escalation — found from sitemap: https://docs.firehydrant.com/docs/signals-escalation-policies (checked 2026-11-06)
- [S19] Alert delivery, routing & noise reduction — found from sitemap: https://docs.firehydrant.com/docs/alert-routing (checked 2026-11-06)
- [S20] Alert delivery, routing & noise reduction — found from sitemap: https://docs.firehydrant.com/docs/signals-notification-preferences (checked 2026-11-06)
- [S21] Incident response, status pages & post-incident review — found from sitemap: https://docs.firehydrant.com/docs/status-page-overview (checked 2026-11-06)
- [S22] Incident response, status pages & post-incident review — found from sitemap: https://docs.firehydrant.com/docs/ai-powered-incident-management (checked 2026-11-06)
- [S23] Integrations, API & administration — found from sitemap: https://docs.firehydrant.com/docs/sso-with-saml (checked 2026-11-06)
- [S24] Integrations, API & administration — found from sitemap: https://docs.firehydrant.com/docs/terraform-provider (checked 2026-11-06)
- [S25] Platform reliability, security & compliance — found from sitemap: https://docs.firehydrant.com/docs/firehydrant-ai-security-practices (checked 2026-11-06)

---

Cite as: whats-best.ai, "FireHydrant — On-Call & Incident Management", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/incident-management/firehydrant

Corrections: https://whats-best.ai/correct/1624?target=page
