FireHydrant
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by FireHydrant, Inc. · firehydrant.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
FireHydrant at a glance
- Vendor
- FireHydrant, Inc.
- Headquarters
- Incorporated in the United States source, captured 6 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 6 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 6 Nov 2026
- Panel verdict
- The AI panel rates FireHydrant 3/5, the mean of 6 judges. 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. how scores are made
- As of
- Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
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.
The scores
| Criterion | Panel median |
|---|---|
| On-call schedules, rotations & escalation | 3.5 of 5 |
| Alert delivery, routing & noise reduction | 3.5 of 5 |
| Incident response, status pages & post-incident review | 4 of 5 |
| Integrations, API & administration | 4 of 5 |
| Platform reliability, security & compliance | 3 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 2.5 of 5 |
On-call schedules, rotations & escalation
Show reasoningHide reasoning
How this is scored
Who is on call and what happens when nobody answers: schedules with daily, weekly and custom rotations, layers and follow-the-sun hand-offs across time zones, overrides, swaps and holiday cover, escalation policies with timeouts, repeat and fallback levels, round-robin and team escalation, calendar export and sync, reminders before a shift, on-call reports and hours exported for on-call pay and working-time rules, and a mobile app that shows the shift and lets a responder hand it over.
0 — No schedules or escalation of any kind; alerts go to a fixed list of people.
3 — A simple weekly rotation and one escalation step; overrides, layers, time zones and on-call reports are basic or not described.
5 — Schedules with several rotation types and layers, overrides and swaps from the app, escalation policies with timeouts and several levels, time-zone handling, calendar export, shift reminders, and a report of who was on call when.
8 — Follow-the-sun and multi-team schedules, round-robin and conditional escalation, coverage gaps flagged before they happen, schedules and policies managed as code or by API, and on-call hours exported per person for pay and working-time rules, all documented.
10 — Scheduling a large organisation runs on: every feature above with fairness and fatigue reports, rest-period rules enforced or warned, schedules imported from HR or workforce tools, and every scheduling limit documented per plan.
The SRE Lead
Rotations with primary and secondary layers, daily, weekly or custom hand-offs, overrides and coverage requests from Slack and the app, gap warnings before they bite, calendar feeds and shift reminders, escalation steps with timeouts, repeats and hand-offs to another policy or team — and a Terraform provider so schedules can live in code. What I found nothing on is an export of on-call hours per person for pay or working-time rules, or fairness reporting, which is the first thing our works council will ask for. 17 18 20 24 2
The IT Operations Manager
The on-call documentation covers what my five-admin standby rotation needs: daily, weekly and custom hand-offs, primary and secondary rotation layers, overrides that stack and survive rotation regeneration, calendar ICS export, shift reminders by email and Slack, and coverage-gap notifications sent daily or weekly at nine in the schedule's own time zone. Escalation policies are documented with per-step timeouts, repeats and hand-off to another policy or team, so paging a deputy ten minutes after the first alert is a documented pattern. I found no public information on exporting on-call hours for pay and working-time rules, or follow-the-sun hand-offs across regions. 17 18 20
The MSP NOC Lead
Every team can own schedules of layered primary and secondary rotations with daily, weekly or custom hand-offs, overrides that stack and survive regeneration, coverage requests with a guaranteed email path, shift reminders, ICS calendar export, and daily or weekly gap warnings at 9 am in the schedule's own timezone — enough for my night rota and my key accounts. Escalation policies add per-step timeouts, repeats and hand-off to another team, and configuration can run as code with the Terraform provider. I could not find round-robin escalation, follow-the-sun hand-offs, or an export of on-call hours per person for pay and working-time rules. 2 17 18 20 24
The ICT Risk Officer
Rotations with daily, weekly and custom hand-offs, primary and secondary layers, stacking overrides, coverage-gap warnings in the schedule's time zone, shift reminders and calendar ICS subscription are all documented, and escalation policies carry per-step timeouts, repeats and hand-off to another policy or team. We found no public information on round-robin escalation or on on-call hours exported per person for pay and working-time rules, which I would need for Arbeitszeit records. 17 18 20
The Engineering Manager
Daily, weekly and custom hand-offs, primary and secondary layers, stacking overrides, coverage requests from Slack and the web, shift reminders and personal calendar subscriptions are all documented, and unstaffed gaps are flagged in advance at nine in the morning in the schedule's own time zone — most of what our works council asked for. I found no public information on on-call hours exported per person for payroll or standby pay, on fairness or fatigue reporting that would warn when someone carries several nights in a row, or on an explicitly described follow-the-sun pattern across responder time zones. 17 18 20 2 7
The Skeptic
Rotations with daily, weekly and custom hand-offs, primary/secondary layers, overrides that stack and survive regeneration, coverage requests and shift claims from Slack or the web app, gap warnings at 9 am in the schedule's own timezone, ICS calendar links, shift reminders, and escalation policies with per-step timeouts, repeats and hand-off to another team are all documented in the manuals. I could not find on-call hours exported per person for pay and working-time rules, and round-robin escalation is nowhere in the captured pages, which is exactly what an on-call payroll argument needs. 17 18 20 2
Alert delivery, routing & noise reduction
Show reasoningHide reasoning
How this is scored
Whether the alert reaches a human and only the right one: notification by push, SMS, voice call, email and chat, critical alerts that override do-not-disturb on iOS and Android, personal notification rules with retries and fallbacks, acknowledgement by app, SMS reply or keypad, delivery receipts, live call routing for a hotline, routing rules by service, severity, payload and time, deduplication, grouping and correlation of related alerts, suppression and maintenance windows, heartbeats for silent failures, and inbound email and webhook endpoints.
0 — Sends no alerts to people; a dashboard or log viewer only.
3 — Push and email notifications with acknowledgement; SMS, voice, routing rules and noise reduction are basic or not described.
5 — Push, SMS, voice and email with personal notification rules and retries, critical alerts on mobile, acknowledgement from the app or by phone, routing by service and severity, deduplication, and maintenance windows.
8 — Alert grouping or correlation with its logic documented, routing on payload fields and time conditions, delivery receipts and a notification log per alert, live call routing, heartbeat monitoring, suppression rules, and the countries and channels where SMS and voice are delivered stated.
10 — Delivery that is evidenced, not promised: redundant SMS and voice carriers named with automatic failover, delivery statistics published, AI or rule-based noise reduction with measurable results, and every notification limit per plan documented.
The SRE Lead
Personal notification steps by priority across push, SMS, voice, email, Slack and WhatsApp, iOS critical alerts that beat do-not-disturb, SMS replies by code or emoji and voice calls you answer verbally, plus routing on any webhook body field with AND/OR chains and a documented first-match-wins rule, live call routing and alert grouping at the Enterprise tier. The grouping logic itself is not documented, and I found no public information on delivery receipts, heartbeat monitoring, maintenance windows, or which countries SMS and voice reach. 19 20 9 7 2
The IT Operations Manager
Every channel I need is documented — mobile push with iOS critical alerts that bypass do-not-disturb, voice calls the responder answers with verbal prompts, SMS with reply codes and even emoji reactions, email and WhatsApp — with notification steps per priority, configurable delays, concurrent zero-delay steps, and acknowledgement from the app or by phone. Routing rules run on any webhook body field through the Common Expression Language with Liquid templating, there is a default fallback route, alert logs with severity levels, Team Support Hours to stop pages outside working hours, and live call routing and alert grouping at the Enterprise tier. I found no public information on delivery receipts, heartbeat monitoring for silent failures, the logic behind alert grouping, or the countries SMS and voice delivery reaches. 2 7 9 19 20
The MSP NOC Lead
Routes match on any field of the webhook body with AND/OR chaining, Common Expression Language rules, Liquid templating, exclusive first-match execution and a default fallback, so I could route by customer straight out of the monitoring payload. Delivery spans push, SMS, WhatsApp, voice, email and Slack DM with priority-based personal ladders, concurrent zero-delay steps, SMS emoji replies, spoken responses on voice calls, and iOS critical alerts that bypass do-not-disturb. We found no public information on delivery receipts, heartbeat monitoring, or named carriers with delivery statistics, and alert grouping appears only as an Enterprise feature without its logic documented. 2 9 12 19 20
The ICT Risk Officer
Push, SMS, voice, email, WhatsApp and Slack delivery is documented with per-priority notification steps, concurrent phone steps at zero delay, iOS critical alerts that bypass do-not-disturb, and acknowledgement by SMS codes, emoji replies or verbal prompts; routing rules read any webhook body field with chained conditions, a first-match execution model and Liquid templating. We found no public information on heartbeat monitoring, delivery receipts, or the countries where SMS and voice are delivered — and the vendor's own status page was showing a live voice-delivery incident for Bulgarian Telenor customers at capture. 9 12 19 20
The Engineering Manager
Push, SMS, voice, email and WhatsApp delivery with per-person rules and delays, iOS critical alerts that override do-not-disturb, and answering by SMS code, emoji or voice prompts are documented, and routes match on priority and any field of the incoming webhook in a documented rule language with a default fallback route. I found no public information on delivery receipts, heartbeats, the logic behind alert grouping, or the countries where SMS and voice are delivered — Android critical alerts are not described, and alert grouping and live call routing sit in the custom-priced Enterprise tier. 20 19 2 9 7
The Skeptic
Push, SMS, voice, email, WhatsApp and Slack delivery with iOS critical alerts that override do-not-disturb, acknowledgement by app, SMS reply code, emoji reaction or verbal phone prompt, and routing rules matching any webhook body field with AND/OR chains plus a Common Expression Language rule engine — the delivery-side documentation is thorough. But we found no public information on delivery receipts, heartbeats or the countries where SMS and voice are delivered, alert grouping appears only as an Enterprise plan line with its logic undescribed, and a scheduled SMS maintenance window is attributed simply to 'our third-party service provider' — the carrier stays anonymous, which is the part I actually want to know. 19 20 9 12 2
Incident response, status pages & post-incident review
Show reasoningHide reasoning
How this is scored
What happens once the alert is a real incident: declaring an incident from Slack, Microsoft Teams or the app, a dedicated channel and video bridge, incident roles and commander, severities and incident types, runbooks, tasks and automated workflows, stakeholder updates, public and internal status pages with subscribers, a timeline, post-incident reviews and postmortem templates with follow-up actions, analytics such as MTTA and MTTR, and AI features that summarise, suggest causes or draft the review.
0 — No incident record of any kind beyond the alert itself.
3 — An incident list with status and notes; channels, roles, status pages and post-incident reviews are basic or not described.
5 — Incidents declared from chat or the app with severities, a Slack or Teams channel created, incident roles, a timeline, a public status page, stakeholder notifications, postmortem templates, and MTTA and MTTR reports.
8 — Workflows and runbooks that automate the response, incident types with their own process, internal and public status pages with components and subscribers, follow-up actions tracked into Jira or Linear, service catalogue and dependencies, and AI summaries with their data handling described.
10 — A response process a regulated enterprise runs on: every feature above with major-incident and regulatory reporting templates, cross-team analytics and learning reviews, AI features documented with model provider, data handling and an opt-out, and every limit per plan stated.
The SRE Lead
Incidents declared from Slack, Teams, the app or the API, pre-defined incident types that pull in the right people, runbooks with conditional steps that can update the status page themselves, auto-created internal status pages plus public ones with components and subscribers, follow-up actions tracked into Jira, MTTR analytics, and AI that drafts the retrospective, suggests status page updates and summarises Zoom transcripts with an organisation-wide on/off toggle. An explicit incident timeline and MTTA reporting are not shown on the captured pages, but this is close to the process my team would run on. 7 21 3 4 22 5 6
The IT Operations Manager
Incidents can be declared from Slack, Microsoft Teams, the interface or the API, with pre-defined incident types that pull in the right responders, a configurable severity matrix, runbooks with conditional logic that can update status pages automatically, built-in roles and task management, and both incident-specific internal pages and global public pages with component impact, custom domains and customer subscriptions. Retrospectives are customizable with templates and real-time collaborative editing, export to Google Docs, Confluence or PDF, and AI-drafted versions with suggested follow-ups; MTTR and participant counts ship out of the box and proposed actions track into Jira workflows. I found no public information on regulatory or major-incident reporting templates. 3 4 5 6 7 21 22
The MSP NOC Lead
Incidents are declared from Slack, Teams, the app or the API with pre-defined incident types that pull the right responders, a configurable severity matrix, runbooks with conditional logic that can update status pages, built-in task and role management, and MTTR and participant analytics out of the box. Status pages come as an auto-created internal page per incident, expiring 48 hours after resolution, and a system-wide external page with component impact, subscribers and custom domains. Retrospectives are collaborative and exportable to Google Docs, Confluence or PDF, with AI-prepared drafts and suggested follow-ups tracked into Jira, and the AI handling is described with organization-wide toggles and vetted providers, OpenAI and Anthropic among the named subprocessors. 3 4 5 6 7 16 21 22
The ICT Risk Officer
Declaration from Slack, Teams, the app or the API, pre-defined incident types, a severity matrix, runbooks with conditional logic, internal and system-wide status pages with subscribers, collaborative retrospectives exported to Google Docs, Confluence or PDF with actions tracked into Jira, and MTTR analytics are all documented. The AI features are documented with an organisation-wide toggle and vetted providers, which is the data-handling transparency I look for; we found no public information on regulatory or major-incident reporting templates. 3 4 6 7 21 22 25
The Engineering Manager
Declaration from Slack, Teams or the API, incident types that pull in the right responders and resources, runbooks with conditional steps that can update status pages, internal and public status pages with subscribers and a custom domain, retrospective templates with follow-up actions tracked into Jira, MTTR analytics, and AI summaries whose providers are named in the subprocessor list and which can be switched off per organization — that is a response process I could run a real incident on. I found no public information on major-incident or regulatory reporting templates or cross-team learning reviews, which is what keeps it off the top step. 7 22 3 5 21 4 6
The Skeptic
Incidents are declared from Slack, the app or the API, with pre-defined incident types, a configurable severity matrix, runbooks with conditional logic, task and role management, per-incident internal status pages, public status pages on a custom domain with subscribers, retros drafted by AI with follow-ups tracked into Jira, and MTTR analytics out of the box. The AI features carry an organisation-wide on/off switch with per-feature settings and named, security-vetted model providers — more disclosure than I usually get. What I did not find: MTTA reporting, major-incident or regulatory templates, or full per-plan limits on the response features. 7 6 21 22 3 4 5
Integrations, API & administration
Show reasoningHide reasoning
How this is scored
How the tool fits the stack and the organisation: inbound integrations with monitoring and observability tools (Prometheus, Grafana, Datadog, Zabbix, Checkmk, PRTG, Azure Monitor, CloudWatch, Sentry), outbound integrations with chat, ticketing and ITSM tools (Slack, Microsoft Teams, Jira, ServiceNow, ConnectWise, Autotask), bidirectional sync, a documented REST API, webhooks and a Terraform provider, teams and services, roles and permissions, single sign-on (SAML or OIDC) and SCIM, audit logs, multi-tenant or customer separation for service providers, and migration help from other tools.
0 — No integrations and no administration beyond a single shared account.
3 — Email and webhook intake and a few named integrations; the API, roles and single sign-on are basic or not described.
5 — Dozens of named inbound and outbound integrations including Slack or Teams and Jira, a documented REST API and webhooks, teams with roles, two-factor authentication, single sign-on, and an import path from at least one other tool.
8 — Bidirectional ITSM and ticketing sync, a Terraform provider or configuration as code, SCIM provisioning, granular roles per team, audit logs, service-provider or multi-tenant set-ups, and API coverage of schedules, escalations and incidents documented.
10 — Administration that scales across many teams and customers: every setting reachable by API with parity stated, audit logs exportable to a SIEM, SSO enforced with SCIM, white-label or sub-account management for service providers, and documented migration from the major competitors.
The SRE Lead
A catalog with Alertmanager, Grafana, Sentry, Datadog, ServiceNow with CMDB and Service Catalog sync, Jira Cloud and Server, Linear and Zendesk; a documented REST API with rate limits and a read-only endpoint; an open-source Terraform provider with its own docs; SAML single sign-on with Okta, Entra ID and Google, SCIM with automatic deactivation, audit logs, multiple organisations, and a Signals Migrator from PagerDuty or Opsgenie. Roles are Owner and Member with per-team on-call permissions rather than fully granular, and API parity across every setting is not stated. 6 8 23 24 9 2
The IT Operations Manager
The integrations catalog names Datadog, Grafana, CloudWatch, Alertmanager, Sentry, ServiceNow with CMDB and Service Catalog synchronization, Jira, Slack, Teams and more, backed by a documented REST API with bearer authentication, pagination and rate limits plus a read-only endpoint, an open-source Terraform provider, SAML SSO with Okta, Entra ID and Google, SCIM provisioning, audit logs and multiple organizations at Enterprise. The Signals Migrator imports schedules, escalation policies and routing rules from PagerDuty or Opsgenie, and permissions like Manage On-Call Schedules scope by team. The captured catalog does not name Checkmk or PRTG, so my path in would be the documented webhook intake, and I found no public information on two-factor authentication. 2 6 8 9 17 23 24
The MSP NOC Lead
The catalog runs deep on the monitoring side — Datadog, Grafana, Sentry, CloudWatch, Alertmanager among others — and outbound to Slack, Teams, Jira Cloud and Server, ServiceNow with ticket and CMDB sync, Zendesk and Freshservice, though I found no named integration for Zabbix, Checkmk, PRTG or Autotask, so my PSA work would ride on webhooks and the documented REST API with its read-only endpoint. A Terraform provider with source on GitHub, SAML SSO with Entra ID, Okta and Google, SCIM provisioning, Owner-versus-Member permissions scoped per team, audit logs and multiple organizations cover the administration side. The Signals Migrator imports schedules, escalation policies and routing rules from PagerDuty or Opsgenie. 4 6 8 9 17 18 23 24
The ICT Risk Officer
Dozens of named inbound and outbound integrations, a documented REST API with bearer auth, rate limits and a read-only endpoint, an open-source Terraform provider, SCIM, SAML SSO with multiple providers and just-in-time provisioning, multi-organisation support, audit logs and per-team on-call permissions are documented, plus migration from PagerDuty and Opsgenie. We found no public information on white-label or sub-account management for service providers. 6 8 9 17 23 24
The Engineering Manager
Dozens of named monitoring, chat and ITSM integrations, a documented REST API with rate limits and a read-only endpoint, an open-source Terraform provider, SAML SSO with SCIM and just-in-time provisioning, audit logs, multiple organizations, ServiceNow CMDB and Service Catalog sync, and a migrator from PagerDuty and Opsgenie are all on the public pages. I found no public information on white-label or sub-account management for service providers, and the captured documentation does not state that every schedule and escalation setting is reachable through the API. 6 8 24 23 9 17
The Skeptic
Dozens of named integrations in both directions — Datadog, Grafana and CloudWatch in; Slack, Teams, Jira, and ServiceNow with CMDB and Service Catalog sync out — a documented REST API with rate limits and a read-only endpoint, an open-source Terraform provider, SAML SSO with multiple providers and domain redirect, SCIM with automatic deactivation, audit logs, multi-organisation accounts, and a Signals Migrator that imports PagerDuty and Opsgenie schedules, escalation policies and routing rules. We found no public information on audit-log export to a SIEM or stated API parity for every setting, so it sits below the top of this scale. 6 8 24 23 9 2
Platform reliability, security & compliance
Show reasoningHide reasoning
How this is scored
Whether the pager works on the day everything else is down and holds up in an audit: an architecture independent of the customer's own cloud, multi-region or multi-zone hosting with failover, a stated availability or SLA with credits, the vendor's own public status page and incident history, delivery via redundant carriers, encryption in transit and at rest, security certifications (ISO 27001, SOC 2, BSI C5), penetration tests, data retention and deletion, audit trails, and what the vendor documents for DORA, NIS2, HIPAA or other regulated customers.
0 — Nothing on availability, security or how the service is operated.
3 — A claim of high availability or "enterprise security"; the SLA, status page, certifications and architecture are basic or not described.
5 — A public status page, a stated availability or SLA, hosting regions named, encryption in transit and at rest, ISO 27001 or SOC 2 stated, and data retention described.
8 — An SLA with credits published, the incident history public, multi-region failover or redundancy documented, redundant notification carriers named, certifications with their scope, a trust centre with reports on request, and a DORA or NIS2 addendum or mapping offered.
10 — Operation evidenced end to end: failover tested and published, independent audits (ISO 27001, SOC 2 Type II, BSI C5) with reports available, regulatory obligations for financial and critical-infrastructure customers explained in plain language, and the vendor's own post-incident reviews public.
The SRE Lead
A public status page with live incidents and scheduled maintenance, a 99.99% uptime statement, SOC 2 Type 2 and SIG Lite in the Freshworks trust centre, encryption in transit and at rest, penetration testing and MFA listed as controls, and retention and deletion after termination described. There is no published SLA with credits — SLAs sit in the Enterprise tier — and no public information on multi-region failover, redundant carriers or DORA and NIS2 support; the captured 2022 subscription agreement also states the service is not licensed for time-critical or mission-critical functions, which a pager buyer should read before signing. 2 9 11 12 14 15
The IT Operations Manager
There is a public status page showing live incidents — including a voice-call delivery problem — and scheduled third-party maintenance, a 99.99% uptime claim, SOC 2 Type 2 and SIG Lite in the Freshworks trust centre with encryption in transit and at rest, penetration testing, and retention spelled out with destruction of customer data within ten days of termination. SLAs appear as an Enterprise feature, but I found no public information on credits, multi-region failover, redundant notification carriers, or DORA and NIS2 documentation. For a plant running around the clock I must also flag that the captured subscription terms state the services are not licensed for time-critical or mission-critical functions. 2 9 11 12 14 15
The MSP NOC Lead
There is a public status page with incident history — currently showing voice-delivery trouble for Bulgarian Telenor customers and scheduled SMS maintenance in the United States and Canada — plus a Freshworks trust centre listing SOC 2 Type 2, SIG Lite, CCPA, penetration testing, encryption in transit and at rest, backups and audit logging, and the privacy notice spells out retention of up to six years for service data. A 99.99 percent uptime figure is stated on the features page and SLAs are listed as an Enterprise feature. We found no public information on an SLA with credits, multi-region failover, redundant carrier names, certification scopes, or DORA and NIS2 documentation. 2 9 11 12 15
The ICT Risk Officer
A public status page, a stated 99.99% uptime, SOC 2 Type 2 in the trust centre, encryption in transit and at rest, penetration testing and retention up to six years with destruction within ten days of termination are documented. The enterprise tier lists "SLAs" as a feature, but we found no public information on availability figures or credits, DORA or NIS2 material, or multi-region failover — and the subscription agreement itself states the service "will not be used... in connection with any of Customer's time-critical or mission-critical functions", with support hours of Monday to Friday, 9:00 to 17:00 Eastern, which I cannot reconcile with a pager under BaFin supervision. 2 9 11 12 14 15
The Engineering Manager
A public status page with incident history, a stated 99.99% uptime, encryption in transit and at rest, SOC 2 Type 2 in a trust centre alongside penetration testing and MFA, and retention periods of up to six years are documented. I found no public information on an SLA with credits published, multi-region failover, redundant SMS and voice carriers, or any addendum for DORA or NIS2 customers, and the subscription agreement itself says the service is not licensed for mission-critical use — an odd footing for a pager. 12 2 11 15 14 25
The Skeptic
A public status page with components and incident history, a stated 99.99% uptime, SOC 2 Type 2 and SIG Lite in the Freshworks trust centre, encryption in transit and at rest, penetration testing, and retention spelled out to the day. But the SLA appears only as an Enterprise plan line with no published credits, we found no public information on hosting regions, failover or named notification carriers, and the subscription terms state the service 'will not be used… in connection with any of Customer's time-critical or mission-critical functions' — a remarkable line to find in a pager contract, sitting next to a liability cap of six months' fees and no refunds. 12 2 11 15 14 9
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where alerts, incident timelines, chat transcripts, contact data, phone numbers and account data are stored and processed, and who the subprocessors are (hosting, SMS and voice carriers, push services, email delivery, AI summary and transcription models, analytics, support and payment tools). Independently sourced by the sovereignty pipeline. Telephony and push providers needed to reach a responder in another country are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (SMS and voice, AI, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models and notification carriers, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The SRE Lead
The contracting entity and data controller are FireHydrant, Inc. of New York, now part of Freshworks, and the public subprocessor list locates infrastructure (AWS, Google), the AI models (OpenAI, Anthropic), transcription, email, support and payment providers in the United States; the single sign-on documentation distinguishing EU-based instances is the only suggestion of EU hosting I found. The privacy notice refers to a data processing agreement governing processor data, but no published agreement appears on the captured pages. The chain is at least transparent — the list with locations is public — but nothing here is EU-anchored. 14 15 16 23 11
The IT Operations Manager
The contracting entity is FireHydrant, Inc. of New York, now part of Freshworks, and the subprocessor list is published with every entry located in the United States — Amazon Web Services for infrastructure, OpenAI and Anthropic for the AI features, AssemblyAI and Recall.ai for transcription, SendGrid for email, Stripe for payments, Intercom for support. The SSO documentation refers to EU-based FireHydrant instances, but I found no public information on an EU contracting entity or representative, where alerts, timelines and contact data are stored, or a published data processing agreement. 11 14 15 16 23
The MSP NOC Lead
Contracting is with FireHydrant, Inc. of New York under New York law and US export control, new subscriptions from April 2026 move to Freshworks terms, and the published subprocessor list places all eighteen providers — AWS, SendGrid, Stripe, Intercom, and OpenAI, Anthropic, AssemblyAI and Recall.ai for AI — in the United States. One support document distinguishes EU-based from North America-based instances, which suggests a European hosting option. We found no EU contracting entity or representative, no published data processing agreement and no stated safeguards for the US processing chain, so I would need contractual clarification before any customer data leaves my Nuremberg operations. 14 15 16 23
The ICT Risk Officer
The subprocessor list is published with locations for every processor — hosting on Amazon Web Services and Google, AI models on OpenAI, Anthropic, AssemblyAI and Recall.ai, email via Sendgrid, support via Intercom, payments via Stripe — and every one is in the United States, as are the contracting entity FireHydrant, Inc. of New York and New York governing law with venue in New York County. A data processing agreement is referenced for processor data, but we found no public information on a published data processing agreement, an EU contracting entity, or a stated hosting region — the SSO documentation alone refers to "EU-based FireHydrant instances" — so incident timelines, chat transcripts and the AI summaries all run through the US chain. 11 14 15 16 23
The Engineering Manager
FireHydrant, Inc. of New York is the contracting entity and the stated data controller, New York law governs, and the published subprocessor list places the infrastructure, email, payment and the AI model providers (OpenAI, Anthropic, Recall.ai, AssemblyAI) all in the United States. An SSO setup page does mention EU-based instances, but the captured pages do not state where incident timelines, chat transcripts or contact data would be held for them, and I found no public information on an EU contracting entity or a published data processing agreement — a data processing agreement is referenced in the privacy notice but we found no copy of it. 15 16 14 11 23
The Skeptic
The contracting entity is FireHydrant, Inc. of New York under New York law, the privacy notice names a United States controller, and the published subprocessor list gives every single entry — hosting on AWS and Google, email via SendGrid, payments via Stripe, the AI models OpenAI, Anthropic, Recall.ai and AssemblyAI — a United States location. The SSO pages do mention 'EU-based FireHydrant instances' for configuration purposes, but we found no public information on where alert, incident and account data is stored, on a published data processing agreement, or on any EU contracting entity or representative. 14 15 16 23
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per user or responder and per plan, whether stakeholders and viewers are free, how many SMS and voice notifications are included and what the rest cost per country, which features (incident response, status pages, AI, live call routing, SSO, audit logs) are add-ons or in higher plans, platform fees, minimum seats, annual versus monthly billing, and the currency and VAT treatment.
0 — No public prices at all; every customer is a sales call.
3 — A starting price per user exists, but notification limits, add-ons and the enterprise tier are unclear.
5 — Plans are public with their price per user and main inclusions, but at least one commonly needed piece (SMS and voice volume, status pages, AI, SSO or the top tier) is unpriced or "contact sales".
8 — Every plan priced publicly with its scaling rule, notification limits and overage prices stated, add-ons priced, stakeholder seats explained, minimum term and billing options and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of responders, stakeholders, notifications and status pages, with every add-on, overage and support fee and the cancellation and data-export terms published.
The SRE Lead
The pricing page shows a free tier with enumerated limits and a Pro plan at "$25 /responder/month, billed annually", while the Signals feature page states pricing is by how many alerts you send, with no per-alert rate anywhere; SMS and voice notifications are "available for purchase" without a price, the Enterprise tier is "Custom Pricing", and the terms state fees are exclusive of taxes with a thirty-day non-renewal notice. I can price the Pro plan but cannot compute a real annual cost for a given alert volume from these pages. 9 2 14
The IT Operations Manager
The plans are public with their inclusions: a free tier up to ten responders, Pro at $25 per responder per month billed annually with unlimited escalation policies and unlimited public status pages, and Enterprise at custom pricing; SMS and voice notifications are listed as available for purchase, and I found no public information on per-message costs or the per-alert rate for the consumption-based Signals pricing. The captured pages give different framings — the Signals page prices by alerts sent while the pricing page shows a per-responder fee — and the terms add that fees are non-refundable, exclusive of taxes, auto-renew with thirty days' notice, and late amounts bear 1.5% monthly interest. I cannot compute a full annual cost from these pages alone. 2 9 14
The MSP NOC Lead
Plans are public with their inclusions: a free tier up to ten responders, Pro at "$25 /responder/month, billed annually" with unlimited public status pages and escalation policies, and Enterprise at custom pricing where alert grouping, live call routing, AI, SCIM and SLAs sit. SMS and voice notifications are described as available for purchase without a price, and the Signals page prices by how many alerts you send without a per-alert rate, so I cannot compute what a month of paging across sixty customers would cost. The terms state fees are exclusive of taxes, subscriptions run monthly or annually with auto-renewal on thirty days' notice, and fees are non-refundable. 2 9 14
The ICT Risk Officer
The Free and Pro tiers are public with their limits — $25 per responder per month, billed annually, up to ten responders free, and integration, runbook and status-page counts per tier — and the terms state taxes are excluded, terms run monthly or yearly with auto-renewal on thirty days' notice, and added users are prorated. The headline model is consumption-based on alerts sent, yet we found no public information on what an alert costs or how many are included; SMS and voice are "available for purchase" without a price and Enterprise is custom pricing, so the real annual cost is not computable from public pages. 2 9 14
The Engineering Manager
A free tier, a Pro plan at $25 /responder/month, billed annually with its inclusions and limits, and an Enterprise tier at custom pricing are public, with fees stated exclusive of taxes and a thirty-day non-renewal notice. The pricing page prices Pro per responder while the Signals page describes pricing by how many alerts you send, and neither states the per-alert rate or the cost of the SMS and voice notifications that are available for purchase — so I cannot compute our annual cost; on the plus side for us, non-licensed users can look up who is on call, which suggests managers who only read along need no seat. 9 2 14 17
The Skeptic
The pricing page publishes a free tier (10 responders, 2 runbooks, 3 integrations, 1 public status page), Pro at $25 /responder/month, billed annually, and Enterprise at Custom Pricing, while the terms add that fees exclude taxes, renew automatically on 30 days' notice, and are non-refundable. But SMS and voice are only 'available for purchase' with no price attached, we found no public information on notification volume limits or overage rates, and the captured pages give different models — per-responder pricing for Pro against Signals being 'priced by how many alerts you send' with no per-alert figure published — so I cannot compute the annual cost of a paging team from what is public. 9 14 2
European sovereignty — proven facts
1 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in US
unverified
Why unverified?FireHydrant is now part of Freshworks Inc. (also a Delaware company), and from April 1, 2026 the Freshworks Terms of Service apply, so the contracting entity may change. |
0/2 pts | 15 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about FireHydrant
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.
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.
What are the best alternatives to FireHydrant?
As of 18 Nov 2026, the panel rates ilert (4/5), All Quiet (3.5/5) and OneUptime (3.5/5) 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 (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: FireHydrant alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 6 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. FireHydrant is now part of Freshworks Inc. (also a Delaware company), and from April 1, 2026 the Freshworks Terms of Service apply, so the contracting entity may change.
- Weak sourcing — Hosting location, Hosting options. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 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. Know more? Tell us
- 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. Know more? Tell us
- 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. Know more? Tell us
- 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. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 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. Know more? Tell us
Sources (25)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage firehydrant.com Checked 6 Nov 2026 Details →
- 2 Features page (on-call and alerting) firehydrant.com Checked 6 Nov 2026 Details →
- 3 Features page (retrospectives) firehydrant.com Checked 6 Nov 2026 Details →
- 4 Features page (analytics) firehydrant.com Checked 6 Nov 2026 Details →
- 5 Features page (status pages) firehydrant.com Checked 6 Nov 2026 Details →
- 6 Integrations page firehydrant.com Checked 6 Nov 2026 Details →
- 7 Documentation docs.firehydrant.com Checked 6 Nov 2026 Details →
- 8 API documentation docs.firehydrant.com Checked 6 Nov 2026 Details →
- 9 Pricing page firehydrant.com Checked 6 Nov 2026 Details →
- 10 Security / trust page firehydrant.com Checked 6 Nov 2026 Details →
- 11 Trust centre (Freshworks) trust.freshworks.com Checked 6 Nov 2026 Details →
- 12 Public status page status.firehydrant.com Checked 6 Nov 2026 Details →
- 13 About page firehydrant.com Checked 6 Nov 2026 Details →
- 14 Terms of service (subscriptions before April 2026) app.firehydrant.io Checked 6 Nov 2026 Details →
- 15 Privacy policy firehydrant.com Checked 6 Nov 2026 Details →
- 16 Subprocessor list firehydrant.com Checked 6 Nov 2026 Details →
- 17 On-call schedules, rotations & escalation — found from sitemap docs.firehydrant.com Checked 6 Nov 2026 Details →
- 18 On-call schedules, rotations & escalation — found from sitemap docs.firehydrant.com Checked 6 Nov 2026 Details →
- 19 Alert delivery, routing & noise reduction — found from sitemap docs.firehydrant.com Checked 6 Nov 2026 Details →
- 20 Alert delivery, routing & noise reduction — found from sitemap docs.firehydrant.com Checked 6 Nov 2026 Details →
- 21 Incident response, status pages & post-incident review — found from sitemap docs.firehydrant.com Checked 6 Nov 2026 Details →
- 22 Incident response, status pages & post-incident review — found from sitemap docs.firehydrant.com Checked 6 Nov 2026 Details →
- 23 Integrations, API & administration — found from sitemap docs.firehydrant.com Checked 6 Nov 2026 Details →
- 24 Integrations, API & administration — found from sitemap docs.firehydrant.com Checked 6 Nov 2026 Details →
- 25 Platform reliability, security & compliance — found from sitemap docs.firehydrant.com Checked 6 Nov 2026 Details →