Managing Licensing

How to manage your on-premises licensing for Monolith

Where your license is managed

Currently, your on-premises license to Monolith is managed within the ".env" file that is within your Monolith package deployment folder.

There are two values within the ".env" file that related to your Monolith License:

MONOLITH_LICENSE_KEY=
MONOLITH_LICENSE_TOKEN=

When the Monolith server starts up, it derives your license from one of these two values.

When both values are present, the MONOLITH_LICENSE_TOKEN value takes precedence.

Monolith License Token (Preferred - Offline Licensing)

The Monolith license token is a long string that is a securely signed token that contains your licensing information.

This method works in both online and offline environments and does not use the internet to operate.

The Monolith server derives your license details from this token.

This is the preferred method, because it does not rely on our licensing server to work and will keep your Monolith deployment operational even during internet outages.

A license token must be provided to you from Monolith support. These tokens expire on your annual renewal date and must be refreshed each year. Contact [e-mail] to get a new token.

Monolith License Key (Online Licensing)

The Monolith license key is a short, unique string that is associated with your Monolith customer account. Monolith uses this value to retrieve your licensing information from our online licensing server on the internet.

This licensing method will not work in air-gapped environments

Updating your license

To update your license, simply replace the License key or token value in your ".env" file with a new one and restart your Monolith Docker deployment.

You can restart your Monolith Docker deployment with the following commands:

docker compose down
docker compose up -d

Be sure to run these commands from the same directory as your ".env" file and "docker-compose.yml" file