Skip to content
dcontrol

License

License

Introduction

dcontrol and most of its plugins require a license to run. Licenses are perpetual and computer bound.

A trial license can be activated for a limited duration of 30 days. Trial licenses will only be requested for the configured plugins in the settings file, so that when on a later date, running a licensed version is combinable with a trial license for a given plugin that was previously not used in trial mode. Trial licenses have no restrictions other than the 30-day time limit.

Upon purchase of a dcontrol license you’ll receive a license.json file which needs to be placed in the config directory /etc/dcontrol/license.json, in the current working directory, or specified with the -l, --licensefile flag.

The first time licenses will need to be activated online (access to the license server https://license.dotcircle.co is required for this step).

Licenses can be released individually (for each plugin, or the core) or in bulk (up to 3 times) to be moved to another computer.

Moving the license to a different computer

Since the license is computer bound, in order to move it to a different one, it must first be released from the current one. This can be done for a single product by running dcontrol --license-release <product> or for all products at once by running dcontrol --license-release-all.

When releasing a single license you need to copy the License key from the license.json file to the new one, when bulk releasing all licenses, you can copy over the license.json file. Note that releasing the licenses must be done on the computer they have been bound to. Moving the license.json file over and releasing them from a different computer won’t work.

Adding a new product license to an existing license file

The basic hierarchy of the license.json file is as follows:

{
  "dcontrol": {
    "activation_key": "12345-12345-12345-12345-123456"
  },
  "modbusTCP" :{
    "activation_key": "12345-12345-12345-12345-123456"
  },
  "websocket" :{
    "activation_key": "12345-12345-12345-12345-123456"
  }
}

Once activated, the activated license and verification codes will be added.

To add a new product license to an existing license file, edit the license.json file and add the product key to it.

Command line argument options

The following command line arguments are available related to license management:

Help

If you’re having any trouble installing a license file please contact dotcircle support.

Third party licenses

The core package uses the following libraries:

  • Qt6 licensed under LGPLv3

  • spdlog Copyright (C) 2016 Gabi Melman. Licensed under MIT

  • fmt Copyright (C) 2012 - 2016, Victor Zverovich. Licensed under MIT

  • yaml-cpp Copyright (C) 2008-2015 Jesse Beder. Licensed under MIT

  • exprtk Copyright (C) 1999 - 2020 Arash Partow. Licensed under MIT

  • prometheus-cpp Copyright (C) Jupp Müller. Licensed under MIT

The various official plugins make use of (in addition to the core package libraries) the following libraries:

  • icalparser Licensed under LGPLv2.1

  • libmodbus Licensed under LGPLv2.1

  • oscpkt Copyright (C) 2010 Julien Pommier. Licensed under zlib

  • OpenSSL Copyright (c) 1998-2019 The OpenSSL Project. All rights reserved. Licenced under OpenSSL and SSLeay


Copyright 2025 © dotcircle