Start from self-hosted evidence, then offer a managed path.

Guardus should make it clear that the managed product is planned while the current proof comes from a working self-hosted status system.

What exists now

This landing app is static-export compatible and can ship independently on guardus.birdor.com. The product proof comes from the Plumego Gatus use case: configuration, endpoint checks, suites, API, UI, alerting, storage, and metrics.

  • Landing pages require no runtime API dependency.
  • Route content can be reviewed and localized in the app workspace.
  • The app remains in draft status until managed capabilities exist.

Managed deployment path

The future Console should handle tenants, teams, scenario configuration, check execution, alert routing, status publishing, billing, and audit history.

  • Waitlist first: capture demand for a managed service.
  • Preview next: hosted demo tenant and authenticated Console flows.
  • Launch later: production checks, billing, account controls, and operational support.