Licensing and billing FAQ

How does licensing work?

Every install ships with a license client that periodically "phones home" to license.summitpsa.com, sending your license key plus light telemetry (hostname, active seat count, app version) and caching the server's response. The default check interval is every 12 hours.

What is a "seat"?

A billable seat is an active, non-system agent. Internal system accounts (such as the scheduler) are not counted.

What happens if the license server is unreachable?

Nothing breaks. The client keeps the last good response and operates from cache. There is a grace window of 7 days (the default) before the app shows a warning banner asking you to check connectivity. The license check never raises errors and never hard-locks the application.

Does my install stop working if the license expires or is suspended?

The application is not hard-locked by licensing. Instead, a banner appears with the appropriate severity — for example a critical banner for an expired or suspended key, or an unrecognized key, and informational notices when expiry is within 30 days. The banner is the enforcement surface; functionality is not cut off by the client.

What if I go over my seat limit?

Exceeding your covered seats raises a warning banner asking you to add seats. Over-seat usage is tracked for billing accountability (with a short grace period) but is never enforced by locking the app.

Can I force a license re-check?

Yes. The license banner includes a "Check now" action (an admin with settings-management permission can use it) that re-polls the license server immediately rather than waiting for the next scheduled check.

How is the license key tied to installation?

The key doubles as your credential to pull the application image from the license-gated registry. A suspended or expired key is rejected at pull time, so you also can't download new versions until it's active again.