> For the complete documentation index, see [llms.txt](https://academy.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pentaho.com/getting-started/start-here/enterprise-trial.md).

# Request an Enterprise trial

```mermaid
flowchart LR
    A["1 · Prepare"] --> B["2 · Submit the form<br/>on pentaho.com"] --> C["3 · AE review<br/>2–3 business days"] --> D["4 · Download<br/>and licence"] --> E["5 · Install and<br/>run workshops"]
    C -.->|meanwhile| L(["Browser lab"])

    classDef here fill:#D6001C,stroke:#D6001C,color:#FFFFFF,stroke-width:2px
    classDef todo fill:#EDEFF2,stroke:#C4CBD4,color:#37404D
    classDef offsite fill:#FFFFFF,stroke:#D6001C,stroke-width:2px,stroke-dasharray: 5 3,color:#37404D
    classDef aside fill:#3F4A56,stroke:#3F4A56,color:#FFFFFF
    class A here
    class B offsite
    class C,D,E todo
    class L aside
```

**The Enterprise Edition trial is the full product, with a named Pentaho account executive alongside you. Take this route if you're building a real proof of concept rather than learning the tool.**

{% hint style="info" icon="arrow-up-right-from-square" %}
**The request form lives on pentaho.com, not here.** You'll leave the Academy to fill it in and come back once your licence arrives. This page covers both halves — what to do before you go, and what to do when you're back.
{% endhint %}

***

## Before you go

{% stepper %}
{% step %}

#### Check this is the right route

The Enterprise trial is support-led. That's its strength and its cost: you get the full product and a person who knows it, but nothing happens for a couple of days.

Take a different route if you just want to look at PDI ([browser lab](https://academy.pentaho.com/getting-started/start-here/evaluate-online), two minutes) or learn it on your own machine ([Developer Edition](https://academy.pentaho.com/getting-started/start-here/developer-edition), fifteen minutes).

Take this one if you need enterprise features, your own data at real volume, or a trial period that matches an actual evaluation deadline.
{% endstep %}

{% step %}

#### Get these ready

The form is short, but two answers determine how well your trial goes. Have them straight before you start:

* **What you're trying to evaluate** — the specific thing you need to prove, not "we're looking at ETL tools." This is what your AE uses to size the trial and to bring in the right technical help.
* **Roughly when you need to decide** — this sets your trial length.
* **Your work email address.** Requests from personal addresses take longer to validate.
  {% endstep %}

{% step %}

#### Submit the form on pentaho.com

This opens pentaho.com in a new tab. Come back here once you've submitted — the rest of this page is what happens next.

<p align="center"><a href="https://pentaho.com/get-started/" class="button primary" data-icon="arrow-up-right-from-square">Request a trial on pentaho.com</a></p>

Choose the **trial** option rather than demo or sales — that's the one that routes to a support-led evaluation.

{% hint style="success" icon="bookmark" %}
**Bookmark this page before you go.** Your licence email will contain a download link, but not the install and workshop instructions. This is where you'll want to land when it arrives.
{% endhint %}
{% endstep %}
{% endstepper %}

***

## While you wait

Expect **2–3 business days**. Two things happen in that window: your request is assigned to an account executive in your region, and they validate it — confirming your organisation, the use case, and the trial length you need. You'll hear from a named person, not a no-reply address. If a detail is missing they'll ask rather than reject it.

Don't wait idly. Most people use the gap productively:

{% columns %}
{% column width="50%" %}
**Run a workshop now**

The browser lab needs nothing from you and starts in about two minutes. Work through your first PDI workshop while your request is being validated — it's the same workshop content you'll use in the trial.

<a href="https://academy.pentaho.com/getting-started/start-here/evaluate-online" class="button primary" data-icon="bolt">Open the 2-hour browser lab</a>
{% endcolumn %}

{% column width="50%" %}
**Get your environment ready**

* Decide which of your own data sources you want to connect to, and check you have credentials
* Confirm who else needs access to the trial environment
* Skim the installation guide so the install is quick when the link arrives

<a href="https://academy.pentaho.com/pentaho-11-installation-en" class="button secondary" data-icon="screwdriver-wrench">Installation guide</a>
{% endcolumn %}
{% endcolumns %}

***

## When your licence arrives

{% stepper %}
{% step %}

#### Download and apply your licence

Your AE sends a download URL and a licence key together.

|                  |                                                          |
| ---------------- | -------------------------------------------------------- |
| **Download URL** | Sent by your AE — specific to your trial, don't share it |
| **Licence key**  | Sent with the download link                              |
| **Trial length** | Agreed with your AE                                      |

Install the product first, then apply the licence:

{% tabs %}
{% tab title="Windows" %}

```powershell
cd \
cd Pentaho/design-tools/license-installer
./install_license.bat install C:\path\to\your-licence.lic
```

{% endtab %}

{% tab title="macOS / Linux" %}

```bash
cd ~/Pentaho/design-tools/license-installer
./install_license.sh install ~/path/to/your-licence.lic
```

{% endtab %}
{% endtabs %}

{% hint style="warning" icon="triangle-exclamation" %}
REPLACE-ME — confirm these licence installer paths and command syntax against Pentaho 11 before publishing.
{% endhint %}
{% endstep %}

{% step %}

#### Install

Enterprise Edition installs the Pentaho Server as well as the design tools, so it's a longer install than Developer Edition. Follow the full guide, then verify both components start.

{% tabs %}
{% tab title="Pentaho Server" %}
Windows:

```powershell
cd \
cd Pentaho/server/pentaho-server
./start-server.bat
```

Linux:

```bash
cd /opt/pentaho/pentaho-server
./start-server.sh
```

{% endtab %}

{% tab title="Data Integration" %}
Windows:

```powershell
cd \
cd Pentaho/design-tools/data-integration
./spoon.bat
```

Linux:

```bash
cd ~/Pentaho/design-tools/data-integration
./spoon.sh
```

{% endtab %}
{% endtabs %}

<a href="https://academy.pentaho.com/pentaho-11-installation-en" class="button primary" data-icon="screwdriver-wrench">Pentaho 11 installation guide</a>
{% endstep %}

{% step %}

#### Run the workshops

Enterprise workshops cover the server-side capability Developer Edition doesn't have — scheduling, enterprise security, and Pipeline Designer.

<a href="https://academy.pentaho.com/pentaho-data-integration" class="button secondary" data-icon="diagram-sankey">Data Integration</a>

<a href="https://academy.pentaho.com/pipeline-designer" class="button secondary" data-icon="arrow-progress">Pipeline Designer</a>
{% endstep %}

{% step %}

#### Check in with your AE

Your AE will follow up during the trial. That conversation is more useful if you bring specifics — which workshops you got through, what you connected to, and where you got stuck.

If you hit something blocking, contact them directly rather than waiting for the scheduled check-in. Extending or resetting a trial is straightforward while it's running.
{% endstep %}
{% endstepper %}

***

## If something goes wrong

{% hint style="warning" icon="life-ring" %}

<details>

<summary>I submitted the form and haven't heard anything</summary>

Allow 2–3 business days. Check your spam folder — the first email comes from a named person rather than a no-reply address, so it sometimes gets filtered. After three business days, email <REPLACE-ME@pentaho.com> with the address you used on the form.

</details>

<details>

<summary>I filled in the form but I'm not sure it was the right one</summary>

The pentaho.com form covers trials, demos, and sales enquiries. If you picked demo or sales by mistake you'll still hear from someone — mention that you want a support-led trial when they reply, and they'll route it.

</details>

<details>

<summary>My licence key isn't working</summary>

Check that the `.lic` file path in the install command is correct and that the file hasn't been altered by an email client. Run the installer's list command to see what's currently registered. If the key is rejected, reply to your AE's email — they can reissue it.

</details>

<details>

<summary>I need the trial extended</summary>

Ask your AE. Extensions during an active trial are routine, especially where the delay was on our side.

</details>

<details>

<summary>I just want to look at the product, not run an evaluation</summary>

Take the [browser lab](https://academy.pentaho.com/getting-started/start-here/evaluate-online) instead — two minutes, no form, no follow-up.

</details>
{% endhint %}

{% hint style="warning" icon="life-ring" %}
**Need help?**

Press <kbd>Ctrl</kbd> + <kbd>K</kbd> and click **Ask** to search every page on this site, or email <REPLACE-ME@pentaho.com>.

<button type="button" class="button primary" data-action="ask" data-icon="gitbook-assistant">Ask about this step...</button>
{% endhint %}

<p align="center"><a href="https://academy.pentaho.com/getting-started" class="button secondary" data-icon="arrow-left">Back to all three options</a></p>


---

# 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://academy.pentaho.com/getting-started/start-here/enterprise-trial.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.
