> ## Documentation Index
> Fetch the complete documentation index at: https://docs.strata.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Installation

> [!NOTE]
>
> **Console terminology:** In the Maverics Console, Orchestrator instances and
> configuration delivery are managed through **Deployments**. When working directly
> with YAML, configuration is managed as files delivered via the `-config` flag or
> `MAVERICS_CONFIG` environment variable.

## System Requirements

Before installing the Orchestrator, ensure your environment meets the minimum requirements for your chosen deployment method.

### Hardware

* **CPU** -- 2+ cores recommended for production workloads
* **Memory** -- 1 GB minimum
* **Disk** -- 100 MB for the binary, additional space for cache. 1 GB recommended as a starting point

### Supported Operating Systems

| OS | Version | Architecture |
| - | - | - |
| RHEL | 8+, 9+ | amd64 |
| Ubuntu | 22+ | amd64 |
| Debian | 12+ | amd64 |
| Windows | Server 2019, 2022, 2025 | amd64 |
| macOS (development only) | 26+ | arm64 |

### Network and Access

* **Port** -- 443 (HTTPS)
* **Network** -- Outbound HTTPS access from the Orchestrator host to your chosen cloud identity system
* **TLS** -- Valid TLS certificates for production deployments
* **Access** -- Root or administrator access required for installation and configuration

## Download the Orchestrator

All Orchestrator downloads are available through the **Maverics Console** at [maverics.strata.io](https://maverics.strata.io). Downloads are accessed from within a **Deployment** -- open any Deployment and use the **Download Orchestrator Software** modal.

> [!NOTE]
>
> The download experience is currently located inside Deployments rather than in the main Console navigation. To access the download modal, create or open a Deployment, then look for the download option in the Deployment detail view.

### Platform Installers

Platform installers are production-ready packages for deploying the Orchestrator to your infrastructure. The latest version is **v2026.02.1** (released February 5, 2026).

The Orchestrator is a stateless service that can be deployed on Linux, Windows, Docker, and optionally run on Kubernetes.

| Platform | File | Notes |
| - | - | - |
| Windows | `maverics-orchestrator.msi` | Registers as a Windows service with guided setup for configuration source, TLS certificates, and environment variables |
| macOS | `maverics-orchestrator.zip` | Standalone binary archive — development and testing only, not for production |
| Red Hat | `maverics-rhlinux.rpm` | RPM package for RHEL-based distributions |
| Ubuntu / Debian | `maverics-package.deb` | DEB package for Debian-based distributions |
| Docker | `maverics-orchestrator.tar` | Pre-built container image (load with `docker load`) |

> [!NOTE]
>
> **FIPS 140-3 Builds** -- The Orchestrator offers FIPS-compliant builds using a FIPS 140-3 validated cryptographic module. See [FIPS 140-3 Builds](/reference/orchestrator/installation/fips) for current status, feature details, and availability.

### Other Resources

| Resource | File | Description |
| - | - | - |
| Windows Client Authenticator App | `WindowsClientAuthenticatorAppforMaveric.exe` | Desktop authenticator application for Windows environments |

The Windows Client Authenticator App is also available from the Console download modal.

## Deployment Guides

> **[Programmatic Install](/reference/orchestrator/installation/programmatic)**
>
> Download Orchestrator packages from Artifactory for CI/CD pipelines

> **[Linux, macOS & Windows](/reference/orchestrator/installation/linux-macos-windows)**
>
> Platform-specific installation using RPM, DEB, MSI, or standalone binary

> **[Docker](/reference/orchestrator/installation/docker)**
>
> Load and run the Orchestrator as a container

> **[Kubernetes (Helm)](/reference/orchestrator/installation/kubernetes)**
>
> Deploy to Kubernetes using the official Strata Helm chart

## CLI Flags

The `maverics` binary accepts the following flags. All flags use single-dash format (Go `flag` package convention).

| Flag | Type | Default | Description |
| - | - | - | - |
| `-config` | string | `/etc/maverics/maverics.yaml` | Configuration file path |
| `-secretProvider` | string | -- | Secret provider URL (e.g., `hashivault://vault.example.com/secret/data/maverics`) |
| `-version` | bool | false | Print the Maverics version and exit |
| `-verbose` | bool | false | Enable verbose (DEBUG) logging |

**Precedence:** CLI flag > environment variable > default value. For example, `-config /path/to/config.yaml` overrides the `MAVERICS_CONFIG` environment variable, which overrides the default path.

## Environment Variables

Environment variables provide an alternative to CLI flags for configuring the Orchestrator. This is particularly useful in containerized deployments where flags may not be practical.

| Variable | Purpose | Default |
| - | - | - |
| `MAVERICS_CONFIG` | Config file path (alternative to `-config` flag) | -- |
| `MAVERICS_SECRET_PROVIDER` | Secret provider URL | -- |
| `MAVERICS_DEBUG_MODE` | Enable DEBUG logging (`true`/`false`) | -- |
| `MAVERICS_HTTP_ADDRESS` | Override HTTP server bind address | -- |

## Post-Installation Verification

After installation, verify the Orchestrator is installed correctly and can start successfully.

```bash theme={null}
# Verify the binary is installed
maverics -version

# Start with a config file
maverics -config /etc/maverics/maverics.yaml

# Check the health endpoint (in another terminal)
curl -s https://localhost:9443/status
# Expected: {"status": "up"}
```

The health endpoint at `/status` returns a JSON response indicating the Orchestrator is running. The default listen address is `0.0.0.0:9443`, configurable via the `http.address` setting in your YAML configuration.

> [!NOTE]
>
> On Linux, the Orchestrator runs as user `maverics` under `systemd`.

## Related Pages

> **[Configuration](/reference/orchestrator/configuration)**
>
> Configure the Orchestrator after installation

> **[Getting Started](/introduction/getting-started)**
>
> End-to-end quick-start guide