> ## 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.
# Overview
> Orchestrate the full lifecycle of Lerian applications in customer-owned infrastructure with native Helm Chart and Kubernetes integration.
The **Lifecycle Management** is built on the [Distr platform](https://distr.sh/docs/getting-started/what-is-distr/) to orchestrate the full lifecycle of Lerian applications in customer-owned infrastructure. Whether you're running in a private cloud, on-premises, or a hybrid setup, this tool gives your team direct access to our official **Helm Charts**, enabling fast, secure, and self-managed deployments.
With native Kubernetes integration and enterprise-grade security, this tool is the foundation for reliable, scalable, and compliant operations in any environment.
Lifecycle Management is the operational backbone of the [BYOC deployment model](/en/deployment-models). If you're using the **SaaS** model, Lerian handles deployment and lifecycle operations for you — this tool is not required.
## Why use Lifecycle Management?
***
Lifecycle Management is built to support the realities of modern infrastructure:
* **Bring Your Own Cluster (BYOC)**: Run Lerian in customer-managed Kubernetes environments.
* **Token-protected distribution**: Secure access to Helm repositories and OCI images.
* **Operational visibility**: Monitor deployed versions and system health in real time.
* **Full autonomy**: Take full control over installations, upgrades, and rollbacks.
### Key features
#### Deploy in your infrastructure
Install Lerian services in environments you fully control, whether on-premises, in a private cloud, or in a hybrid setup. The plugin is built to meet strict compliance, data protection, and security standards.
#### Integrated with Kubernetes
Our applications are packaged as OCI images and Helm Charts, so you can use standard Kubernetes tools to deploy, configure, and operate your services.
#### Secure by default
All artifact access is token-protected. Only authenticated users can retrieve Helm Charts and container images, ensuring deployment integrity.
#### Visibility without compromise
Our support team can remotely monitor your deployment without infringing on your autonomy. We track:
* Deployed versions.
* Health and availability signals.
* Compatibility with supported releases.
### Total lifecycle control
Manage your entire deployment workflow using the dashboard or native Kubernetes tools:
* Install new environments.
* Apply upgrades and patches.
* Roll back to a previous version.
* Pin a version as needed.
### Standardized, zero-friction updates
Our update pipeline ensures you can adopt the latest versions quickly, with minimal disruption to your production environment.
## Accessing the Lifecycle dashboard
***
The Lifecycle dashboard is available to **Enterprise BYOC** customers only. Community users manage deployments directly using Helm Charts and the documentation. If you’re on the SaaS model, Lerian handles deployment for you.
Before you can install Lerian applications, you’ll need access to the Lifecycle dashboard. This is where you’ll create deployments, configure agents, and manage your environments.
To get started:
Send a valid **company email** to the **Implementation Team,** or via email to [suporte@lerian.studio](mailto:suporte@lerian.studio).
We'll register your email and trigger an invite from the platform.
Check your inbox and follow the invitation link.
Create your password to activate your account.
Log in at [https://lifecycle.lerian.studio/](https://lifecycle.lerian.studio/) and begin managing your deployments.
These steps give you access to the dashboard. The actual plugin installation starts when you create a deployment and install the agent in your Kubernetes cluster.
## Installation guide
***
Once you have dashboard access, follow these steps to install and configure the Lerian product you want to deploy.
### 1. Access the Lifecycle Management dashboard
Go to [https://lifecycle.lerian.studio/login](https://lifecycle.lerian.studio/login) and log in with your credentials.
### 2. Create a new deployment
In the navigation bar, click Deployments.
* If you don't have any deployments yet, the **Install a new Agent** window appears automatically.
* Otherwise, click **+ New Agent.**
Select **Kubernetes via Helm Chart**.
Fill in the **Agent Name** and the **Kubernetes Namespace**.
Make sure **Enable cluster-scope permissions** is not enabled.
Click Continue .
### 3. Install the agent in your cluster
After selecting the agent type, the following screen shows a custom `kubectl` command for your deployment.
#### 3.1. Before running the command:
Check if the namespace exists:
```
kubectl get namespace
```
If it doesn't exist, create it:
```
kubectl create namespace midaz
```
#### 3.2. Copy the Helm install command from the install new Agent window.
It typically looks like this, but with your unique token and environment:
```
kubectl apply -n midaz -f "https://app.distr.sh/api/v1/connect?targetId=115c891b-89da-46bb-ac22-b13f507dcf5d&targetSecret=40767acb4e78974d445df26db1b3c642"
```
Always copy the command exactly as shown in the UI. It includes deployment-specific values.
#### 3.3. Run the command in your terminal.
Use a terminal connected to your Kubernetes cluster and run the following command:
```
kubectl apply -n midaz -f "https://app.distr.sh/api/v1/connect?targetId=115c891b-89da-46bb-ac22-b13f507dcf5d&targetSecret=40767acb4e78974d445df26db1b3c642"
```
#### 3.4. Confirm that the agent was installed
To verify the agent was successfully installed:
```
kubectl get pods -n midaz
```
You should see a pod named `distr-agent-xxxxx` with the status Running.
#### 3.5. Click the Continue button in the Install a new Agent window.
### 4. Configure your application
Select the application you want to deploy and the version.
The Helm values will be displayed automatically. You can use the **Helm values** section to apply environment-specific configuration, like:
* Replica counts.
* Secrets and environment variables.
* Domain and ingress settings.
**Never** use the Helm default information. It is example information and should never be used in production environment.
It is recommended that after you define your secrets and variables to use in Helm, **save a copy of your defined secrets in your secrets manager service**.
### 5. Monitor your deployment
You can track the status in two ways:
* In your Kubernetes cluster, using kubectl or your preferred dashboard.
* In the Lifecycle dashboard, with a centralized view of agent status and deployed versions.
For detailed Helm agent configuration and advanced capabilities, refer to the official Distr documentation: [Onboarding a Helm App](https://distr.sh/docs/guides/onboarding-a-helm-app/#creating-a-new-deployment)