> ## 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.

# Installing Midaz via Helm

> Install Midaz on Kubernetes with the official Helm chart — Ledger, databases, and observability stack in a single command.

<Tip>
  **This page is intended for DevOps engineers and infrastructure teams.** It covers Kubernetes deployment configuration using Helm charts. If you're looking for a high-level understanding of Midaz's deployment options, see [SaaS and BYOC](/en/deployment-models).
</Tip>

This is the recommended way to deploy Midaz on Kubernetes. The Helm chart installs everything you need in a single command: the core Ledger service (or legacy Onboarding/Transaction), PostgreSQL, MongoDB, Valkey, RabbitMQ, and an optional observability stack (Grafana + OpenTelemetry).

<Warning>
  **Use the Ledger service for all new installations.** The separate Onboarding and Transaction services are supported for migration scenarios only and will be deprecated in a future release.
</Warning>

<Note>
  This guide covers Midaz Helm chart v5.x. For upgrading from previous versions, see [Upgrading Helm](/en/platform/helm/midaz/midaz-upgrade-guide).
</Note>

## What gets deployed

***

A default `helm install` deploys the following components:

* **Ledger** — Unified API service (port 3002) handling onboarding, transactions, and account management.
* **PostgreSQL** — Primary + replica for relational data storage (port 5432).
* **MongoDB** — Document store for audit logs and metadata (port 27017).
* **Valkey** — In-memory cache for session and balance data (port 6379).
* **RabbitMQ** — Message broker for async event processing (ports 5672/15672).
* **Grafana + OTEL LGTM** — Observability stack with dashboards, logs, traces, and metrics (port 3000, if enabled).

## Prerequisites

***

Before deploying Midaz with Helm, make sure you have:

* [**Kubernetes (v1.30+)**](https://kubernetes.io/releases/download/) – Running cluster.
* [**Helm 3+**](https://helm.sh/docs/intro/install/) – Installed and available (`helm version`).
* Access to a container registry with Midaz images.
* DNS and TLS certificates for ingress (or cert-manager installed).

<Note>
  The source code for this Helm chart is available at:

  * [midaz-helm](https://github.com/LerianStudio/helm/tree/main/charts/midaz)
  * [midaz](https://github.com/LerianStudio/midaz)

  The default installation matches the one provided in the [Midaz quick installation guide](https://github.com/LerianStudio/midaz?tab=readme-ov-file#quick-installation-guide-localhost).
</Note>

Want a deeper understanding of the architecture? Check the [Midaz architecture overview](/en/midaz/architecture).

## Install Midaz via Helm Chart

***

To install Midaz using Helm, run the following command:

```bash theme={null}
helm install midaz oci://registry-1.docker.io/lerianstudio/midaz-helm --version <version> -n midaz --create-namespace
```

Replace `<version>` with the desired Helm chart version. You can check available versions by running:

```bash theme={null}
helm search repo oci://registry-1.docker.io/lerianstudio/midaz-helm --versions
```

This creates a namespace called `midaz` (if it doesn't already exist) and deploys the chart.

<Tip>
  The Helm chart is in our [GitHub repository](https://github.com/LerianStudio/helm). You can fork it, customize values, or extend as needed.
</Tip>

## Verify the installation

***

After running the install command, verify that all pods are running:

```bash theme={null}
kubectl get pods -n midaz
kubectl get svc -n midaz
```

<Note>
  **Expected result:** You should see 5-7 pods in `Running` state (Ledger, PostgreSQL primary, PostgreSQL replica, MongoDB, Valkey, RabbitMQ, and optionally Grafana). All services should have `ClusterIP` endpoints assigned. If any pod is in `CrashLoopBackOff` or `Pending`, check the pod logs with `kubectl logs <pod-name> -n midaz`.
</Note>

To confirm the Helm release is tracked:

```bash theme={null}
helm list -n midaz
```

## Next steps

***

* [Configure ingress](/en/platform/helm/midaz/midaz-ingress) to expose Midaz services outside the cluster.
* [Configure observability](/en/platform/helm/midaz/midaz-observability) with Grafana and OpenTelemetry.
* [Configure dependencies](/en/platform/helm/midaz/midaz-dependencies) like PostgreSQL, MongoDB, RabbitMQ, and Valkey.
* [Components reference](/en/platform/helm/midaz/midaz-components-reference) for detailed Midaz service parameters.