Key Takeaways (BLUF)
Bottom Line Up Front (BLUF): While a public status page is essential for B2C and general SaaS customer communication, it is often inappropriate for internal microservices, staging environments, or strict enterprise SLAs. Broadcasting the downtime of your internal CI/CD pipeline or a dedicated single-tenant enterprise cluster to the public internet is a security and PR risk. WakeMetrics supports both Public and Private status pages, allowing you to use public pages for marketing transparency, and password-protected or IP-whitelisted private pages for internal engineering teams and VIP clients.
The Role of the Public Status Page
A Public Status Page (`status.yourcompany.com`) is a marketing and customer support asset. It exists to deflect support tickets, prove historical uptime to prospective buyers, and demonstrate transparency.
Public pages should only display top-level, customer-facing components:
- The Marketing Website
- The Web Dashboard / Login Portal
- The Public REST API
- Regional infrastructure (e.g., US-East, EU-Central)
You should never expose granular, internal architectural details (e.g., "Kafka Cluster 3", "Staging DB Migration", "Billing Cronjob") on a public page. Doing so confuses customers and provides unnecessary reconnaissance data to potential attackers.
The Role of the Private Status Page
A Private Status Page is an operational asset designed strictly for internal employees, stakeholders, or specific VIP enterprise clients. It is shielded from the public internet via password protection, SSO (Single Sign-On), or IP Whitelisting.
Private pages are used for two primary use cases:
- Internal Engineering Hub: Display the health of 50+ internal microservices, staging environments, CI/CD pipelines, and internal VPNs. When a developer's build fails, they can check the internal page to see if GitHub Actions or the internal Jenkins server is currently degraded.
- Dedicated Enterprise SLAs: If you host single-tenant, dedicated infrastructure for a massive enterprise client (e.g., a dedicated VPC for a bank), they require a status page specifically for their infrastructure. You cannot put "Bank X Dedicated Server" on your public page. Instead, you create a private page accessible only to that client's IT department.
Securing a Private Status Page
To ensure internal data does not leak, Private Status Pages in WakeMetrics can be secured via multiple methods:
| Security Method | Best Used For | Setup Complexity |
|---|---|---|
| Password Protection | Small startups sharing a page with early beta testers or investors. | Very Low (Takes 10 seconds) |
| IP Whitelisting | Internal teams operating entirely out of a corporate office or strict VPN. | Low (Requires static IPs) |
| SAML / SSO (Okta, Google Workspace) | Large enterprises requiring centralized employee access revocation and audit logs. | Medium (Requires IdP config) |
| Unique Access Tokens | Sharing dedicated SLA pages with specific enterprise clients via automated URLs. | Low |
Managing Both with a Single Truth
The true power of a modern observability platform is maintaining a single source of truth.
In WakeMetrics, your synthetic monitors continuously probe all your infrastructure. You can then route specific monitors to specific pages.
For example, the "Public API" monitor updates both the Public and Private pages. The "Internal Billing Worker" monitor only updates the Private page.
This allows your SRE team to manage hundreds of checks from one dashboard, while automatically curating the exact level of visibility for the appropriate audience.
Frequently Asked Questions
Can search engines index my Private Status Page?
No. WakeMetrics enforces strict `noindex, nofollow` meta tags on all private pages, and the authentication barrier prevents web crawlers from accessing the content.
Do I have to pay for separate WakeMetrics accounts to have both?
No. A single WakeMetrics organization can host multiple independent status pages (e.g., one public, three private) routing different components to each.
Conclusion
Do not leak your internal architecture to the public, and do not keep your enterprise clients in the dark. By utilizing a hybrid strategy of Public status pages for general transparency and Private status pages for granular, authenticated visibility, you can satisfy both your marketing and engineering requirements. Deploy your Public and Private status pages with WakeMetrics/signup/page.tsx).