License
|
The automatic retrieval and monitoring options on this page aren’t yet released. They will be released with the next 6.4 release. Currently, you must manually enter your license. |
Magnolia DX Core requires a license to run. You receive a license key from Magnolia with your purchase. Magnolia can automatically retrieve and register the license at startup from several sources. Choose the option that best fits your security and environment requirements.
Additionally, you can provide the license manually through the UI. You must register the same license on both the author and public instances.
Editions and licenses
Magnolia on-premise is available in the following editions:
| Some modules have undergone licensing changes with Magnolia 6.3. See Old module packs, new extensions and Modules for more details. |
DX Core
DX Core is your core system for content and experience management. DX Core provides all the features you need for creation, management and delivery of personalized experience across the web and all your channels.
Each instance of DX Core requires a license.
Community Edition
Free, open-source GPLv3 license. The Community Edition has fewer features than DX Core and is limited to one receiver.
| Community Edition does not require a license key. |
Try it out
Try Magnolia CMS. You can try our Client Hosted or Cloud deployment. Download our open source community edition for free or apply for time-limited trials of our DX Core offers.
Buying a license
Contact us to buy a license for DX Core or your desired extension.
Requesting license key renewal
If your license key has expired, send a mail to info@magnolia-cms.com and request a new key.
Hello Magnolia,
Please send me a renewed license key.
- License owner's name:
- License owner's email address:
- Company name:
- Phone:
Thanks
Updating a license key
At startup, Magnolia attempts to register the license automatically using the following sources, in the order given.
The magnolia.license.location folder and default location ${magnolia.home}/license.key are monitored for file changes to provide a convenient way to update the license without manual intervention through the UI or restarting the application to reload it from a configuration (system properties, environment variables, etc.).
-
Using the
magnolia.license.keyproperty set via any configuration mechanism supported by Magnolia. That includes environment variables, system properties, and alsomagnolia.properties(or YAML) files.This respects standard Magnolia configuration precedence: system properties → environment variables → configuration files.
-
By providing a file via the
magnolia.license.locationproperty. This is suitable for managed secrets (for example, for Docker or Kubernetes), where you supply the license from container secrets. However, the property can point anywhere in your file system and refer to any file of your choice.This location is monitored for license key changes by default. -
Adding a file at the default location
${magnolia.home}/license.key.Supports embedding the license in the deployment image.
This location is monitored for license key changes by default. -
You can also manually update the key in the About app or in the Configuration app after installing Magnolia.
| If a license is already configured in the system, it’s overridden by sources 1 to 3 above. However, if a license isn’t registered automatically, the current license (if any) is left untouched. |
Manually entering a license
-
Open the About Magnolia app
-
Click Enter license info.
-
Enter the registered email address in the License owner field. If you requested a new license, ensure that you enter the same email address you used when requesting the license.
Email is case-sensitive. If you registered as John.Doe@example.comthenjohn.doe@example.comdoesn’t work. -
Enter the license key in the License data field.
If the About app isn’t installed or not working properly, you can update your license in the Configuration app.
Find the /modules/enterprise/license node and update the key property.
|
Security considerations
Using a system property or environment variable (magnolia.license.key) may expose the license in some environments:
-
The value can be visible in the About app’s configuration properties.
-
Anyone with access to the host may query a process environment’s variables or inspect command-line parameters.
When security considerations are a concern, it’s more secure to choose a file-based approach (magnolia.license.location or ${magnolia.home}/license.key) or use the former JCR-based injection via the Configuration app.
|