InfraNestInfraNest

Monitoring & Status

Branded status pages, powered by your monitoring

Publish a status page on your own domain that shows exactly what is up, what is degraded and what is planned — straight from the checks you already run. Cut the “is it just me?” tickets, keep customers in the loop, and never update a page by hand again.

Free plan · No credit card · Your first page live in minutes

Acme Cloud · status1 component degraded
APIOperational
WebsiteOperational
DashboardDegraded performance
DatabaseOperational
CDNOperational

Live from the monitors you already run.

Your brand, your domain, your checks

Point each component at a monitoring check and the page shows real status, uptime and incident history with nothing to keep current. Host it on status.yourdomain.com with a guided CNAME and automatic HTTPS, styled with your logo and colors.

  • Components map straight to your monitoring checks
  • Custom domain with automatic HTTPS, no certificate wrangling
  • Your logo, colors and copy — it looks like part of your product
ComponentsLive from monitoring
ComponentLinked check90-day uptime
APIapi.acme.com · HTTPS99.98%
Websiteacme.com · HTTPS100%
Dashboardapp.acme.com · HTTPS99.71%
Databasedb-primary · TCP99.99%

Each component maps to a check — no status to update by hand.

Customers keep themselves informed

When something breaks, post an update once and every subscriber hears about it by email, SMS or webhook — so your inbox stays quiet. Incident templates walk you from Investigating to Resolved, and the whole history stays on the page for anyone who asks later.

  • Subscribers notified automatically on every incident post
  • Templated updates from Investigating through to Resolved
  • A permanent, public record of how you handled it
Incident · Elevated API errors
Investigating — looking into elevated API errors14:02
Identified — a database failover is the cause14:19
Monitoring — a fix is deployed, watching recovery14:37
Resolved — API fully operational15:04

Every post emails and texts your subscribers automatically.

Private pages and full white-label

Not every status page is for the public. Password-protect a page so only your team or a single client can see it, and run as many pages as you need from one set of checks. On paid plans the InfraNest branding disappears entirely, so the page reads as purely yours.

  • Password-protect a page for internal or client-only eyes
  • Run separate public and internal pages from the same checks
  • White-label removes every trace of InfraNest
Internal status · ops.acme.comPrivate · white-label
ACCESSPassword protected — team onlyOn
DOMAINops.acme.com with automatic HTTPSLive
BRANDINGYour logo and colors, InfraNest hiddenOn
PAGESSeparate public and internal pages2 live

Everything else it handles

The parts that are only interesting when you need them.

Your own custom domain

Serve the page from status.yourdomain.com with a guided CNAME and automatic HTTPS — no certificate to buy or renew.

Full white-label

Remove every trace of InfraNest so the page reads as purely your product, logo, colors and copy included.

Private & password-protected

Lock a page behind a password for internal teams or a single client, so status stays need-to-know.

Email, SMS & webhook subscribers

Let customers subscribe however they prefer and get notified the moment an incident is posted or resolved.

Incident templates

Post consistent updates with Investigating, Identified, Monitoring and Resolved states, and affected components attached.

Scheduled maintenance

Announce planned work ahead of time so it shows as maintenance, not a surprise outage — with subscribers told in advance.

Uptime history

Show a rolling uptime bar and 90-day history per component, straight from your monitoring data.

Multiple pages

Run as many pages as you need — one public, one internal, one per client — all fed by the same checks.

Publish your first status page in minutes

Point a component at a check you already have, add your domain, and go live. Nothing to host, nothing to maintain.

A manual status page vs InfraNest

The difference between a page you update by hand and one that keeps itself current.

By hand

  • “Is it just me?” fills your support inbox during an outage
  • A separate tool to wire up, host and keep patched
  • Status edited by hand — so it is usually out of date
  • No easy way to tell customers before you start maintenance

With InfraNest

  • Live status straight from the checks you already run
  • Your brand and domain with automatic HTTPS, nothing to host
  • Subscribers notified automatically the moment something changes
  • Planned maintenance shown as planned work, not a false outage

Pairs well with

Frequently asked

Where does the status come from?

Straight from your InfraNest monitoring. Each component on the page is linked to a check, so operational, degraded and down states — plus uptime and incident history — are always live. There is nothing to toggle by hand.

Can I host it on my own domain?

Yes. Point a subdomain like status.yourdomain.com at InfraNest with a guided CNAME and we handle HTTPS automatically. The page looks like part of your own product, not a third-party service.

Can a status page be private?

Yes. Any page can be password-protected so only your team or a specific client can see it, and you can run public and internal pages side by side from the same set of checks.

How do subscribers get notified?

Visitors subscribe by email, SMS or webhook. When you post an incident or resolve one, or when a scheduled maintenance window opens, subscribers are notified automatically — no separate announcement to send.

Does it remove the InfraNest branding?

On paid plans, yes — full white-label strips every trace of InfraNest so the page reads as purely yours. The free plan carries a small InfraNest credit.

Turn your monitoring into a status page

Link a component to a check, add your domain, and go live in minutes.

Start for free