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

The wizard is deliberately short — it establishes your instance’s identity and your first login, then hands off to an in-app checklist:

1. Site configuration — name your deployment and confirm the access URL.
2. Admin account — create your first administrator login (your email is the login id).
3. Finish — review the summary and sign in with the account you just created.

Everything else — connecting a collector, defining your networks, running discovery, adding device credentials, enabling alerting — is guided by the Deployment Checklist that appears inside the app after you sign in. Each checklist step links to the right page and ticks itself off as it detects the work is done, so you can complete them in any order and at your own pace.

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

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 checks in every few minutes over a single outbound connection. Each successful check-in refreshes a signed license that is valid for 48 hours.

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 normally on the last refreshed license — for up to 48 hours after its last successful check-in. Beyond that window the license is treated as expired: collectors can no longer connect and licensed features pause. Nothing is deleted — once connectivity returns, the next check-in refreshes the license and normal operation resumes on its own.

A fully offline option for permanently disconnected sites is planned — see Air-gapped deployments.

What’s next

• Install more collectors for additional sites and segments.
• Read Getting the real source IP before pointing real syslog at a collector.
• Learn the product: Using GridNMS.