# Installation

> Install Self-Hosted Deployment on-premises for the first time

You can deploy the solution on your own infrastructure using the vpctl command-line tool.

Unlike deployment in AWS and Azure, the process for deployment on premises uses the vpctl tool to manage the entire release lifecycle, from pulling releases and syncing container images to generating secrets and deploying Helm charts or ArgoCD applications.

> **Important:**
>
> Unity doesn't deliver on-premises installations directly. Your IT organization or solutions integrator performs the installation steps in the pages listed below and operates the deployment after rollout. For the full delivery model, refer to the [on-premises overview](..).

For the first installation, follow this workflow:

[Overview of the infrastructure](./infrastructure.md): Learn about the infrastructure requirements and what the deployment creates.
[Hardware requirements](./hardware-requirements.md): Plan the physical infrastructure for a baseline production deployment.
[1. Prerequisites](./prerequisites.md): Ensure that you have the required configuration, tooling, and permissions.
[2. Deployment](./deployment.md): Pull, configure, and deploy the solution using the vpctl tool.
[3. Postdeployment](./postdeployment.md): Perform the initial configuration of the identity subsystem and validate the deployment.
[vpctl reference](../../vpctl/_index): Use the vpctl command-line tool to deploy and manage on-premises releases. Includes command reference, manifest schema, architecture, and security guidance.
[Costs](./costs.md): Estimate the hardware investment and operating costs.