Trust
Nova's default motion is a managed private-beta service. A self-hosted or private deployment may be appropriate for regulated teams, strict network boundaries, or data-residency requirements, but it requires design review.
Private deployment is worth discussing when telemetry cannot leave a controlled environment, when customer networks require private routing, or when internal security teams need direct control over the observability stack.
It is not the default option for small teams that simply want Linux host monitoring quickly. The managed beta service is the simpler path for most early customers.
NovaUI is a Django application that manages tenants, users, collector nodes, feature toggles, limits, audit logs, billing state, Grafana org mapping, and OIDC claims. The current operational stack also depends on Redis-backed feature state, Grafana integration, APISIX/GitOps resource generation, and telemetry backends such as Mimir and Loki.
A private deployment therefore needs more than a single binary. It needs infrastructure, secrets management, backup/restore planning, upgrades, monitoring for the monitoring system, and clear ownership boundaries.
Before presenting self-hosted deployment as an offer, Proxima should confirm target infrastructure, supported regions, support hours, upgrade responsibility, retention storage, tenant model, TLS and identity integration, and incident response expectations.
For now, this page should help qualify serious private-deployment conversations without promising a public self-hosted SKU.