> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/10.2-install/pentaho-installation-overview-cp/acquire-and-install-enterprise-licenses.md).

# Acquire and install enterprise licenses

To use Pentaho products, you must acquire and install enterprise licenses that can be verified with a license server.

Consider whether the following situations apply to your environment:

* If you cannot use a cloud or local license server in your environment, please review alternatives with your Pentaho representative. You might incur additional charges for manual audits.
* If you are upgrading from any previous 10.x version to Pentaho 10.2, then additional entitlements might be required. Please contact your customer support representative for details.
* If you are an existing customer wanting to upgrade from Pentaho 9.x or earlier supported versions, do not start the server before upgrading the licenses. You must install the new version of the product before activating the licenses.

Complete the following steps to acquire and install enterprise licenses:

1. Contact the Pentaho Sales team to purchase enterprise licenses for Pentaho products.

   After you purchase your Pentaho enterprise licenses, you receive an email with and activation ID or cloud license server information that can be used to unlock the product.

   **Note:** The activation ID is used only for a trial license. For information about a trial license see **Acquire a trial license** in the **Try Pentaho Data Integration and Analytics** guide.
2. Choose the type of license server to use for verifying Pentaho product licenses.
   * If you do not have security restrictions that prevent you from accessing a cloud license server, use the Pentaho cloud license server.
   * If you cannot use the Pentaho cloud license server, install a local license server behind your firewall to use for verifying licenses. For instructions on installing a local license server, see [Install a local license server on Linux](/install/10.2-install/pentaho-installation-overview-cp/acquire-and-install-enterprise-licenses/install-and-manage-a-local-license-server/install-a-local-license-server-linux.md).

     **Note:** If your environment has security restrictions that prevent the license server from reaching the back office URL, use offline activation. See [Activate offline entitlements for a local license server](/install/10.2-install/pentaho-installation-overview-cp/acquire-and-install-enterprise-licenses/install-and-manage-a-local-license-server/activate-offline-entitlements-for-a-local-license-server.md).
3. Install Pentaho product licenses.

   For instructions on installing licenses, see [Install licenses using PUC](https://github.com/pentaho/documentation/blob/main/PDIA/10.2/Install/Pentaho%20installation/Pentaho%20Installation%20\(overview%20cp\)/Acquire%20and%20install%20enterprise%20licenses/Install%20licenses%20using%20PUC=GUID-BBFF7838-ED4A-4252-803F-A90041648CA8=5=en=.md) or [Install licenses using the PDI client](/install/10.2-install/pentaho-installation-overview-cp/acquire-and-install-enterprise-licenses/install-licenses-using-the-pdi-client.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/install/10.2-install/pentaho-installation-overview-cp/acquire-and-install-enterprise-licenses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.