Licensing

Upload license files in the Licenses administration page. The page shows active endpoint and Runner capacity, current usage, remaining capacity, endpoint-kind usage, active licenses, and licensed feature entitlements.

Endpoint capacity

Endpoint capacity licenses add capacity as endpoint equivalents. A license with endpoint capacity 25 adds capacity for 25 full-weight endpoints.

When multiple valid endpoint capacity entitlements are active, Ordyn sums their capacity.

Ordyn counts approved endpoints by endpoint kind:

Endpoint kind	Capacity weight
Agent endpoint	1.00
Switch endpoint	1.00
Generic endpoint	0.33
Printer endpoint	0.33
Telematik card terminal endpoint	0.50

Only approved endpoints count toward used capacity.

Capacity enforcement

Ordyn checks capacity when an endpoint would become approved.

Approval is blocked when approving the endpoint would exceed active capacity. This applies to:

• approving a pending endpoint
• automatic agent enrollment when the enrollment token auto-approves endpoints
• claiming a staged agent endpoint through enrollment
• creating manual non-agent endpoints, because those endpoints are approved immediately

Manual agent endpoints are created as staged endpoints and do not consume capacity until they are approved.

If capacity later drops below current usage, for example because a license expires or is deleted, Ordyn marks the installation as over capacity in the license summary. Existing approved endpoints are not automatically rejected, suspended, revoked, or deleted.

When over capacity, Ordyn determines which approved endpoints are within capacity by approval time. Earlier approved endpoints are selected first. Approved endpoints outside the active capacity cannot receive additional instructions.

This affects:

• creating a direct instruction for an endpoint, for example by browsing the filesystem or registry.
• starting a job for selected endpoints

Runner capacity

Every installation includes capacity for two configured Runners without a license. Runner capacity entitlements add licensed slots to these two included slots. Each entitlement unit adds one Runner slot, and capacity from multiple active Runner licenses is combined.

Every configured Runner uses one slot, including disabled, offline, and unenrolled Runners. Creating a Runner is blocked when all included and licensed slots are in use.

If Runner capacity later drops below the number of configured Runners, existing Runners remain configured. Ordyn assigns the available slots to the earliest-created Runners first. The Runner list and Runner details show whether each Runner is entitled or outside the available capacity.

Runners outside the available capacity cannot receive a new job reservation. If a job target has compatible Runners only outside capacity, the target fails with a licensing error. A target that already reserved a Runner can finish its work and workspace cleanup even if that Runner falls outside capacity while the target is running.

License expiration and deletion

Licenses have a validity period. A license is active only while:

• validation status is valid
• it has not been deleted
• its validity start is not in the future
• its validity end is in the future

Expired licenses are ignored for capacity and feature entitlement. Ordyn rejects uploading a license file that is not currently valid or is already expired.

Deleting a license removes it from active licensing calculations.

The license summary shows separate next-expiration dates for active endpoint and Runner capacity licenses. Feature entitlements show their own next expiration.

Package discovery service license

Package discovery service execution requires an active package discovery service license.

Without an active package discovery service license:

• manual package discovery scans are rejected
• enabling package discovery targets is rejected
• scheduled package discovery dispatch is skipped
• queued package discovery scans fail before execution

Configuration that does not enable package discovery can still be saved.