Use case

Client monitoring for agencies and MSPs.

Nova's tenant model, Grafana organization mapping, team roles, collector health, and usage limits fit agencies that maintain production Linux servers for multiple clients.

Discuss agency beta Read FAQ

Fit: Agencies, MSPs, and software houses maintaining client infrastructure.
Tenant model: Separate client workspaces can map to separate Grafana orgs.
Operations: Collector health, limits, billing status, and team roles are visible in NovaUI.
Beta note: Multi-client packaging is a private-beta conversation, not public self-service yet.

Why agencies are a strong fit

Agencies and MSPs often support many small production systems but do not want to maintain a custom Grafana/Loki/Mimir deployment for every client.

Nova can give a repeatable pattern: create a tenant, enroll collectors, open Grafana in the correct org, and monitor whether client servers are online, warning, offline, or not connected yet.

What is implemented today

NovaUI already has tenant membership, admin/editor/viewer roles, collector lists, collector status, usage and limits, billing state, and Grafana org links. It also records audit events for token and file-monitor lifecycle changes.

White-label reporting, public agency dashboards, and automated monthly client reports should be treated as future roadmap unless implemented separately.

Use one tenant per client or environment where separation matters.
Use viewer roles for read-only client access when appropriate.
Track collector limits so each client scope remains explicit.
Confirm support expectations before onboarding client workloads.