SolarWinds does not use a single licensing structure across all of its products. The license type, capacity, and activation process depend on the specific product, edition, deployment model, and resources being monitored or managed. For this reason, the actual deployment scope should be defined before selecting a license.
Depending on the product, SolarWinds licensing may be based on nodes, interfaces, volumes, devices, users, databases, log sources, or other monitored resources. Many current products also use subscription licensing, with terms that may be annual or multi-year.
For example, network monitoring products may measure licensing according to monitored infrastructure and its components, while service management products can use a user- or device-based model. As a result, one licensing metric cannot be applied across the entire SolarWinds portfolio.
Activation generally takes place after the product has been installed. During this process, information such as a unique Machine ID may be used to identify the installation environment.
In connected environments, activation can be completed through the product's administration interface, License Manager, or the relevant licensing section. The exact procedure depends on the product and deployment type.
For isolated environments or systems with restricted internet access, some products support offline or manual activation. In this approach, the required system information is generated from the target environment, the license file is obtained through the appropriate licensing process, and the file is then transferred back and imported into the installation.
Before selecting a license, the product, number of monitored resources, deployment model, required modules, and network connectivity should be identified. These factors determine the appropriate licensing structure and required capacity.
Licensing requirements can also change as the environment grows. Adding servers, network devices, databases, users, or other monitored resources may increase the required capacity.
For this reason, licensing is best considered alongside deployment planning. Keeping the purchased entitlement aligned with the actual scope of the environment helps maintain appropriate coverage as the infrastructure changes.