Protect and License CODESYS Applications with CodeMeter
The integration of CodeMeter with CODESYS gives developers, device manufacturers, and industrial software vendors a common foundation for protecting application code and intellectual property, controlling the use of software-based functionality, and delivering licenses securely throughout the product lifecycle.
CODESYS projects, boot applications, libraries, runtime functionality, and optional device features can be protected against unauthorized access, copying, reuse, and manipulation while being licensed through permanent, trial, subscription, feature on demand, or metric-based models. With options ranging from device-bound software licenses and portable hardware containers to local network licensing, the implementation can be adapted to the target architecture, threat scenario, available connectivity, required portability, production-continuity requirements, and installed-base management processes.
What Is CODESYS?
CODESYS is an independent software platform for industrial automation based on the international IEC 61131-3 standard. It combines a development environment for creating controller applications with runtime systems that execute these applications on PLCs, industrial PCs, embedded devices, and virtualized control platforms.
Device manufacturers can integrate the CODESYS Runtime Toolkit into their own controllers, while machine builders and automation engineers use the CODESYS Development System to create the applications that control machines, production lines, buildings, energy systems, mobile equipment, and other industrial assets.
As more of the value and differentiation of these products moves into software, protecting and licensing that software becomes an essential part of the product strategy.
What Does the CodeMeter Integration with CODESYS Enable?
CodeMeter provides the protection and licensing technology used within the CODESYS ecosystem. The integration supports several objectives:
- Protecting CODESYS projects, executable applications, libraries, and proprietary functionality
- Preventing unauthorized copying or use of protected applications
- Assigning licenses to devices, users, applications, or specific features
- Enabling permanent, trial, subscription, feature on demand, and metric-based license models
- Storing licenses in software-based or hardware-based containers
- Activating licenses during production or after devices have been deployed
- Expanding licensed functionality without replacing the underlying hardware
- Supporting licensing workflows for physical and virtualized controllers
This integrated approach allows software protection, entitlement management, and commercial licensing to become part of the product lifecycle rather than separate processes added after development.
Who Benefits from the Integration?
CODESYS Application Developers
Machine builders, system integrators, and automation engineers can protect the applications they create against unauthorized access, copying, and reuse. This is particularly important when an application contains proprietary process knowledge or controls a machine whose competitive value lies substantially in its software.
Device and Controller Manufacturers
Manufacturers can license runtime functionality and optional device features individually. A common hardware platform can therefore support multiple product variants, with the required capabilities activated by license.
This simplifies product differentiation and makes it possible to sell additional functionality after a device has entered service.
Library and Add-On Developers
Developers of proprietary libraries, plug-ins, and functional extensions can protect their intellectual property and control who is authorized to use it. Licensing can turn specialist automation expertise into a commercial software product without requiring developers to build a proprietary licensing system.
Machine Operators and End Users
Operators can purchase the functionality needed for a particular application and add capabilities later as requirements change. Depending on the implementation, licenses can remain attached to a specific device or be stored in a portable hardware container.
Protecting CODESYS Applications and Intellectual Property
Industrial controller applications can contain valuable engineering knowledge: machine sequences, process parameters, control algorithms, motion profiles, and other application-specific expertise.
The CODESYS Key uses CodeMeter technology to provide protection functions including:
- Project encryption to protect CODESYS application source code
- Encryption of the boot application to protect executable code on the controller
- Access protection for libraries and application functions
- Secure storage of the cryptographic keys and licenses required to use protected components
A protected application can be associated with the license stored in the CODESYS Key. Copying the application to another controller does not automatically transfer the authorization needed to use it.
This helps developers prevent unauthorized reuse of their work and makes it considerably more difficult to reproduce a machine simply by copying its control application.
Licensing Software and Device Functionality
The integration does more than restrict access. It allows manufacturers and developers to define which software functions customers may use and under what conditions.
Depending on the product and implementation, possible models include:
- Permanent licenses: The licensed functionality can be used indefinitely.
- Feature on Demand: Additional functions can be activated after the device has been delivered.
- Trial licenses: Customers can evaluate functionality for a defined period or under defined conditions.
- Subscription licenses: Usage rights remain valid for a specified term and can be renewed.
- Application-based licenses: The license level reflects application requirements, such as the number of I/O channels or controlled axes.
- Update entitlements: An installed version can continue operating while access to subsequent software versions depends on a valid update entitlement.
Application-based licensing is particularly relevant when standardized hardware replaces traditional product variants. Instead of tying the price solely to processor performance or device size, the software can be licensed according to the capabilities that the application actually requires.
Select the Right License Container
Industrial environments differ significantly in terms of connectivity, device architecture, maintenance processes, and operational risk. CodeMeter therefore supports different ways of storing and managing licenses.
Software-Based Licenses
A software license container binds the license to the target system without requiring additional hardware. Licenses can be made available electronically and used immediately after activation.
This approach is well suited to devices on which the necessary system characteristics remain sufficiently stable throughout the operational lifecycle.
CODESYS Key
The CODESYS Key is a USB security device based on CodeMeter technology. It stores CODESYS and compatible third-party licenses independently of the target system.
Because the license is held on the CODESYS Key, it can be transferred to another compatible device. The hardware unit also supports CODESYS security functions such as project encryption, boot application encryption, and access protection for libraries and application functions.
Device-Specific Binding
For OEM implementations, licenses can be bound to selected characteristics of the target device. This allows the licensing mechanism to reflect the manufacturer’s hardware architecture and production processes.
Network Licensing
Where supported by the licensed product, licenses can be managed centrally on a license server and made available across a local network. This can be useful for industrial PCs, virtualized environments, and installations in which licenses should not be stored separately on every individual system.
The appropriate option depends on the threat scenario, available connectivity, required portability, operational environment, and the logistical and administrative implications of using hardware containers.
Delivering Licenses from Production to the Field
Industrial licensing has to work across complete device fleets, not only for individual online users.
CodeMeter-based workflows can support several stages of the product lifecycle:
- Individual activation following an online purchase
- License provisioning during device production
- Batch activation of multiple controllers
- Delivery of additional licenses to devices already operating in the field
- Upgrades when an application requires more functions or greater capacity
- Delegated or self-service license creation through a license portal
This gives manufacturers the flexibility to integrate licensing into their existing production and order-processing systems. It also creates a foundation for aftermarket business: functionality can be activated or expanded without recalling the device or replacing its hardware.
Designed for Industrial Operating Conditions
Licensing in industrial automation must take production continuity into account. A controller may remain in service for many years, operate in a segmented network, or be located where no permanent Internet connection is available.
For this reason, an industrial licensing architecture should not automatically depend on continuous access to a cloud service. Licenses can be stored locally in a software container or CODESYS Key, while network-based arrangements can keep license management within the operator’s own infrastructure.
The selected model should balance commercial control with operational resilience. License renewals, hardware changes, software updates, and recovery procedures all need to be considered before devices are deployed at scale.
Licensing for Virtual PLCs and Software-Defined Automation
Virtual PLCs separate control functionality from a dedicated physical controller. Multiple control instances can run on one industrial computer or server, often alongside applications for visualization, analytics, artificial intelligence, or cloud connectivity.
This architecture offers greater flexibility, but it changes the licensing challenge. Ownership of a physical device no longer provides a reliable indication of how many controller instances are being used. Software vendors need a way to control the creation and operation of virtual instances and to assign the appropriate entitlements.
CodeMeter provides licensing mechanisms that can support these software-defined environments. Depending on the product architecture, licenses can be associated with individual instances or supplied through a local network license server, including redundant configurations when high availability is required.
The Future of Industrial Software Licensing
In this interview, Dieter Hess, CEO of the CODESYS Group, and Stefan Bamberg, Director Sales and Key Account Management at Wibu-Systems, discuss how industrial licensing is changing as automation becomes increasingly software-defined.
This is a YouTube video. If you click on this video you agree to the privacy & terms of Google and you also agree to our privacy policy.
The discussion explores:
- Why manufacturers are commercializing software separately from hardware
- The continuing role of permanent licenses in industrial automation
- How feature-on-demand licensing creates aftermarket opportunities
- Why application-specific metrics can be more appropriate than hardware-based pricing
- The challenges of subscription and cloud licensing in production environments
- How virtual PLCs change the relationship between software instances and physical devices
The central consideration is clear: Industrial companies need greater commercial flexibility, but licensing must never disregard availability, connectivity, and production continuity.
Frequently Asked Questions
The CODESYS Key can be used to encrypt CODESYS projects and boot applications. The cryptographic keys required to access or execute the protected content are stored in the hardware security device. Copying the application alone does not transfer the corresponding authorization.
Yes. CodeMeter can be used to assign licenses to individual software functions, libraries, runtime capabilities, or commercial product variants. This enables feature on demand and other modular sales models.
No. Many licensing scenarios can use a software-based license container. The CODESYS Key is valuable when portability, independence from the target device, or its application-protection functions are required. The appropriate container depends on the device, operational environment, and licensing model.
Yes. CodeMeter supports workflows for activating additional functionality, upgrading license levels, and delivering entitlements to devices in the field. The exact process depends on the device architecture and available connectivity.
No. Licenses can be stored locally in software- or hardware-based containers via file exchange. If supported, network licensing can also be implemented within the operator’s local infrastructure. For certain activation or update processes (e.g., adding, modifying, or revoking existing licenses), file exchange is required again. A continuous connection to the outside world is not necessary.
Yes. CodeMeter can provide the entitlement control needed to license software instances independently of the underlying physical hardware. The precise architecture – such as local binding or network licensing – depends on the CODESYS product and deployment environment.
Protect Your Engineering Investment and Create New Digital Business
Whether you develop CODESYS applications, manufacture industrial controllers, or sell automation software, CodeMeter can help you protect your intellectual property and turn software functionality into controlled, marketable products.
Talk to our experts about protection and licensing for your CODESYS-based solution.