All posts

What a hosted status page actually costs in 2026

A hosted public status page is simple to view, but it still needs reliable infrastructure, a safe incident-publishing path, and historical data that does not disappear with the service it describes. Those costs are real, even when a vendor bundles a page into a broader monitoring plan.

There is no universal "right" price. Some products include status pages in a free tier with narrow limits; others reserve them for paid plans alongside faster checks, team access, or retention. The useful question is whether the service stays available during an incident and includes the controls your team actually needs.

What "hosted" actually means

A hosted status page is not just the page that customers see. It is:

  • A public URL, typically status.yourbrand.com.
  • A renderer that subscribes to incident events and re-renders.
  • A historical view for uptime and past incidents.
  • A publishing workflow for timely incident updates.
  • Enough separation from your production stack to remain reachable during an outage.

All of those have a real implementation cost. The thing that changed is that the implementation is shared across thousands of customers, so the marginal cost per customer is small.

What it means for self-hosted

Self-hosting a status page — using Uptime Kuma, Cachet, Statping, or your own — still works in 2026 and is still the right choice in some scenarios. The comparison we wrote on /vs/uptime-kuma goes into the trade-offs in detail, but the short version is:

  • Pick self-hosted if "I run the database" is in your team's comfort zone and the rest of your service is already self-hosted. Consistency wins.
  • Pick hosted if you'd rather spend the time on your own product. You are paying for someone else's uptime, which is what you're already buying for the rest of your stack.

Managed and self-hosted options are different trade-offs. Both can be sensible when their operational requirements match the team using them.

What this changes for vendors

For uptime-monitoring vendors, the important differences are:

  • How fast do checks run? (5 minutes vs 10 seconds vs 30 seconds.)
  • How many monitors per account?
  • Which alert deliveries are built in or configurable for each organization?
  • How does the price of the Pro tier compare?

ZnowPulse offers 5-minute checks on Free and checks as often as every 10 seconds on Pro. Free includes unlimited monitors, one Nexus Point, email and webhooks, and delivery integrations that an organization can configure. Hosted public status pages, team features, exports, backups, and unlimited Nexus Points are Pro features. Pro is $5.99 per month or $59.99 per year; the Free plan has no card requirement or expiry.