Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by HetrixTools · hetrixtools.com

Report an error on this page Is this your product? →

Link to this page

HetrixTools: AI-assisted analysis on whats-best.ai HetrixTools: AI-assisted analysis on whats-best.ai (dark)

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.

HetrixTools at a glance

Vendor
HetrixTools
Headquarters
Not stated on the vendor’s pages as of 10 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 10 Nov 2026
Free plan
Not stated on the vendor’s pages as of 10 Nov 2026
Panel verdict
The AI panel rates HetrixTools 2.5/5, the mean of 6 judges. HetrixTools is an uptime, blacklist and server monitoring service with status pages. how scores are made
As of
Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources

HetrixTools alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

HetrixTools is an uptime, blacklist and server monitoring service with status pages. Status pages is the only criterion never below 6: custom domain with automatic SSL, per-page passwords, timestamped incident updates, daily, weekly or monthly uptime reports, with the vendor's name removable only on Business and Enterprise. Checks and locations, alerting and on-call, automation and teams, and reports and reliability cluster at 5 to 6 — checks every minute from up to 12 locations, an outage confirmed only when most agree, 21 alert channels on every plan, unlimited history — while the captured pages give no information on escalation policies, on-call rotations, or browser and transaction checks. Pricing transparency sits at 3: "15 monitors free forever" is precise, but the Professional, Business and Enterprise plans carry no public prices and SMS and voice alerts are charged "using credits" with no credit price stated. Sovereignty, at 2 to 3, is where the scores split: the rationales weigh the same GDPR page — encrypted replication, 30-day backups, staged erasure — against an unnamed hosting country, an unshown subprocessor list and no data processing agreement.

Report an error

Speaks for it

  • Checks run every minute from up to 12 locations, with an outage called only when most of them agree
  • Status pages on every plan including Free, on a custom domain with automatic SSL, with per-page password protection
  • Twenty-one alert channels — email, SMS, phone calls, webhooks and 17 apps — on every plan, with alerts repeatable up to 30 times at intervals from 1 to 60 minutes
  • Outages, errors and response times kept with unlimited history on every plan, with ping and MTR samples and a screenshot captured after a failure
  • A free tier of 15 uptime monitors and 32 blacklist monitors "free forever", with every feature except sub-accounts

Report an error

Held against it

  • The captured pages give no prices for the Professional, Business and Enterprise plans, and no stated cost for the credits that SMS and voice alerts use
  • We found no public information on where data is hosted, the contracting entity's jurisdiction, the subprocessors on the referenced list, or a data processing agreement
  • We found no public information on escalation policies with timeouts, on-call schedules or rotations
  • We found no public information on browser, transaction or multi-step checks, or on TCP and port checks
  • We found no public information on single sign-on, SCIM, two-factor authentication or bulk monitor import

Report an error

Best for

  • You need a branded public status page with incident history and scheduled uptime reports, included even on the free plan
  • Your agency manages many client monitors and needs per-member visibility control, white-label reports and per-client password-protected pages
  • You want email, SMS, phone-call and webhook alerting available on every plan rather than gated by tier
  • You want outages confirmed by checks from several locations within the same minute before anyone is paged

Report an error

Avoid if

  • You need documented escalation policies, on-call schedules and rotations as part of your incident tooling
  • Your compliance process requires a named hosting country, a subprocessor list and a data processing agreement before adoption
  • You must verify checkout or login flows with browser or multi-step transaction checks

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Checks, locations & failure confirmation

Show reasoning
How this is scored

What can be monitored and how reliably a failure is detected: HTTP(S) with status code and keyword checks, TCP and port, ping, DNS records, SSL certificate and domain expiry, cron jobs and heartbeats, multi-step API checks with assertions, browser or transaction checks of a login or checkout, the shortest check interval, the number and regions of probe locations, the re-check from a second location before an alert, timeouts and response time thresholds, and private locations inside the customer's own network.

0 — Runs no checks of its own; a status page or alerting tool that only receives signals from other monitors.

3 — HTTP checks of a URL at a fixed interval with an up or down result; keyword, SSL, cron and the probe locations are basic or not described.

5 — HTTP(S), keyword, TCP or port, ping and SSL expiry checks, cron or heartbeat monitoring, an interval of one minute or less, several named probe locations, a failure confirmed from a second location before alerting, and response times recorded per check.

8 — Multi-step API checks with assertions on headers and body, browser or transaction checks of a user flow, DNS and domain expiry checks, sub-minute intervals, probe locations listed by city with the confirmation logic documented, private locations or agents for internal services, and maintenance windows that pause checks.

10 — Coverage and accuracy a reliability team runs on: every check type above with code-based checks (for example Playwright or scripted tests) in version control, location-specific thresholds, false-positive handling and probe health published, and the detection method documented so a result can be reproduced.

Report an error

The Agency Developer

Keyword checks, SSL expiry checked by default on every HTTPS monitor, domain expiry and nameserver-change warnings, and checks every minute from up to 12 locations with an outage confirmed only when most locations agree — that covers the certificate and domain watch I never want to learn about from a client's phone call again. The bot's user agent is published, its node IPs can be firewalled, and a failure captures ping, MTR, a screenshot and the source code. We found no public information on TCP or port checks, cron or heartbeat monitoring, browser or transaction checks of a login flow, or private check locations inside my own network. 1 3 4

Report an error

The SaaS Platform Engineer

One-minute checks from up to 12 locations, with an outage only confirmed once most locations agree and per-location error logs minute by minute, is exactly the failure-confirmation discipline I want, alongside keyword, SSL expiry, domain expiry and nameserver checks. We found no public information on multi-step API checks with assertions, browser or transaction checks, or TCP, ping and cron check types, and the locations are described only as around the world rather than named by city. 1 3 4

Report an error

The Customer Support Lead

Websites and servers are checked every minute from up to twelve locations, and an outage is only called when most of them agree — that confirmation logic is exactly what stops my team paging customers over a blip on one probe. Keyword, SSL expiry and validity, domain expiry and nameserver-change checks are documented, alongside response times and errors kept with unlimited history, per-location failure logs, and an open-source server agent for the machines themselves. We found no public information on TCP or port checks, ping as a standalone check, cron or heartbeat monitoring, multi-step API checks with assertions, or browser-flow checks. 1 3 4

Report an error

The E-Commerce Operations Manager

Every monitor is checked every minute from up to 12 locations, and an outage is only called when most of them agree — with self-healing nodes, per-location error logs minute by minute, and ping and MTR diagnostics captured during the outage. Keyword checks, SSL certificate expiry by default, certificate validity mismatches, domain expiry and nameserver changes are all documented, and short downtimes can be filtered out before alerting. We found no public information on browser or transaction checks of a checkout or payment flow, multi-step API checks with assertions, TCP or port checks, or probe locations named by city — for a shop whose checkout once failed for six hours while the homepage answered fine, that is what keeps this at the mid level. 1 3 4

Report an error

The Information Security Officer

Checks run every minute from up to 12 locations with an outage called only when most of them agree, keyword and SSL certificate expiry checks are documented (SSL expiry on by default, with domain expiry and nameserver change warnings), and each location's exact error is logged minute by minute. The bot's user agent is published and every check comes from a monitoring node whose IP we can allow-list in our firewall, which is the reproducibility an auditor asks for; we can also set a delay before alerting and pause alerts for planned work. We found no public information on TCP or port checks, cron or heartbeat monitoring, multi-step or browser checks, or private check locations inside our own network, and the locations are counted but no cities are given. 1 3 4

Report an error

The Skeptic

Every-minute checks from up to 12 locations with an outage called only "when most of them agree", plus keyword checks, SSL expiry by default, SSL authenticity, domain expiry and nameserver change warnings, per-location error logs minute by minute, and self-healing nodes across several hosting providers per location — the confirmation logic is the strongest part. We found no public information on TCP or port checks, ping or heartbeat monitors, multi-step or browser checks, sub-minute intervals, or probe locations named by city; open-source agents cover internal server metrics rather than checks run from inside the customer's network. Diagnostics are retained per event — ping and MTR samples plus a screenshot and page source captured after the failure — and the bot's behavior and user agent are documented, with checks blockable by IP. 1 3 4

Report an error

Alerting, escalation & on-call

Show reasoning
How this is scored

How the right person learns about a failure: alert channels (email, SMS, phone call, push app, Slack, Microsoft Teams, Telegram, webhooks), alerts to PagerDuty, Opsgenie or similar tools, escalation policies when an alert is not acknowledged, on-call schedules and rotations, acknowledge and resolve from the app, alert grouping and noise reduction, recovery notifications, maintenance windows that mute alerts, and whether SMS and calls are included or charged per message.

0 — No alerting at all; results can only be viewed in the dashboard.

3 — Email alerts and one or two chat integrations; escalation, phone calls and schedules are basic or not described.

5 — Email, SMS, a mobile push app, Slack, Microsoft Teams and webhooks, alerts forwarded to PagerDuty or Opsgenie, per-monitor alert contacts, recovery notifications, a delay or threshold before alerting, and maintenance windows that mute alerts.

8 — Phone call alerts, escalation policies with timeouts, on-call schedules and rotations with overrides, acknowledge and resolve from the app or chat, alert grouping, incident timelines with who did what, and the price of SMS and calls stated per country or included in the plan.

10 — On-call that replaces a separate incident tool: follow-the-sun schedules, escalation across teams, alert routing by service and severity, post-incident reviews generated from the timeline, and delivery of every alert channel monitored and reported.

Report an error

The Agency Developer

Email, SMS, phone calls, webhooks and 17 apps on every plan, alerts repeated up to 30 times until acknowledged, a minimum outage length before alerting, and maintenance mode that pauses alerts while monitoring carries on — a workable channel spread for an agency on-call rota. SMS and voice calls run on credits, and the captured pages do not state what a credit costs. We found no public information on escalation policies, on-call schedules, alert grouping or recovery notifications. 1 4

Report an error

The SaaS Platform Engineer

Phone calls and SMS to any number on every plan, plus webhooks and 17 apps, with a delay threshold before alerting, maintenance mode and repeat alerts up to 30 times until acknowledged, covers a lot of what a rotation needs. We found no public information on escalation policies with timeouts, on-call schedules and rotations, which specific chat or pager tools the apps are, or what an SMS or call credit costs. 1 4

Report an error

The Customer Support Lead

Twenty-one channels including email, SMS, voice calls and webhooks come with every plan, alerts can repeat up to thirty times until acknowledged, alerting can wait until an outage has lasted longer than a chosen time, and a maintenance mode pauses alerts while checking continues — the tools I needed during our last three-hundred-ticket incident. We found no public information on escalation policies with timeouts, on-call schedules and rotations, alert grouping, or what SMS and call credits cost per country. 1 4

Report an error

The E-Commerce Operations Manager

Email, SMS, voice calls to any number and webhooks are documented on every plan alongside 17 further apps — the SMS-and-call-the-person-on-duty channel I need in the March-to-June season exists. Alerts repeat every 1 to 60 minutes up to 30 times until acknowledged, short outages can be ignored, and planned maintenance mutes alerts. We found no public information on escalation to a second person when nobody answers, on-call schedules and rotations, or what the alert credits cost, so I cannot compute what a bad night of SMS and calls would cost. 1 4

Report an error

The Information Security Officer

Email, SMS, phone calls, webhooks and 17 built-in apps are available on every plan, with voice calls and text messages charged "using credits", alerts repeatable up to 30 times at an interval we choose from 1 to 60 minutes, and a maintenance mode that pauses alerts while monitoring continues. We found no public information on escalation policies with timeouts, on-call schedules or rotations, alert grouping, per-country SMS and call pricing, or the cost of a credit. Without documented escalation and rotations this cannot stand in for our incident tooling. 1 4

Report an error

The Skeptic

Twenty-one channels on every plan — email, SMS, phone calls and webhooks plus 17 apps — with repeat alerts up to 30 times during an outage, acknowledgement, a chosen minimum outage length before alerting, and maintenance mode that pauses alerts. We found no public information on escalation policies with timeouts, on-call schedules or rotations, alert grouping, or incident timelines, and the 17 apps are not named so we cannot confirm forwarding to PagerDuty or Opsgenie; SMS and calls run "using credits" whose price is not stated. 1 4

Report an error

Status pages & incident communication

Show reasoning
How this is scored

How customers and colleagues are told: public status pages on a custom domain with SSL, components and component groups fed automatically by monitors or set by hand, incident updates and scheduled maintenance announcements, subscribers notified by email, SMS, RSS or webhook, uptime history shown per component, private or password-protected pages for internal teams or single customers, branding and custom CSS, several languages, page templates, and how the status page itself stays online when the main product is down.

0 — No status page of any kind.

3 — A public status page listing monitors with their current state; custom domain, incident updates and subscribers are basic or not described.

5 — Public status pages on a custom domain, components linked to monitors, incident updates and scheduled maintenance, email subscribers, uptime history per component, the vendor's branding removable, and a password-protected or private page option.

8 — Component groups, SMS, RSS and webhook subscribers with per-component subscriptions, private pages with single sign-on or IP restriction, several languages, incident templates, embeddable status widgets, audience-specific pages for single customers, and the status page hosting kept separate from the main service and documented.

10 — Incident communication end to end: incidents drafted from monitor events and approved by a person, updates published to the page, subscribers, chat and social channels at once, a full incident archive with post-mortems, status page uptime published, and accessibility of the page stated.

Report an error

The Agency Developer

Public pages on my own domain with automatic SSL, logo, colours and light or dark mode, monitors grouped into ordered categories, timestamped incident updates kept in a history, and a password unique to each page — one page per client is genuinely workable. Full white-label without the vendor's name comes with Business and Enterprise only, with partial branding on Free and Professional. We found no public information on subscriber notifications by email, SMS or RSS, or on multiple languages. 1 5

Report an error

The SaaS Platform Engineer

Custom domain with automatic SSL, logo, colours and embedding, monitor grouping, password-protected pages, announcements with timestamped updates and saved incident history are all documented, with the vendor branding removable only on Business and Enterprise. We found no public information on subscribers being notified of incidents by SMS, RSS or webhook, multiple languages, or how the status page itself stays hosted if the main service goes down. 1 5

Report an error

The Customer Support Lead

Status pages run on my own domain with automatic SSL, monitors grouped into categories my customers would recognise, announcements with timestamped updates saved into an incident history, uptime history per monitor, and a password per page for the largest accounts. The vendor's name leaves the page only on Business and Enterprise plans; on Free and Professional it stays in the title and footer. We found no public information on subscribers being emailed when an incident is posted — the captured pages show scheduled daily, weekly or monthly uptime report emails for status pages — and none on incident templates, single sign-on or IP-restricted private pages, or several languages. 1 5

Report an error

The E-Commerce Operations Manager

Public pages on my own domain or subdomain with automatic SSL, monitors grouped into ordered categories, announcements with timestamped updates and saved incident history, per-page password protection, embedding and custom branding are all documented, with full white-label branding on the Business and Enterprise plans. Daily, weekly or monthly uptime reports by email per status page, an uptime world map and per-monitor daily status go beyond the basics. We found no public information on incident subscribers notified by SMS, RSS or webhook, single sign-on for private pages, several languages, or how the page itself stays online when the main service is down. 1 5

Report an error

The Information Security Officer

Status pages come with every plan including Free, on a custom domain with automatic SSL, with logo, favicon, colours, light or dark mode, embedding in our own site, per-page password protection, monitor grouping and ordering, announcements with timestamped updates, a kept incident history, daily or weekly or monthly email uptime reports, and overall uptime plus daily status per monitor. Full removal of the vendor's name in title and footer arrives with the Business and Enterprise plans, with the name remaining on Free and Professional. We found no public information on subscriber notifications by SMS, RSS or webhook, several languages, incident templates, or how the page itself stays online when the main service is down. 1 5

Report an error

The Skeptic

Public status pages on every plan including the free one, on a custom domain with automatic SSL, with monitor grouping and ordering, password protection per page, announcements with timestamped updates and incident history, overall and daily per-monitor uptime with history navigation, embedding, and branding — though HetrixTools branding leaves the page only on Business and Enterprise. We found no public information on subscriber notifications by email, SMS or RSS, scheduled maintenance announcements, single sign-on or IP-restricted private pages, several languages, or how the status page hosting stays up when the monitoring service itself is down. 5 1

Report an error

API, monitoring as code & team administration

Show reasoning
How this is scored

How the tool fits a team and a deployment pipeline: a documented REST API to create and read monitors, status pages and incidents, a Terraform provider, CLI or monitoring-as-code workflow, checks run from CI/CD before a deploy, bulk import of monitors, integrations with ticketing and chat tools, team members with roles, single sign-on (SAML) and SCIM, audit logs, several teams or client accounts in one organisation, white-label or client reporting for agencies, and two-factor authentication.

0 — No API, no team accounts; one login per account and monitors are set up only by hand.

3 — A web dashboard with a few team members; the API, roles and multi-client set-up are basic or not described.

5 — A documented REST API covering monitors and status pages, webhooks, team members with roles, two-factor authentication, bulk import or a CSV upload of monitors, and several projects, teams or client groups in one account.

8 — A Terraform provider or monitoring-as-code CLI with checks kept in version control, checks triggered from CI/CD, single sign-on (SAML), SCIM provisioning, audit logs, sub-accounts for clients with their own logins, and white-label client reports.

10 — Administration that scales across many teams and clients: every setting reachable by API and code with parity stated, granular roles per resource, SSO enforced with SCIM, audit logs exportable to a SIEM, and agency or reseller accounts with separate billing.

Report an error

The Agency Developer

A v3 API to manage monitors and pull uptime, reports and downtimes, plus an MCP server for AI agents, webhook alerts, team members whose visibility I can restrict per member, an activity log, sub-accounts and white-label reports — the client-account shape an agency needs. We found no public information on bulk or CSV import of monitors, which matters when standing up two hundred checks at once, or on SAML single sign-on, SCIM or two-factor authentication. 1 4

Report an error

The SaaS Platform Engineer

A v3 API to manage monitors and pull uptime, reports and downtimes, webhooks, team sub-accounts with per-person control over what they see and change, an activity log, white-label client reports and MCP agent access on every plan give real automation. We found no public information on a Terraform provider or monitoring-as-code workflow, SAML single sign-on, SCIM, two-factor authentication or bulk import — so the checks-in-version-control story I need is not documented. 1 4

Report an error

The Customer Support Lead

A version 3 API lets my team manage monitors and pull uptime, reports and downtimes from our own code, webhooks post every alert as JSON, and sub-accounts let us choose what each team member can see and change, with an activity log and white-label reports shareable privately with clients. We found no public information on a Terraform provider or command-line workflow, checks run from CI/CD, single sign-on, SCIM, two-factor authentication, or bulk import of monitors. 1 4

Report an error

The E-Commerce Operations Manager

A version 3 API is documented for managing monitors and pulling uptime, reports and downtimes from our own code, alert webhooks post JSON to our URL, team members can be invited with control over what each can see and change, an activity log records what the team did, reports are white-label, and an MCP interface for AI agents is included on every plan. We found no public information on two-factor authentication, bulk monitor import, a Terraform provider or monitoring-as-code workflow, single sign-on or SCIM provisioning. 1 4

Report an error

The Information Security Officer

A v3 API manages monitors and pulls uptime, reports and downtimes from our own code, webhooks post alerts to our own URL, sub-accounts let us choose what each team member can see and change (not on Free), and an activity log records what happens in the account and what the team did — the nearest thing to an audit log here, though we found no public information on exporting it. We found no public information on single sign-on (SAML), SCIM provisioning, two-factor authentication, Terraform or monitoring-as-code, bulk import, or checks run from a deployment pipeline. Before any of our staff get a login I need single sign-on and an exportable audit trail, and the captured pages do not describe them. 1 4

Report an error

The Skeptic

A documented v3 API to manage monitors and pull uptime, reports and downtimes, webhooks, an MCP server on every plan, sub-accounts with per-member control over what each can see and change, a white-label report option, and an activity log of what your team did. We found no public information on two-factor authentication, bulk import, single sign-on or SCIM provisioning, a Terraform provider or monitoring-as-code CLI, or checks triggered from a CI/CD pipeline, and the API's coverage of status pages and incidents is not stated. 1 4 5

Report an error

Uptime reports, data & the vendor's own reliability

Show reasoning
How this is scored

What the record is worth and whether the monitor itself can be trusted: uptime and SLA reports per monitor and period, response time charts and percentiles, scheduled reports by email, client-facing reports, how long check results and incident history are kept, export of results by CSV or API, the vendor's own public status page and incident history, its SLA, the probe IP addresses and user agent published for allow-listing, and an open-source or self-hosted edition.

0 — No history of any kind; only the current state is shown.

3 — An uptime percentage and a response time chart per monitor; retention, export and the vendor's own status are basic or not described.

5 — Uptime and response time reports per monitor and period, SLA reports, scheduled email reports, the retention period of check results stated, CSV or API export, the probe IPs published, and the vendor's own public status page.

8 — Response time percentiles and breakdowns (DNS, connect, TLS, first byte), client-ready branded reports, retention of a year or more stated per plan, a raw export of check results, the vendor's incident history and post-mortems public, and an SLA with credits published.

10 — A record that holds up in an audit: SLA calculations with their method stated, incident records suitable for ISO 27001, NIS2 or DORA evidence, full history exportable in an open format, a self-hosted or open-source edition with feature parity stated, and the vendor's own availability over several years published.

Report an error

The Agency Developer

Outages, errors and response times with unlimited history on every plan, daily, weekly or monthly email reports per status page, and reports private by default that I can make public or white-label with my own domain and logo — that is my monthly client report requirement covered. The bot's user agent is published and every check comes from nodes I can allow-list in a firewall. We found no public information on response-time percentiles, CSV export, the vendor's own public status page or an SLA. 1 3 4 5

Report an error

The SaaS Platform Engineer

Unlimited history of outages, errors and response times on every plan, scheduled daily, weekly and monthly email reports, white-label client reports, API access to reports and downtimes, and a published bot user agent with checks from nodes you can block in a firewall. We found no public information on SLA reports, response time percentiles, the vendor's own public status page, or a published SLA with credits. 1 3 4 5

Report an error

The Customer Support Lead

Outages, errors and response times are kept with unlimited history on every plan, reports can be white-labelled on our own domain and shared publicly or kept private — the record I point to at a contract renewal — and daily, weekly or monthly email reports can be scheduled per status page. The monitoring bot's user agent is published and checks come from nodes a customer can firewall, which helps with allow-listing. We found no public information on response-time percentiles, SLA reports or an SLA with credits, or the vendor's own public status page and incident history. 1 3 4 5

Report an error

The E-Commerce Operations Manager

Outages, errors and response times come with unlimited history on every plan, and each failure captures ping and MTR samples, per-location errors and a screenshot with source code of what my visitors saw — good raw material for the report I hand the agency. Reports are private by default, can be made public, white-labelled on our own domain, and emailed daily, weekly or monthly, and the monitoring bot's user agent and node IP blocking are published. We found no public information on the vendor's own status page and incident history, an SLA, response-time percentiles or breakdowns, or a raw export of check results. 3 4 5

Report an error

The Information Security Officer

Outages, errors and response times are kept with unlimited history on every plan, reports are private by default and can be published under our own domain, logo and colours, and daily, weekly or monthly email reports are available for any status page — a decent evidentiary trail when paired with per-location error logs, ping and MTR samples and a snapshot of what visitors saw during the outage. The bot's user agent and node IPs are published for allow-listing, and reports are reachable through the API. We found no public information on response time percentiles or breakdowns, SLA reports, the vendor's own status page and incident history, an SLA with credits, or a self-hosted edition. 1 3 4 5

Report an error

The Skeptic

Outages, errors and response times with "unlimited history on every plan", scheduled daily, weekly or monthly email reports for status pages, white-label reports on your own domain, and evidence retained per outage — ping and MTR samples plus a screenshot with the page's source code. The bot's user agent is published and its checks can be blocked by IP, but we found no public information on response time percentiles or breakdowns, an SLA with credits, CSV export, or the vendor's own status page and public incident history — where the monitor publishes its own outages is not shown. 1 3 4

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Who the contracting entity and the parent company are, where account data, alert contacts (names and phone numbers of the people on call), status page subscribers and check results are stored and processed, and who the subprocessors are (hosting, SMS and phone gateways, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. Probe locations outside Europe 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 or open-source 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 call gateways, email, 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, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The Agency Developer

The GDPR page states all data is stored on secure servers within HetrixTools' own infrastructure without naming a country, and documents breach notification to affected users, staged erasure and encrypted replication, while a subprocessors list is referenced but not shown in the captured pages. We found no public information on the contracting entity's jurisdiction, a hosting location, the subprocessors themselves, or a data processing agreement — too many unknowns in the chain for me to vouch for it to clients. 2

Report an error

The SaaS Platform Engineer

The GDPR page documents storage on the vendor's own infrastructure, encrypted replication, 30-day backups, staged erasure on written request and breach notification to affected users, and it references a subprocessors list. We found no public information on the contracting entity's jurisdiction, where data is hosted, which subprocessors are used, a data processing agreement, or any certification — so nothing places the chain in Europe or out of it. 2

Report an error

The Customer Support Lead

The vendor's GDPR page commits to notifying affected users of a breach and describes encrypted database replication, backups kept thirty days, and storage on the vendor's own infrastructure, without naming a country. The page refers to a subprocessors list without reproducing it, and states that AI assistant providers are the customer's own processors rather than the vendor's. We found no public information on the contracting entity's jurisdiction, a published data processing agreement, or where account data, alert contacts and check results are processed. 2

Report an error

The E-Commerce Operations Manager

A GDPR page documents encrypted database replication and backups with 30-day backup retention, staged data erasure, one-way password hashing and breach notification to affected users, and states data is stored on secure servers within the vendor's own infrastructure. We found no public information on where that infrastructure is located, the contracting entity's jurisdiction, the hosting, SMS, email or payment subprocessors (a subprocessors list is referenced for AI assistants but not shown), or a data processing agreement — for my German, Austrian and Swiss customers that chain is unproven. 2

Report an error

The Information Security Officer

The GDPR page states all data sits on secure servers within the vendor's own infrastructure without naming a country, and refers to a subprocessors list without naming a single subprocessor or location; we found no public information on the contracting entity's jurisdiction, a published data processing agreement, or ISO 27001 or SOC 2 certification. Genuine GDPR work is documented — three-stage erasure on written request, breach notification to affected users, one-way hashed passwords, pseudonymous user identifiers, encrypted database replication and 30-day backup retention. Until the subprocessor names, locations and a data processing agreement are visible, the on-call staff's mobile numbers and status page subscribers cannot pass through this chain. 2

Report an error

The Skeptic

The vendor's GDPR page documents concrete practices — data "stored on secure servers within HetrixTools' own infrastructure", encrypted database replication, 30-day backup retention, staged erasure within 30 days of a written request, hashed passwords, pseudonymization, and breach notification to affected users — but never states where that infrastructure sits, the contracting entity's jurisdiction, or the subprocessors involved. A subprocessors list is implied (the customer's chosen AI provider "does not appear on our subprocessors list") yet its contents are not shown, and we found no public information on a published data processing agreement or certifications such as ISO 27001 or SOC 2. 2

Report an error

Pricing transparency

Show reasoning
How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per tier by number of monitors, check interval and status pages, team seats and on-call responders, what SMS and phone alerts cost, which features (multi-step or browser checks, SSO, longer retention, private locations, white-label) cost extra, the free tier and its limits, overage handling, minimum term and VAT.

0 — No public prices at all; every customer is a sales call.

3 — A starting price or a free tier exists, but how cost scales with monitors, intervals, seats or alerts is unclear.

5 — Tiers are public with their monitor count, interval and main inclusions, but at least one commonly needed piece (SMS or call alerts, extra seats, extra status pages, SSO, longer retention) is unpriced or "on request".

8 — Every tier priced publicly with its scaling rule (monitors, interval, seats, responders, status pages), SMS and call costs stated, add-ons priced, overage handling stated, minimum term and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given number of monitors, interval, team size and alert volume, with every add-on, overage and support fee and the cancellation and data-return terms published.

Report an error

The Agency Developer

The free tier is documented in detail — 15 uptime monitors and 32 blacklist monitors free forever with every feature except sub-accounts — and the plan ladder names Free, Professional, Business and Enterprise, but the captured pages show no price for any paid plan. SMS and phone alerts are charged in credits without a stated credit price, so I cannot compute the annual cost of two hundred monitors with alerting. We found no public information on VAT treatment, minimum terms or overage handling. 1 4 5

Report an error

The SaaS Platform Engineer

The free tier is precisely public: 15 uptime monitors and 32 blacklist monitors with every feature except sub-accounts, and plans named Free, Professional, Business and Enterprise appear on the pages. We found no public information on paid-tier prices, how monitor counts, locations or seats scale with cost, what the SMS and phone-call credits cost, or minimum term and VAT treatment. 1 4 5

Report an error

The Customer Support Lead

The free tier is documented in detail — fifteen uptime monitors and thirty-two blacklist monitors with every channel and every feature except sub-accounts — so a small team's cost is computable at zero. Beyond that the paid plans appear only by name, and we found no public information on their prices, how monitor count, locations or seats scale in cost, or what SMS and call credits cost. 1 4 5

Report an error

The E-Commerce Operations Manager

The free tier is documented precisely: 15 uptime monitors and 32 blacklist monitors free forever with every feature except sub-accounts, and the plan names Professional, Business and Enterprise appear alongside it with their location counts and white-label levels described. We found no public information on the prices of the paid plans, what an SMS or voice-call credit costs, seat or extra status page pricing, minimum term or VAT treatment, so I cannot budget a full season of alerting from these pages. 1 4 5

Report an error

The Information Security Officer

The free tier is precisely stated — "15 monitors free forever" for uptime plus "32 monitors free forever" for blacklist monitoring — with every feature on every plan except sub-accounts, and status pages included even on Free. Paid plan names (Professional, Business, Enterprise) appear only in connection with white-label levels and we found no public prices for them, while SMS and voice alerts are charged "using credits" with no credit price stated. A buyer cannot compute a real annual cost from the captured pages alone. 1 4 5

Report an error

The Skeptic

The free tier is concrete — "15 monitors free forever" for uptime, "32 monitors free forever" for blacklists, status pages included, and every feature on every plan except sub-accounts — an unusually flat model. But the captured pages give no prices for the named Professional, Business and Enterprise plans, and SMS and phone alerts run "using credits" with no credit price shown, so how cost scales with locations per plan, sub-accounts or alert volume cannot be computed from what was captured. 1 4 5

Report an error

European sovereignty — proven facts

0 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined — uncited Report an error
Hosting options Not determined — 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 HetrixTools

Is HetrixTools European?

Not determined: the vendor’s pages as captured do not say where HetrixTools is based.

Where does HetrixTools store data?

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

Does HetrixTools have a free plan?

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

What are the best alternatives to HetrixTools?

As of 19 Nov 2026, the panel rates Hyperping (3.5/5), Uptimia (3.5/5) and Checkly (3.5/5) highest among the other 23 Uptime Monitoring & Status Pages 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 Hyperping (EU-Made, France). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: HetrixTools alternatives.

Where this could be wrong

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.

Sources (5)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page hetrixtools.com Checked 10 Nov 2026 Details →
  2. 2 Security / trust page — found from the homepage hetrixtools.com Checked 10 Nov 2026 Details →
  3. 3 Checks, locations & failure confirmation — found from sitemap hetrixtools.com Checked 10 Nov 2026 Details →
  4. 4 Checks, locations & failure confirmation — found from sitemap hetrixtools.com Checked 10 Nov 2026 Details →
  5. 5 Status pages & incident communication — found from sitemap hetrixtools.com Checked 10 Nov 2026 Details →