Frequently asked questions

Answers about Nova V1, the managed Linux monitoring service.

What is Nova?

Nova is a Thailand-hosted managed Linux server monitoring platform. It uses NovaUI as the control plane, Grafana for dashboards, Grafana Alloy on hosts, Mimir for metrics, and Loki for logs.

How do I add a server?

An admin creates a collector in Nova, Nova generates a one-time install token, and you run the generated curl/bash installer on the Linux host. Alloy then pulls remote config from Nova and starts sending metrics and logs.

What telemetry is included in V1?

V1 includes Alloy health, Linux CPU, RAM, disk usage, disk I/O, network I/O, uptime, systemd journal logs, and up to 3 fixed file log paths per host. Docker metrics and logs are optional per node.

Does Nova support Windows, Kubernetes, or traces?

Not in V1. The first release is intentionally focused on managed Linux host monitoring. Windows monitoring, Kubernetes, Tempo traces, custom Alloy configs, and custom dashboard support are outside the V1 scope.

How does Grafana access work?

NovaUI is the identity source. Users log into Nova, Nova issues OIDC claims with the tenant and role, and Grafana maps the user into the correct organization as Admin, Editor, or Viewer.

How is Nova billed?

Pricing is not finalized during private beta. Proxima will confirm scope, host count, support needs, and any beta commercial terms directly before onboarding.

Do I need to host anything myself?

No. Nova hosts the control plane and monitoring stack. You install the collector on each Linux host you want monitored.

Can Nova run offline?

No. Nova collectors need network access to the managed Nova control plane, CFG server, Mimir, and Loki. The server also needs access to https://github.com/grafana/alloy/releases/ for Alloy binaries during install; you can block that URL after install. If you do not want hosts to allow internet access, Proxima can provide a self-hosted control plane. An Alloy download mirror built into the control plane is planned.

What retention is planned for V1?

The current V1 product definition targets 1 year of metrics retention and 90 days of logs retention.