> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/hypersim/licensing-reference/simulator-license.md).

# Simulator License

To run simulations on a simulator, a license must be installed on the simulator itself. Simulators are usually shipped with a license already pre-installed.

## **View the Simulator License Details**

To view the license information, [HYPERSIM must be installed on your workstation](https://www.opal-rt.com/docs/hypersim/get-started/download-and-install-hypersim.md), [connected to the simulator](https://www.opal-rt.com/docs/hypersim/get-started/configure-workstation-and-simulator-link.md), and the [simulator added to the **Targets** in HYPERSIM](https://www.opal-rt.com/docs/hypersim/get-started/configure-workstation-and-simulator-link/add-the-simulator-to-hypersim-targets.md).

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-0e4891cf9dff87519ca32f453d99fb79ae92c62d%2Fimage%20(822).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

1. In the **HYPERSIM** tab, left-click **Targets**.
2. Click the simulator’s **IP address** to expand its menu.
3. Select **License**.
4. Review the HYPERSIM License **Description** list.

License features can be either binary (true or false) or numeric, indicating the number of units available for that feature.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-fc3ac58fa7d8640cb169d8c0c9746789465d409f%2Fimage%20(823).png?alt=media" alt=""><figcaption></figcaption></figure>

The first line of the HYPERSIM License Description list shows the **End of software maintenance**. Just above the list, the **License Path** displays the location of the license file, whose name includes the **License Number** and the **simulator serial number**. Above the License Path, the license **Expiration Date** is indicated.

* The **Expiration Date** is set to *INFINITY*, unless a demo license is installed.
* The **End of Maintenance Date** indicates how long the simulator is covered by OPAL-RT Support and provides a general cutoff for compatible HYPERSIM versions.\
  For example, an **End of software maintenance** of *October 5, 2025* means that:
  * You can contact OPAL-RT Support through the [customer portal ](https://opal-rt.com/contact-technical-support/)until October 5, 2025.
  * HYPERSIM versions released in 2026 or later will not be supported with this license.

{% hint style="danger" %}
Long Term Support (LTS) versions of 2024.1 and 2024.4 continue to receive updates for customers under maintenance. Therefore, you may not be eligible to use these versions even if your maintenance extends beyond 2024, because new releases for these LTS branches are still being issued after 2024.
{% endhint %}

You can renew the Maintenance Contract by contacting your OPAL-RT representative.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/hypersim/licensing-reference/simulator-license.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
