01 / PUBLIC EDGE
Probe what the internet can reach
Only explicitly approved service names and verified health results belong on the public surface. Unknown data remains unknown instead of becoming synthetic uptime.
SSRF-safe by designPublic launch foundation
Know what is healthy.Reveal only what is safe.
One status platform for internet-facing services and private networks—designed around outbound-only agents, server-side authorization, and deliberately redacted public views.
- Exact email allowlist
- Server-side access policy
- Separate public projection
Current status
Public surface operationalStatus websiteHistory collecting
Public status APIHistory collecting
Built on a clear boundary
Useful for viewers. Honest for operators.
A status page should answer whether a service is healthy without exposing the endpoint, network path, diagnostics, or internal identity behind that answer.
02 / PRIVATE NETWORK
Keep internal services internal
Private names and diagnostics render only after signed-in email authorization. A minimized outbound snapshot can be connected without publishing internal targets.
Identity-scoped agents03 / PUBLIC PROJECTION
Publish a deliberate summary
Public APIs are a separate, redacted view—not private records serialized and hidden later by the interface.
Deny by defaultOne control plane, two paths
Health follows the network path that matters.
Public probes observe what customers see. Private agents observe what operators see. Every result keeps its source, time, and configuration revision.
PUBLIC
Internet endpoints
Regional probes
Control planeEvaluate · redact · publish
PRIVATE
Internal services
Outbound agents
Current implementation
Start with a trustworthy public surface.
The publishable surface now separates anonymous public health from an email-authorized private view. Company-confidential monitoring data remains disabled until its separate approval gate is met.
02
Ready to publishPublic/private access boundary
- Honest public statusResponsive health view with no fabricated historyREADY
- Server-side email authorizationExact allowlist matching with generic denial responsesREADY
- Private snapshot boundaryNo private names in public HTML, APIs, or cachesREADY
- 04Live private monitor feedConnect only after targets and allowed data are approvedNEXT
Open the public service view