Skip to main content
The Orchestrator is distributed as platform-specific packages downloadable from the Maverics Console. To download the installer for your platform, open any Deployment in the Console and use the Download Orchestrator Software modal. See Download the Orchestrator for details.

Linux

Red Hat / RHEL

Verify the RPM

Download Strata’s public GPG key:
Import the key into RPM:
Verify the key installation by running:
Verify the RPM:

Install the RPM

Install the RPM package on Red Hat Enterprise Linux and compatible distributions (CentOS, Rocky Linux, AlmaLinux):
This installs the Orchestrator binary to /usr/bin/maverics and creates a systemd service unit. Start the service and enable it to run on boot:
The default configuration file path is /etc/maverics/maverics.yaml. Place your configuration file at this path before starting the service, or update the service unit to point to a different location.

Ubuntu / Debian

Verify the DEB package

Download Strata’s public GPG key:
Import the key:
Verify the .deb.sig file:

Install the DEB package

Install the DEB package on Ubuntu, Debian, and compatible distributions:
This installs the Orchestrator binary and creates a systemd service unit. Start the service and enable it to run on boot:
The default configuration file path is /etc/maverics/maverics.yaml. Check the service status with:

macOS

The macOS distribution is for development and testing purposes only. It is not supported as a production platform.
Extract the standalone binary archive:
Run the Orchestrator directly, specifying your configuration file:
macOS does not have native systemd service integration. The binary runs in the foreground by default. For persistent background operation, you can manage the process with launchd by creating a launch daemon plist, or run it within a terminal multiplexer like tmux or screen.

Windows

Run the MSI installer (maverics-orchestrator.msi), which provides a guided setup wizard. The installer prompts you to configure:
  • Configuration source — Path to your YAML configuration file or a remote config source URL
  • TLS certificates — Paths to your certificate and private key files
  • Environment variables — Any runtime environment variables the Orchestrator needs
The installer registers the Orchestrator as a Windows service that starts automatically on boot. Manage the service from the command line:
Configuration is set during MSI installation and can be updated through the Windows Services management console (services.msc) or by modifying the service registry entries.

Installation Overview

System requirements, download options, CLI flags, and environment variables

Configuration

Configure the Orchestrator after installation

Getting Started

End-to-end quick-start guide