Understanding SLASCONE

Understanding SLASCONE


SLASCONE is a modern licensing and analytics solution, born in the cloud era. Unlike legacy licensing solutions providing complex client libraries and requiring a new license key every time a license parameter changes (e.g., expiration date, feature), SLASCONE’s approach is different.

In a typical scenario, the client you want to license/protect has to initially communicate over https with SLASCONE in order to get activated (using the provided license key). After the initial activation, the client periodically pulls from SLASCONE the actual license parameters. The need to generate new license keys upon license parameter change becomes obsolete.



As a vendor you have to decide how often your software communicates with SLASCONE in order to pull/refresh the actual license parameters (heartbeat). Heartbeats constitute the fundament of SLASCONE.

Practically, heartbeats can be triggered in two ways:

  • Periodically: by implementing such a logic in your software.
  • Manually: by giving the end user of your software the option to trigger a heartbeat, which means to refresh his licensing data.


The heartbeat frequency depends on your business model. Regardless of the business model though, it is recommended to at least:

  1. trigger a heartbeat every time a new version/hotfix of your software is installed.
  2. give your end users the option to manually trigger a heartbeat.

This minimum recommendation suffices for many business scenarios. Nevertheless, there are scenarios in which you must/can trigger additional heartbeats.


Let’s us now explain how this translates in some typical business scenarios:

  • Perpetual: In such a case, SLASCONE is mainly used in order to activate the license and ensure that this license code cannot be used again. Additional periodical heartbeats would only serve if license parameters change very frequently (e.g., new feature).
  • Subscription: After the initial activation, a heartbeat must be triggered when the license expires. For example in case of a yearly subscription, a heartbeat has to be triggered after 365 days. If the end user has renewed his subscription the heartbeat succeeds and the cycle is reset. If not, the heartbeat fails due to the expired license and the software is blocked.
  • Software Version binding: For scenarios in which the end user has licensed Release 12.0 but not 13.0 thus being allowed to use the software as long as he does not upgrade to Version 13.0. The minimum heartbeat recommendation is sufficient for this scenario, since during the installation/upgrade process a heartbeat is triggered. SLASCONE returns a not compliant software version and the software is blocked.