> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Version compatibility

> Check which plugin versions match each Midaz Core release before deploying or upgrading your environment.

By checking the table below before installing or upgrading, you ensure that **plugin deployments** remain aligned with your **Midaz Core version**, reducing the risk of incompatibilities or unexpected behavior.

While most plugins have independent versioning, **CRM** follows a **shared release cycle** with Midaz Core, as it is maintained within the same repository.

## Compatibility table

***

| Plugin             | Midaz v2 Compatibility                            | Midaz v3 Compatibility                               | Notes                                                                |
| :----------------- | :------------------------------------------------ | :--------------------------------------------------- | :------------------------------------------------------------------- |
| **Access Manager** | <Icon icon="square-check" color="green" /> v1     | <Icon icon="square-check" color="green" /> v2        | Each Midaz version requires a specific plugin version                |
| **CRM**            | <Icon icon="square-check" color="green" /> v2.x.x | <Icon icon="square-check" color="green" /> v3.x.x    | Source-available, versioned together with Midaz, deployed separately |
| **Fees Engine**    | <Icon icon="xmark" color="red" /> Not supported   | <Icon icon="square-check" color="green" /> Supported | Only available starting from Midaz v3                                |

<Note>
  **Midaz v2.x.x** documentation is no longer available. If you're still using v2, we strongly recommend upgrading to **Midaz v3.x.x** to ensure full compatibility with **all** Lerian's products and plugins.
</Note>

## Upgrade recommendations

***

* Always upgrade **Midaz Core** first.
* **CRM** is versioned together with Midaz Core (for example, Midaz `v3.5.0` → CRM `v3.5.0`), but it is **deployed independently**.
* **Access Manager** and **Fees Engine** require explicit version alignment with Midaz.
* Always validate upgrades in a staging environment before production rollout.