hostnag vs openstatus
openstatus is an open-source status page and uptime monitor built for infra as code: HTTP, TCP, DNS, ICMP and gRPC monitors declared in YAML or Terraform, run from 28 locations, with an MCP server and self-hosting under AGPL-3.0. Heartbeats for jobs and links, plus certificates, domains and mail setup, all set up from forms instead of configuration files.
14 days of Pro to start, then free for 20 hosts. No card, nothing to install.
Side by side
openstatus read from its public documentation on 2026-09-17. Tell us if it changed.| What breaks | openstatus | hostnag |
|---|---|---|
| A host goes downwebsite, API, VPN, mail, gateway | Yes | Yes |
| openstatus: HTTP, TCP, DNS, ICMP and gRPC monitors with status, header and body assertions, from up to 28 locations. | ||
| A certificate expiresdays-before thresholds, daily inside the last window | Unknown | Yes |
| openstatus: The HTTP monitor reference documents assertions only; nothing says whether certificate expiry raises an alert. | ||
| A domain lapsesregistration expiry from RDAP | Unknown | Yes |
| openstatus: No domain registration check is documented. | ||
| A certificate is swappedfingerprint changed, wrong host, chain not trusted | Unknown | Yes |
| openstatus: Nothing documents a certificate check beyond the TLS handshake of an HTTPS monitor. | ||
| A DNS record driftsexpected answer missing or changed | Yes | Yes |
| openstatus: DNS monitors assert the records a lookup returns (equal, not equal, contains, not contains) for A, AAAA, CNAME, MX, NS and TXT. | ||
| An ISP link dropsthe public address from several locations, by ping or a TCP port, confirmed by a ping from an internal device | Unknown | Yes |
| openstatus: ICMP monitors watch a public address externally; nothing documents an internal confirmation for an office or ISP link.hostnag: external and internal | ||
| Mail stops being deliveredMX, SPF, DKIM, DMARC and blocklists, at the expiry cadence of your plan | Unknown | Yes |
| openstatus: A TCP monitor reaches a mail port; nothing documents SPF, DKIM, DMARC or blocklist checks. | ||
| A scheduled job stops runningcron, backups, workers: a heartbeat that goes quiet | Unknown | Yes |
| openstatus: No heartbeat or cron monitor is among the documented monitor types. | ||
| Your nameservers or registrar changenameservers, registrar, DNSSEC, certificate issuer, DNS answers, redirect targets | Partly | Yes |
| openstatus: A DNS monitor can assert the NS answer; nothing documents watching the registrar, DNSSEC or redirect targets. | ||
| A vendor you depend on has an incidenttheir status page read for an outage or degraded state, the incident named | Unknown | Yes |
| openstatus: Nothing documents reading a vendor's status page.hostnag: read from their own status page | ||
UNKNOWN means their documentation did not say either way on the day we read it. PARTLY is covered with a limit noted in the cell.
What openstatus has that we don't
- Open source under AGPL-3.0, self-hostable, with private locations in a single small container.
- Monitoring as code: YAML or Terraform applied from the CLI or CI, a typed API and Node SDK, and an MCP server.
- Up to 28 locations per monitor, gRPC monitors, and status pages with password protection.
Switching
- 01Your monitors are already a list: the YAML or Terraform they are declared in, or the CLI's --json output.
- 02Put them in a CSV with at least the columns type and target (name, interval, port, keyword, expected_status and record_type are optional; the import dialog links a template) and upload it in the import dialog.
- 03HTTP monitors become http (a status assertion maps to expected_status, a body assertion to keyword), TCP monitors tcp, DNS monitors dns with their record_type.
- 04Ping (ICMP) monitors carry over as Ping monitors, run from hostnag's own probes.
- 05gRPC monitors have no counterpart in hostnag; watch the port instead.
- 06Check intervals snap up to the nearest hostnag preset (1, 5, 15, 60, 360 or 1440 minutes).
- 07Monitors are created up to your plan's limit; the rest stay listed in the preview so nothing is lost silently.
Pricing
A free Hobby plan covers 1 monitor at 10-minute checks and one status page; Starter is $30 a month for 20 monitors at 1 minute from 6 locations, Pro $100 for 50 at 30 seconds from 28, Scale $500, and Enterprise is custom.Free
$0/ mo$0/ yrFor your own handful of hosts.
- Monitors
- 20
- Beacons
- 2
- Groups
- 3
- Status pages
- 1
- Seats
- 3
- Every
- 5min
- Locations
- 1
- History
- 30days
- Channels
- Email, Slack, Discord, Microsoft Teams, Telegram, Webhook
- More
- No packs
Pro
$19/ mo$190/ yrFor a team's sites, APIs and gateways.
- Monitors
- 100
- Beacons
- 10
- Groups
- 25
- Status pages
- 10
- Seats
- 10
- Every
- 1min
- Locations
- 3
- History
- 90days
- Channels
- Email, Slack, Discord, Microsoft Teams, Telegram, Webhook, PagerDuty, Opsgenie
- More
- Packs of 100 monitors at $15 a month, up to 4; packs of 10 beacons at $10 a month, up to 9
Business
$79/ mo$790/ yrFor many groups: clients, products or offices.
- Monitors
- 500
- Beacons
- 100
- Groups
- ∞
- Status pages
- ∞
- Seats
- ∞
- Every
- 1min
- Locations
- 5
- History
- 365days
- Channels
- Email, Slack, Discord, Microsoft Teams, Telegram, Webhook, PagerDuty, Opsgenie, SMS
- More
- Packs of 100 monitors at $15 a month, as many as you need; packs of 10 beacons at $10 a month, as many as you need
Sources
Read on 2026-09-17.Bring your openstatus monitors. Hear about the next outage first.
Start free