Join the waitlist for hosted Guardus instead of self-managing status infrastructure.

This route intentionally acts as the primary CTA until pricing, billing, and account creation are implemented.

What waitlist teams are asking for

Guardus is planned for teams that want scenario-level monitoring and clear public status communication without operating the underlying status stack themselves.

  • Managed execution of active checks and scenario suites.
  • Hosted public status pages with customer-ready incident language.
  • Console workflows for configuration, history, alerts, and team access.

What is not live yet

There is no production waitlist backend, account signup, billing plan, or hosted Console in this milestone. The landing CTA defines intent and route structure so those systems can be connected later.

  • No paid plan claims until billing is implemented.
  • No SLA claims until managed operations are defined.
  • No tenant data collection from this static route.