Last Modified September 26, 2026
- Home
- Implementation Guides
Intro to Developer Implementation Guides
software_DNA can be implemented using two(2) distinct implementation approaches depending on the type of Application to be licensed:
| DNA Library implementation |
** Recommended **
For Apps implemented on supported OS platforms, we recommend the use of the DNA Library which acts as the interface between your App and the DNA Servers, and manages the local / encrypted CDM License file.
Supported OS platforms include Windows, MAC, Linux, Android, and Raspberry Pi.
|
| Activation API implementation |
The Activation API does not require a DNA Library and provides a HTTPS / JSON_based interface to the DNA Servers. Use for the following situations:
- for SAAS Apps (i.e. web browser based)
- for OS platforms not supported by one of the DNA Libraries
- when the DNA Library cannot be used (ex: a plug-in for an application where calls to an
external Library is not possible or difficult)
The App is responsible for functions such as read-write of the DNA License, node-locking, ...
Helper Functions are available for selected OS environments that implement the communication with the DNA Servers and manage the DNA License file. You can use the Helper Functions provided by software_DNA or design your own as explained in the Guides.
|
software_DNA gives you all the flexibility you need to implement your licensing strategy. We generally recommend using one of the following strategies which are detailed in our Online Implementation Guides:
| TurnKey (Do-All) Activation |
The TurnKey implementation of software_DNA uses the DNA_ProtectionOK API call to implement
the complete software_DNA protection solution with built-in GUI screens
in one simple function call. This includes:
Activation process
De-Activation process
Re-activation process
Validation process
Evaluation Code feature (optional) in either the Registration mode
or the Evaluate Now mode
"Send Lost Password" feature
"Set Proxy" option
"Prefix" option
Provides a full set of built-in user interface screens to capture all required information
Set Language for dialog boxes and messages
Supports all license models
|
| Custom Activation |
The Custom implementation strategy uses the full breadth of the software_DNA API
using a 2-step process, providing detailed control
over the activation process and User input screens of your design to meet your activation flow
requirements.
Supports all Licensing Models
|
| StreamLined Activation |
A streamlined implementation strategy using the full breadth of the software_DNA API
using a 1-step process, providing detailed control
over the activation process and User input screens of your design to meet your activation flow
requirements.
Requires only one GUI screen of your design to capture license information.
It supports the following license schemes:
- Single-User / Multi-Computer Licensing without the "Roll-Over Re-Activation" option
- Multi-User Licensing
- Floating Licensing
|
View the Online Developer Guide based on your selected implementation approach.
Various Guides