Skip to content
GridNMS Docs

First Run

When the installer reports the API healthy, open the UI at the address it prints (for example https://localhost — accept the one-time self-signed-cert warning) and complete the one-time setup wizard.

The setup wizard

Section titled “The setup wizard”

The wizard walks you through first-boot configuration:

  1. Site configuration — name your deployment and confirm the access URL.
  2. Admin account — create your first administrator login.
  3. Network discovery (optional) — scan a CIDR or range to find devices.
  4. Sample data (optional) — load a demonstration dataset to explore the feature set before connecting real infrastructure.
  5. Service startup — bring the background services online.
  6. Login — sign in with the admin account you just created.

Verify health

Section titled “Verify health”

The installer prints the access URL when the stack is healthy. You can confirm it directly:

Web app:  https://<host>            (self-signed by default — see HTTPS / TLS)
Health:   https://<host>/health →  {"status":"ok"}

The UI and API are served together over HTTPS (port 443) by default, with a self-signed certificate generated on first boot — accept the browser warning, or swap in your own certificate. See HTTPS / TLS.

How licensing works

Section titled “How licensing works”

Your plan, features, and device limit are managed by GridNMS and checked automatically. On first start your instance registers using your license key, then quietly re-checks about once an hour over a single outbound connection.

Because your plan is managed centrally, it can’t be changed by editing anything locally. If your instance temporarily can’t reach GridNMS, it keeps running on the last known-good license for a short grace period. A fully offline option is available for disconnected sites — see Air-gapped deployments.

What’s next

Section titled “What’s next”