Skip to main content
This page provides the official version mapping between Helm chart versions and application versions. Use it as a reference before deploying or upgrading your environment.
Looking for upgrade instructions? Check the Upgrading Helm guide for step-by-step procedures.

Source of truth


The official and most up-to-date version matrix is maintained in the Helm repository README. This matrix is automatically updated whenever applications have a new release, ensuring it always reflects the latest compatibility information. The tables on this page are provided for quick reference, but always check the Helm repository for the most current versions.
Always update the Helm chart when updating applications. The Helm chart version and application versions are tightly coupled. Updating an application (like Midaz) without updating its corresponding Helm chart can cause deployment failures.Exception: Some hotfixes may not require a Helm chart update. Check the release notes for specific guidance.

Versioning scheme


Lerian uses a prefixed semantic versioning scheme for Helm charts:
{component}-v{MAJOR}.{MINOR}.{PATCH}[-{prerelease}]
Examples:
  • midaz-v4.4.8 - Midaz Helm chart version 4.4.8
  • plugin-crm-v3.2.1 - CRM plugin chart version 3.2.1
  • plugin-br-pix-direct-jd-v1.3.0-beta.1 - Pix plugin beta release
The Chart version refers to the Helm chart package version. The App version refers to the actual application container image version deployed by the chart.

Midaz core


The main Midaz Helm chart deploys core services. Starting from chart v5.x, a unified Ledger service is available that combines Onboarding and Transaction functionality.
Chart versionLedgerCRMOnboardingTransaction
5.7.03.5.33.5.33.5.33.5.3
5.3.03.5.13.5.13.5.13.5.1
4.4.8--3.4.43.4.7
4.3.4--3.4.33.4.6
4.0.0--3.0.03.0.0
Starting from chart v5.x, the Ledger service is the recommended deployment option, combining Onboarding and Transaction into a single service. The CRM backend is also included in the main Midaz chart (enabled via crm.enabled: true). See the Upgrading Helm guide for migration details.For the complete version history, check the Helm repository tags.

Plugins


Plugins are deployed as separate Helm charts with independent versioning. Each plugin requires a valid Enterprise license.

CRM

The standalone plugin-crm chart includes a UI component and remains compatible with both chart v4.x and v5.x deployments.
Chart versionBackendUIMidaz Helm chart compatibility
4.0.03.5.12.0.0v4.x, v5.x
3.2.12.0.02.0.0v3.x, v4.x
3.1.02.0.02.0.0v3.x, v4.x

Fees Engine

Chart versionBackendUIMidaz Helm chart compatibility
4.1.23.0.83.0.0v3.x, v4.x, v5.x
3.5.13.0.53.0.0v3.x, v4.x, v5.x
3.4.73.0.33.0.0v3.x, v4.x
Fees Engine is only available for Midaz v3 and later. It is not compatible with Midaz v2.

Pix

Chart versionPixJobMidaz Helm chart compatibility
1.2.61.2.1-beta.111.2.1-beta.11v3.x, v4.x, v5.x
The Pix plugin is still under development.

These products have their own Helm charts and are not Midaz plugins.

Reporter

Reporter is a standalone product for generating reports from Midaz data.
Chart versionManagerWorker
2.0.01.1.11.1.1
1.1.74.0.04.0.0

Access Manager (shared service)

Access Manager provides authentication and identity services shared across Lerian products.
Chart versionappVersionAuthIdentity
6.0.02.3.02.4.42.1.1
5.2.2-2.4.42.1.1
4.0.0-2.2.02.0.0

Product Console

Product Console provides the unified visual interface for Lerian products.
Chart versionConsole
2.0.11.5.0
1.0.01.0.0

OTEL Collector Lerian

OpenTelemetry Collector configured for Lerian’s observability stack.
Chart versionOTEL
2.2.12.1.0

Infrastructure dependencies


The following table lists the minimum required versions for infrastructure components when using the latest Midaz Helm chart.
DependencyMinimum versionNotes
Kubernetes1.20+1.30+ recommended
Helm CLI3.8+Required for OCI registry
PostgreSQL16.3Primary database
MongoDB16.4.0Document storage
RabbitMQ2.1.11Message broker
Valkey2.4.7In-memory cache (Redis fork)
OTEL Collector2.2.1Optional, for observability

Version compatibility rules


Follow these guidelines to ensure a stable deployment:
  • Upgrade Midaz Core first — Always upgrade the main Midaz Helm chart before upgrading any plugins. Plugins depend on Midaz Core APIs.
  • Check plugin compatibility — Before upgrading a plugin, verify it’s compatible with your current Midaz version using the tables above.
  • Test in staging — Always test new version combinations in a staging environment before deploying to production.
  • Review breaking changes — Check the Upgrading Helm guide for breaking changes between major versions.

Helm chart repository


All Lerian Helm charts are available from the OCI registry:
# Midaz Core
oci://registry-1.docker.io/lerianstudio/midaz-helm

# Plugins and other products
oci://registry-1.docker.io/lerianstudio/plugin-crm
oci://registry-1.docker.io/lerianstudio/plugin-fees-helm
oci://registry-1.docker.io/lerianstudio/plugin-br-pix-direct-jd
oci://registry-1.docker.io/lerianstudio/plugin-br-pix-indirect-btg-helm
oci://registry-1.docker.io/lerianstudio/plugin-br-bank-transfer-helm
oci://registry-1.docker.io/lerianstudio/reporter
oci://registry-1.docker.io/lerianstudio/plugin-access-manager
oci://registry-1.docker.io/lerianstudio/fetcher-helm
oci://registry-1.docker.io/lerianstudio/flowker-helm
oci://registry-1.docker.io/lerianstudio/tracer-helm
oci://registry-1.docker.io/lerianstudio/underwriter-helm

Pix Indirect (BTG)

Chart versionappVersion
2.1.11.5.1

Bank Transfer

Chart versionappVersion
1.1.02.1.0

Fetcher

Chart versionappVersion
2.0.31.2.0

Flowker

Chart versionappVersion
1.0.01.0.0

Tracer

Chart versionappVersion
1.0.01.0.0

Underwriter

Chart versionappVersion
1.0.11.0.0
For source code and detailed chart documentation, visit the GitHub repository.