Nitro Injection or Afterburner – Protecting Software During or After Compilation

Share:
2026-10-06 - 2026-10-07
Online Masterclass

Software developers typically have two options for integrating protection and licensing into an application: use an API to verify license entitlements, or protect the executable code through encryption and obfuscation.

At first glance, the distinction seems straightforward: APIs are used for licensing, while tools are used for software protection. But separating protection and licensing creates a potential point of weakness between the two and can substantially reduce the overall protection of the software.

CodeMeter deliberately combines these two mechanisms. CodeMeter Protection Suite intertwines protection and licensing so that attackers cannot simply bypass one layer while leaving the other untouched.

The webinar explores the different AxProtector technologies within CodeMeter Protection Suite, each designed for specific programming environments and protection scenarios. It focuses in particular on protection applied after compilation versus Compile Time Protection (CTP), which integrates protection directly into the compilation process.

Think of it as the difference between nitro injection and an afterburner: Both enhance performance, but they do so at different stages. Likewise, CodeMeter Protection Suite can protect software during compilation with Compile Time Protection or apply protection to the compiled application afterward post compilation.

The close connection between protection and licensing is central to the CodeMeter security concept, but it does not restrict users to a single deployment model. For applications that require protection without licensing, CodeMeter Protection Suite can also be used in Unbound Mode. The webinar shows how this works and how to maximize the protection level within these parameters.

At the other end of the spectrum, CodeMoving provides a high-security option for use cases requiring maximum protection and strong license binding.

Nitro Injection or Afterburner – Protecting Software During or After Compilation

6 October 7.00 pm CEST English Register
7 October 9.00 am CEST English Register
7 October 2.00 pm CEST German Register
I can't attend the live event, but send me the recording when available. Request
Check your Time Zone

Agenda

  • Overview of CodeMeter Protection Suite
  • Programming languages with intermediate code (.NET, Java)
  • Programming languages without a compiler (JavaScript, Python)
  • Programming languages with traditional compilers (C/C++, Delphi, Golang, etc.)
    • Encryption as a single block
    • Encryption of individual functions using a PDB file
    • Protection with Compile Time Protection
  • Optional mode: Protection without licensing
  • High-security option: CodeMoving
  • CRA compliance: CPSRT library

The Cyber Resilience Act (CRA) adds another important consideration: software vendors need to be able to address vulnerabilities over the lifetime of their digital products.

The AxProtector tools in CodeMeter Protection Suite therefore shift a substantial part of the security functionality into a dedicated component, CodeMeter Protection Suite Runtime (CPSRT), while requiring only minimally invasive changes to the software itself. This architecture gives software vendors the flexibility to update their application and CPSRT independently when required.

Join the webinar to compare the available protection approaches, identify the one that fits your application, and understand how to implement it with CodeMeter Protection Suite.

For those who join us live and answer a quick survey at the end of the session correctly, there is an additional treat in store: We will draw the winner of a four-hour free CodeMeter consultation from the most brilliant minds in our company. The winner will be notified in the replay announcement.

To top