Skip to main content
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

​
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. Downloads are accessed from within a Deployment — open any Deployment and use the Download Orchestrator Software modal.
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.
FIPS 140-3 Builds — The Orchestrator offers experimental FIPS-compliant builds using a FIPS 140-3 validated cryptographic module. See FIPS 140-3 Builds for current status, feature details, and availability.

​
Other Resources

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

​
Deployment Guides

Programmatic Install

Download Orchestrator packages from Artifactory for CI/CD pipelines

Linux, macOS & Windows

Platform-specific installation using RPM, DEB, MSI, or standalone binary

Docker

Load and run the Orchestrator as a container

Kubernetes (Helm)

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

​
Post-Installation Verification

After installation, verify the Orchestrator is installed correctly and can start successfully.
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.
On Linux, the Orchestrator runs as user maverics under systemd.

Configuration

Configure the Orchestrator after installation

Getting Started

End-to-end quick-start guide