Skip to content
GridNMS Docs

First Run

When the installer reports the API healthy, open the UI at the address it prints (for example http://localhost:3001) 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:

UI + API:  http://<host>:3001        (one port — the server serves the SPA)
Health:    http://<host>:3001/health →  {"status":"ok"}

How licensing is enforced

Section titled “How licensing is enforced”

Your license state, feature set, and device limit are controlled centrally by the platform and verified locally against a bundled public key. On first boot the connector registers with the platform using your license key, receives a short-lived signed license token, and re-checks in hourly.

Editing the local database can’t grant a higher tier — the signature won’t verify. If the instance can’t reach the platform, it runs on the last good license through a short grace window, then degrades. (A true offline / air-gapped tier with a long-lived token is available — see Air-gapped deployments.)

What’s next

Section titled “What’s next”