Enterprise Features

Some features of Sakuli require an enterprise license. Please consult our overview to see and request packages and prices. After you registered for an enterprise subscription, you will get a license-key and an NPM access token which are required to use enterprise features.

Using NPM-Token

All enterprise plugins are published on NPM. In contrast to the core packages they are not publicly accessible. Therefore you need the provided access token in order to install these packages into your Sakuli projects. The easiest way is to add the token in a .npmrc-file in the root of your project directory:

# cd to/your/project
echo "//registry.npmjs.org/:_authToken=<PERSONAL-TOKEN>" >> .npmrc

This command will create an .npmrc file with the neccessary token configuration. Every upcoming npm install will use this configuration. If you dont like to save the token in a file (because this file might be shared) you can configure it to use an environment variable:

echo "//registry.npmjs.org/:_authToken=\${NPM_TOKEN}" >> .npmrc

In this case you have to provide the token via an environemnt variable NPM_TOKEN or set it per installation of an enterprise package:


It is usually not necessary to persist the token since you will seldomly run npm install that often. If it is required to set the token permanently on a system consult the official npm guid for CI/CD integration (even useful outside CI/CD contexts).

Using the License-Key

The license-key contains information about your subscription which will be checked by enterprise components before they are executed. In order to provide this information to Sakuli you also have to set the license-key as an environment variable. Because the license-key is read on every single test execution it is useful to store it persistently on your system or set it in a script where the actual test is also called.

The name of the environment variable for the license-key is SAKULI_LICENSE_KEY.

Environment Variables

An environment variable is a dynamic-named value that can affect the way running processes will behave on a computer.

They are part of the environment in which a process runs. For example, a running process can query the value of the TEMP environment variable to discover a suitable location to store temporary files, or the HOME or USERPROFILE variable to find the directory structure owned by the user running the process.

- Wikipedia, 08/2019

So basically an environment variable is just a simple key-value pair provided to a certain process e.g. VAR_NAME=VALUE. They can be set for each process or system-wide - so that they become accessible for each upcoming process.

The approach for integrating an environment variable depends on the respective operating system.

On Windows

To set an environment variable on Windows you have to:

  • Open Start-Menu and type env into the search mask
    • An entry ‘Edit the system environment variables’ should appear (click on it)
  • After the System Properties dialog showed up
    • Go to the Advanced tab
    • Click on the button Environment Variables (at the bottom of the dialog)
  • You should see two tables including Variable and Value columns for User Variables and System variables

There you can set, edit or delete environment variables permanently on your system (it is recommended to edit the system variables table if possible). A more detailed guide can be found here

Alternatively you can use Rapid Environemnt Editor which is a nice tool for editing environment variables on Windows.

In case of a more restrictive environment - where it is not possible to edit environment variables that easily - you can set them in a batch script:


sakuli run .

On Linux or OSX

On Linux or OSX it is usually a file which sets up the environment for certain processes.

  • ~/.bashrc on Linux
  • ~/.profile on OSX

These files can be edited with every text editor to add, edit or remove environment variables. An environment variable is defined by:


A new variable can be added with the command:

echo "export VARIABLE_NAME=VALUE" >> ~/.bashrc  # Linux
echo "export VARIABLE_NAME=VALUE" >> ~/.profile # OSX