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 Hund Software · hund.io

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

Link to this page

Hund: AI-assisted analysis on whats-best.ai Hund: 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.

Hund at a glance

Vendor
Hund Software
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
Starting price
“STARTING AT $29/month Your First Status Page, Fully Featured” (vendor’s words) source, captured 10 Nov 2026
Panel verdict
The AI panel rates Hund 2/5, the mean of 6 judges. Hund, from Hund, LLC. how scores are made
As of
Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources

Hund alternatives, European ones first →

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

The panel's verdict

Hund, from Hund, LLC. of Wyoming, is a hosted status page service with a native monitoring engine, starting at $29/month with 20 components, unlimited team users, and all integrations. The bench scores it strongest on status pages and automation and teams (6): unlimited public and private pages on a custom domain with free HTTPS, granular subscriptions by component and event type, a version 1 API with a published specification, webhooks, a Terraform provider for status page resources, and 22 integrations. Weakest are sovereignty (1) and alerting and on-call (2). Sovereignty rests on a Wyoming entity, hosting described only as multiple geographic regions, SOC 2 and ISO 27001 stated as alignment rather than certification, and no public information found on residency, subprocessors, or a data processing agreement. On alerting, we found no public information on channels, escalations, or on-call schedules beyond webhooks. Checks sit at 2-3; reports and reliability at 3-4 on a published SLA with 99.95% and 99.9% commitments. Scores fell within a point on every criterion; no genuine split emerged.

Report an error

Speaks for it

  • Unlimited public and private status pages on a custom domain with free HTTPS and full branding control
  • Version 1 API with a published RAML specification, webhooks, and a Terraform provider for provisioning status page resources
  • Published SLA with 99.95% (Enterprise Tier) and 99.9% (Usage-Based Tier) commitments, 10% and 25% service credits, and a 30-day claim window
  • Starting price of $29/month is public, including 20 components, unlimited team users, and all integrations
  • 30-day free trial with no credit card required and all features included

Report an error

Held against it

  • We found no public information on alert channels, escalation policies, on-call schedules, or acknowledging and resolving alerts
  • We found no public information on check types, check intervals, or named probe locations
  • Hund's internal monitoring is the sole source for determining downtime, and service credits cap at 100% of the monthly fee
  • We found no public prices for the named add-ons (Extra Component Packs, Private Pages and Access Controls, Managed Email Subscribers, Enterprise SSO)
  • We found no public information on data residency, subprocessors, or a data processing agreement, and SOC 2 and ISO 27001 are stated as alignment rather than certification

Report an error

Best for

  • You need branded status pages for multiple audiences or key clients on your own domain, with granular subscriptions by component and event type
  • Your team manages the incident lifecycle programmatically through an API, webhooks, and Terraform
  • You want to evaluate before buying — the 30-day free trial requires no credit card and includes all features

Report an error

Avoid if

  • You need your own third-party monitoring to count toward SLA claims — the SLA names Hund's internal monitoring as the sole source for determining downtime and does not accept third-party monitoring
  • You depend on Managed Subscriber Services staying available — they depend on third-party providers and are excluded from the SLA
  • Your procurement cannot contract with a US entity — the contracting party is Hund, LLC. of Wyoming
  • Your remedy expectations run beyond service credits capped at 100% of the monthly fee for the affected service

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

Native checks run from global regions and the monitoring service is covered by the SLA, so this is a real monitor rather than a page fed by other tools. But I found no public information on check types — HTTP status or keyword, SSL or domain expiry — on the check interval, named probe locations, or how a failure is confirmed before anyone is told, which is what I would need before pointing it at sixty client sites. 1 3

Report an error

The SaaS Platform Engineer

The pages show native checks running from global regions that feed the components on the page, and the service agreement names a native monitoring service alongside the hosted status page. We found no public information on check types, check intervals, probe locations by city, or confirmation of a failure from a second location before anyone is alerted, which is what I would need before trusting it to wake my rotation. 1 3

Report an error

The Customer Support Lead

The pages confirm a native monitoring engine with checks run from global regions feeding the status page, but check types such as keyword, SSL or port checks, the check interval, the named probe locations, and how a failure is confirmed before anyone is told are all undescribed. I cannot judge from this evidence how quickly a customer-visible outage would be caught. 1 3

Report an error

The E-Commerce Operations Manager

The pages describe a native monitoring engine running checks from global regions that feed the components on the page, but we found no public information on check types such as keyword or SSL checks, the check interval, named probe locations, or how a failure is confirmed before anyone is told. For me that means I cannot see whether the checkout and payment page can actually be watched, only that some kind of check exists. 1 3

Report an error

The Information Security Officer

The vendor states it runs native checks from global regions and its service level agreement names a native monitoring service as covered, but the captured pages do not describe check types, check intervals, named probe locations or any second-location confirmation before an alert is raised. 1 3

Report an error

The Skeptic

Native checks "from global regions" exist and the SLA counts the native monitoring service among covered services — but not a single check type, interval or named region is described, and nothing says a failure is confirmed from a second location before anyone is told. Without knowing how a down is confirmed, I treat this as checks that exist and little more. 1 3

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

A developer-first API with webhooks and incident-lifecycle automation is the extent of what I found on notifications; there is no public information on email, SMS, phone call or chat alert channels, escalation policies, on-call schedules, or what a message costs. I once learned about an expired certificate from a client's angry phone call, and nothing captured shows who gets told about a failure and how. 1 2

Report an error

The SaaS Platform Engineer

The homepage describes webhooks for custom integrations and lists a count of twenty-two integrations, but we found no public information on alert channels such as email, SMS or phone calls, escalation policies when an alert is not acknowledged, on-call schedules, or acknowledgement from the app or chat. 1 2

Report an error

The Customer Support Lead

What is documented is a developer-first API for automating the incident lifecycle, webhooks for custom integrations, and twenty-two integration repositories. We found no public information on alert channels such as email, SMS or phone calls, escalation policies, or on-call schedules, so if our service failed at 2am I could not say from these pages who or what would be woken. 1 2

Report an error

The E-Commerce Operations Manager

A developer-first API with webhooks and a set of integrations could carry failure events onward, but we found no public information on alert channels such as SMS or phone calls, escalation policies, on-call schedules, or acknowledging and resolving an alert from a mobile app. The night-shift picture — who gets woken and how — is blank on the captured pages. 1 2

Report an error

The Information Security Officer

Webhooks, granular per-component subscriber notifications and a managed email subscriber add-on are documented, alongside a stated incident lifecycle API. We found no public information on responder channels such as SMS or phone calls, escalation policies, on-call schedules or acknowledgment and resolution from the app. 1 2

Report an error

The Skeptic

Webhooks, 22 integration repositories and "all integrations" bundled into the plan are documented, but the captured pages never describe how a person is actually alerted — no channels for the team, no escalation, no on-call schedules, no acknowledge-and-resolve. Whether SMS or phone alerts exist at all is unknown from these pages. 1 2

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

This is the heart of the product: unlimited public and private pages for different audiences including custom pages for key clients, a custom domain with free HTTPS, full branding control, components tied to the monitoring engine, granular per-component subscriptions, an embeddable status widget, and private pages with access controls plus Enterprise SSO as an add-on. I found no public information on subscriber channels beyond email, several languages, incident templates, or how the page itself stays online if the main service fails. 1 2

Report an error

The SaaS Platform Engineer

This is the core of the product: unlimited public and private pages, a custom domain with free HTTPS, full branding control, twenty components to monitor and display, granular subscriptions per component and event type, and managed or unmanaged email subscribers. There is an embeddable live status widget, pages aimed at different audiences and key clients, and the incident lifecycle is automatable through the API. We found no public information on subscriber channels beyond email, multiple languages, or how the page hosting is kept separate from the main service. 1 2

Report an error

The Customer Support Lead

This is the vendor's heart and covers most of what my team needs: pages on a custom domain with free HTTPS, twenty components to monitor and display, unlimited public and private pages for different audiences including custom pages for key clients, granular email subscriptions by component and event type, full branding control, and an embeddable status widget. We found no public information on incident templates, per-component uptime history I could point to in a contract renewal, or SMS and RSS subscribers, so it sits in the middle of the scale. 1 2

Report an error

The E-Commerce Operations Manager

This is clearly the core of the product: unlimited public and private pages for different audiences on a custom domain with free HTTPS, components linked to the native checks, subscriptions to specific components and event types, full branding control, and an open-source embeddable status widget. We found no public information on SMS or RSS subscribers, several languages, or how the status page hosting is kept separate from the main service when it fails. 1 2

Report an error

The Information Security Officer

Unlimited public and private pages on a custom domain with free HTTPS, components with granular subscription controls, full branding control, an embeddable open-licensed status widget and custom pages for key clients are all documented. Higher-end elements such as component groups, non-email subscriber channels and multiple languages are not described in the captured pages. 1 2 3

Report an error

The Skeptic

This is the core of the product: unlimited public and private pages, custom domain with free HTTPS, subscriptions to specific components and event types, an embeddable widget under an MIT licence, and SSO-gated or per-client pages as add-ons. For my money the gaps are component groups, SMS or RSS subscribers, multiple languages, and any statement of how the page hosting survives an outage of the main service. 1 2

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 published API specification with webhooks, a Terraform provider for provisioning status page resources, unlimited team users, and Enterprise SSO as an add-on make a decent scripted base. I found no public information on roles, two-factor authentication, bulk import for standing up two hundred monitors at once, client sub-accounts with their own logins, SCIM, or audit logs. 1 2

Report an error

The SaaS Platform Engineer

A version 1 API with a published specification, webhooks, a Terraform provider for provisioning hosted status page resources, unlimited team users, and an Enterprise SSO add-on give it real programmatic footing. The Terraform provider covers status page resources rather than the checks themselves, and we found no public information on team roles, two-factor authentication, SCIM, audit logs, or checks triggered from CI/CD. 1 2

Report an error

The Customer Support Lead

There is a published v1 API specification in RAML, a Terraform provider for provisioning hosted status page resources, webhooks, unlimited team users, and Enterprise SSO as an add-on — a genuinely good story for our platform team. We found no public information on member roles, two-factor authentication, SCIM provisioning, audit logs or white-label client reports, which keeps it at mid-scale. 1 2

Report an error

The E-Commerce Operations Manager

A documented version 1 REST API with a public RAML specification, a Terraform provider for provisioning status page resources, webhooks, an Enterprise SSO add-on and unlimited team users give an agency a lot to automate with. We found no public information on team roles, two-factor authentication, SCIM provisioning, audit logs or separate client logins with their own accounts. 1 2

Report an error

The Information Security Officer

A published API specification, a Terraform provider for the hosted status page resources, webhooks, twenty-two integrations and an Enterprise single sign-on add-on are documented, with unlimited team users. We found no public information on audit logs, SCIM provisioning, two-factor authentication or role-based access, which are our preconditions before anyone gets a login. 1 2

Report an error

The Skeptic

A developer-first API with a published RAML specification, webhooks, a Terraform provider, unlimited team users and an Enterprise SSO add-on is real, documented automation. But the Terraform provider is described for status page resources only, and we found no public information on checks kept in version control, CI/CD triggers, SCIM provisioning, audit logs or per-resource roles. 1 2

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

A published SLA with tiered commitments of 99.95% and 99.9% and 10% or 25% service credits, plus multi-region hosting, cold backups, automated disaster recovery and SOC 2 / ISO 27001 alignment statements, give some substance — though the SLA makes Hund's internal systems the sole source for downtime calculations. I found no public information on uptime or response-time reports per monitor, retention of check results, CSV or API export, probe IPs for allow-listing, or the vendor's own public status page and incident history. 1 3

Report an error

The SaaS Platform Engineer

The service agreement publishes per-tier commitments of 99.9 and 99.95 percent with a 10 and 25 percent credit schedule, a thirty-day claim window, and the homepage describes cold and remote backups with automated disaster recovery. I would weigh that Hund's internal monitoring systems are the sole source for determining downtime and credits are capped at the monthly fee; we found no public information on per-monitor uptime or response-time reports, retention, export, or the vendor's own public status page. 1 3

Report an error

The Customer Support Lead

The published service level agreement names an Enterprise tier at 99.95% and a Usage-Based tier at 99.9% with service credits of 10% and 25%, a claim window and a cap of 100% of the monthly fee — a document I could put in front of a renewal — and the vendor describes multi-region hosting, automated disaster recovery and SOC 2 and ISO 27001 alignment. We found no public information on uptime or response time reports, retention periods, export of results or the vendor's own status page, and the agreement states Hund's internal monitoring is the sole source for downtime calculations. 1 3

Report an error

The E-Commerce Operations Manager

The SLA is public with per-tier commitments (99.95% for the Enterprise tier, 99.9% for the Usage-Based tier) and service credits up to 100% of the monthly fee, though downtime is measured solely by Hund's own internal monitoring and my own monitoring would not count toward a claim. We found no public information on per-monitor uptime or response time reports, retention, export of results, probe IP addresses, or the vendor's own public status page — so no report I could hand the agency to show what an outage cost. 1 3

Report an error

The Information Security Officer

The published service level agreement gives tiered uptime commitments (99.95 percent Enterprise, 99.9 percent Usage-Based) with credit percentages, a 30-day claim window and a remedy cap, and states the vendor's internal monitoring and logging are the sole source for determining downtime, with third-party monitoring not accepted. We found no public information on retention periods for check results, export of results, probe addresses for allow-listing or the vendor's own public status page and incident history. 1 3

Report an error

The Skeptic

The SLA is genuinely published — 99.95% and 99.9% commitments with 10% and 25% service credits, claimed by email within 30 days — but Hund's internal monitoring is named the sole source for determining downtime, managed subscriber services are excluded from the SLA, and credits cap at the monthly fee. We found no public information on retention of check results, export, probe IP addresses, or Hund's own public status page and incident history. 1 3

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 contracting entity is Hund, LLC. in Wyoming, USA, and hosting is described only as spanning multiple regions and availability zones with no country stated; I found no public information on data residency, subprocessors, or a data processing agreement. A US entity with an unlocated hosting chain and unnamed third-party providers is essentially the lowest band, with the agreement question simply undocumented rather than resolved. 1 2 3

Report an error

The SaaS Platform Engineer

The contracting entity is Hund, LLC of Wyoming, and we found no public information on hosting location, data residency, a data processing agreement, or the subprocessors behind SMS, email and payment. The pages state operation in alignment with SOC 2 and ISO 27001 and offer a trust center, but nothing describes where account data and check results are stored or processed. 1 2

Report an error

The Customer Support Lead

The contracting entity is Hund, LLC. in Wyoming, and the pages say infrastructure spans multiple geographic regions and availability zones without naming where account data or subscriber emails are stored; the third-party providers behind managed subscriber services are unnamed. For a company whose customers are tax advisers and payroll offices, we found no public information on a data processing agreement or EU safeguards, and the SOC 2 and ISO 27001 statements are of alignment rather than certification. 1 2 3

Report an error

The E-Commerce Operations Manager

The contracting entity is Hund, LLC. of Wyoming, the infrastructure is described as multi-region without naming where account data and subscriber details are stored, and the SLA refers to unnamed third-party providers behind Managed Subscriber Services. SOC 2 and ISO 27001 are stated as alignment rather than certification, and we found no public information on a data processing agreement or a subprocessor list — a hard sell for my German, Austrian and Swiss customer data. 1 2 3

Report an error

The Information Security Officer

The contracting entity is Hund, LLC. of Wyoming and hosting is described only as multiple unnamed geographic regions and availability zones; we found no public information on data residency, a subprocessor list or a data processing agreement, which is where I look first because subscriber lists and team accounts are personal data. The vendor states alignment with SOC 2 and ISO 27001 rather than certification, and no self-hosted edition is documented. 1 2 3

Report an error

The Skeptic

The contracting entity is Hund, LLC of Wyoming, hosting is described only as "multiple geographic regions" with no location named, and the subscriber services that depend on third-party providers never name those providers. The pages state "alignment" with SOC 2 and ISO 27001 — alignment, not a certificate — and we found no public information on a data processing agreement or on where check results and alert contacts are stored and processed. 1 2 3

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

A starting price of $29/month for a first, fully featured status page with 20 components, unlimited team users and unlimited unmanaged subscriptions is public, along with named add-ons: Extra Component Packs, Private Pages and Access Controls, Managed Email Subscribers and Enterprise SSO. Add-on prices, the cost per additional component or monitor, VAT treatment, minimum term and overage handling are not public, so I cannot compute what two hundred monitored components would cost my agency per year. 1 3

Report an error

The SaaS Platform Engineer

The starting price of $29/month is public with its inclusions — twenty components, unlimited team users, unlimited unmanaged subscriptions, a custom domain with free HTTPS — and add-ons are named, including extra component packs, private pages and access controls, managed email subscribers, and Enterprise SSO. The prices of those add-ons, how the usage-based and enterprise tiers scale, and the cost of SMS or call alerts are not stated on the captured pages. 1 3

Report an error

The Customer Support Lead

A starting price of $29/month is published with real inclusions — twenty components, unlimited team users and issues, unlimited unmanaged subscriptions, custom domain with free HTTPS — plus a 30-day trial with no credit card, and the add-on list names Extra Component Packs, Private Pages and Access Controls, Managed Email Subscribers and Enterprise SSO. The add-ons themselves carry no public prices and the usage-based scaling is described only as paying for the resources you actually use, so I could not compute our annual cost from the captured pages alone. 1 3

Report an error

The E-Commerce Operations Manager

The entry price is public at $29/month with clear inclusions (20 components, unlimited team users, custom domain with free HTTPS, all integrations) and the add-ons are named — Extra Component Packs, Private Pages and Access Controls, Managed Email Subscribers, Enterprise SSO — but none of them carries a price. We found no public information on VAT treatment, minimum term or how the usage-based costs scale, so I cannot compute a real annual cost from the captured pages alone. 1 3

Report an error

The Information Security Officer

A starting price of $29/month with 20 components, unlimited team users and all integrations is public, and the Usage-Based and Enterprise tier names appear in the service level agreement. The add-ons Enterprise SSO, Private Pages and Access Controls, Extra Component Packs and Managed Email Subscribers are named but not priced in the captured pages, and no per-monitor or per-interval unit price is shown. 1 3

Report an error

The Skeptic

A starting price of $29/month with 20 components, unlimited team users and all integrations is public, and the add-ons are at least named — Extra Component Packs, Private Pages and Access Controls, Managed Email Subscribers, Enterprise SSO — but not one of them carries a price. "Pay only for the resources you actually use" has no rate card behind it, and we found no public information on overage handling, minimum term or VAT treatment. 1 3

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 Hund

Is Hund European?

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

Where does Hund store data?

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

Does Hund have a free plan?

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

What are the best alternatives to Hund?

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: Hund alternatives.

Where this could be wrong

Sources (3)

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

  1. 1 Vendor page hund.io Checked 10 Nov 2026 Details →
  2. 2 Code repository (open-source licence) — found from the homepage github.com Checked 10 Nov 2026 Details →
  3. 3 Uptime reports, data & the vendor's own reliability — found from sitemap hund.io Checked 10 Nov 2026 Details →