Guardus models checks around user-visible workflows: login, checkout, webhook delivery, API availability, certificate freshness, and scheduled background flows.

Each scene can combine endpoint reachability, response timing, body assertions, headers, DNS, TLS, and business-specific conditions into one operator-facing signal.

• Show a customer-facing public status result without exposing internal diagnostics.
• Keep operator-only details ready for the future Console view.
• Group related checks into suites so one degraded journey is easier to explain.

The current landing site stays static. Demo content is intentionally descriptive until a managed environment can run real tenant checks and authenticated Console sessions.

• Public route: status summary, incident context, and plain-language service health.
• Console route: check configuration, run history, alert routing, and team workflow.
• Waitlist route: capture teams that want a managed solution instead of self-hosting.