Skip to main content
Lerian provides Helm charts for infrastructure components that support the core platform. These charts handle telemetry collection, data synchronization, and transaction validation. Each is deployed independently with its own versioning.

​
Prerequisites

  • A running Midaz deployment (most infrastructure components connect to Midaz services).
  • Kubernetes 1.23+ for API compatibility and Helm 3.8+ for OCI registry support. Use a currently supported Kubernetes minor release in production. The Tracer chart enables HPA and PDB resources that require autoscaling/v2 and policy/v1.

​
OTEL Collector Lerian

OpenTelemetry Collector configured for Lerian’s observability stack. Collects, processes, and exports telemetry data from Lerian services. OCI registry:

​
Fetcher

Fetcher is Lerian’s internal data-extraction service. It’s required only in managed / multi-tenant deployments (FETCHER_ENABLED=true), where products like Reporter and Matcher use it to reach per-tenant data sources — deploy this chart alongside them in that case. Single-tenant, self-hosted deployments don’t require it: those products connect to their databases directly through datasource configuration. Fetcher runs behind the scenes and is never used as a standalone product. OCI registry:

​
Tracer

Tracer provides transaction validation, rule enforcement, and spending limit management for the Lerian platform. OCI registry:

​
Resources

For the full cross-product compatibility matrix, see Version compatibility.