Licensing

Fuzio is a commercial library that requires a valid license key in order to work. This guide focuses on technical aspects of working with the license.

For pricing information and details on terms and conditions please contact us.

Adding the license to a project

Fuzio needs a license key to run. The license key is a string of capital letters and numbers that you can set in two ways.

Using the fuzio.license.key system property:

Java
Kotlin
System.setProperty("fuzio.license.key", "your_license_key");
System.setProperty("fuzio.license.key", "your_license_key")

Another way is to use the licenseKey(String) engine option. Setting the key this way allows you to use different licenses for different Engine instances:

Java
Kotlin
var engine = Engine.newInstance(
        EngineOptions.newBuilder(HARDWARE_ACCELERATED)
                .licenseKey("your_license_key")
                .build()
);
val engine = Engine(RenderingMode.HARDWARE_ACCELERATED) {
    license = FuzioLicense("your_license_key")
}

Setting the license key as the engine option allows you to override the license key set in the fuzio.license.key system property.

Protecting the license key

Our license keys are always in plain sight. It’s important to note that since the key is just a string literal, complete concealment is not feasible.

To enhance security, you can use techniques such as obfuscation or fetching the license key at runtime. There is no single recommended method. If you choose to protect your license key, you can decide which technique works best for you.

Avoid setting the key through the -Dfuzio.license.key command line argument, because its value can be unintentionally exposed in the process monitor, test reports, crash dumps, and other artifacts.

If you discover your key in public access, please contact us. We will block that key and generate a new one for you.

Chromium open-source components’ licenses

Fuzio is based on the open-source Chromium project that includes the source code and libraries written by developers in the Chromium community. The project also includes a number of open-source third-party libraries.

Fuzio is using Blink, FFmpeg, libsecret, and Wayland Protocols KDE components, supplied under LGPL. Learn more about Fuzio Compliance with LGPL.

One of the key questions arising when an open-source code is used in commercial products, is the permitted use of the open-source code, and possible restrictions of use and distribution of the works based on this open-source code.

We are performing a regular review of the licenses, associated with the Chromium components used by Fuzio, to make sure that there are no terms that would restrict the commercial distribution of Fuzio or the customer applications using it. We also make sure that licenses requiring disclosure of the source code (like GPL) do not apply to Fuzio or applications based on it.

Please see below the links to Chromium components’ licenses associated with Fuzio releases:

Chromium 145.0.7632.46 Licenses (2026.0.0)
Chromium 147.0.7727.56 Licenses (2026.1.0)

If you have any questions, not covered by this article, please contact us.

Design

Versioning