Licensing

How the trial mode works

Each module in N3uron can be used for two hours at a time, without restrictions. Upon expiration of the demo period, each module will automatically stop running. By logging into the N3uron web interface, users can re-start the demo period and enable another two hours of execution time for each module. The demo period may be restarted any number of times.

How licensing works

N3uron is a modular platform and licensing is therefore module-based. Licensed and un-licensed modules can operate side-by-side, allowing some modules to be tested in trial mode (demo), whilst others run with a licensed status (production).

After software installation is complete, a unique UID for the node is generated. When acquiring a new license, you will be required to provide the UID and Host for where N3uron is installed. After purchasing licenses for the required modules, the customer receives a file containing the corresponding license associated with that specific UID and Host. 

There are two different types of licenses:

• Local licenses
• Remote licenses

Add a license

In order to add a license file, open the WebUI, navigate to Licensing > Add license file, and upload or copy/paste the license file. All modules included in the license file will automatically switch from demo to production mode. No restart is required. 

Once the license has been added, the following information is shown:

• Host: Specifies the name of the node to which the license has been added.
• UID: Specifies the UID associated with the license.
• Expires: Specifies the date on which the license expires.
• Expires support: Specifies the date on which the support expires.
• Type: Specifies the type of license. This can only be a production license.
• Status: Displays the current license status. It can be valid, invalid, or expired.

Remove a license

On the other hand, in order to remove a license file, first open the WebUI again, navigate to Licensing > Remove, and remove the license file uploaded. No restart is required. 

Recover a license

Finally, in order to recover a license, navigate to Licensing and click on the Unlicense button. This will generate a text file that you will need to download and send to your N3uron sales representative, together with the Host and UID of the destination node so that the N3uron team can generate and send back a new license. This option exists for users who need to migrate their license to a new node.

Local Tags vs Remote Tags

N3uron module licensing falls into two categories: Local Tags (Local Licenses) and Remote Tags (Remote Licenses). The key difference lies in where the data originates. 

Local Licenses

Use Local Licenses when a node processes data from its own local sources.

• Definition: A N3uron module is considered Local when it processes data originating from its own host node via physical drivers (Modbus Client, OPC UA Client, Siemens Client, etc.).

• Use Case: When an Edge node collects data from a local data source (PLC, meter, SCADA, database, etc.) and exchanges it directly with a third-party application or system (e.g., MQTT Broker, SCADA system, etc.), the modules handling this operation (OPC UA Client, Modbus Client, MQTT Client, OPC UA Server, etc.) are licensed as Local.

• Value: This licensing model suits standalone sites where data processing and external communication occur on-site, without reliance on a central hub.

Remote Licenses

Use Remote Licenses when a node processes data received from other N3uron nodes. Remote Licenses are typically required at the central node in a Centralized Architecture (using N3uron Links).

• Definition:  A module requires a Remote license when it operates on data received from other N3uron nodes via Links.

• The "Data Origin" Rule: When the Central Node uses a module (Historian, MQTT Client, Scripting, Web Vision, REST API Server, etc.) to process, store, or exchange data that was originally collected by Edge nodes, that module requires a Remote license.