Install

Install

How you get the software. Qualified preview components are available through individually approved evaluations, as signed artifacts. General public distribution is not currently offered. Signing in establishes your account; evaluation access requires individual approval. Once approved, your evaluation workspace is created and the 30-day evaluation period begins. Nothing downloads until you ask for it. Public npm is not a supported distribution channel for Aarmos product or runtime packages. The open AVAR verification and conformance packages are the supported public npm surface, so anyone can check a receipt without our software.

  1. 1Sign in. Sign in and request evaluation access. Once approved, your evaluation workspace is created and the 30-day evaluation period begins.
  2. 2Choose. Acquisition follows need — the software is fetched when you decide to install it.
  3. 3Acquire. Download the signed artifact at a fixed version from your approved evaluation.
  4. 4Verify. Check the artifact digest and signature before you install or run it.
  5. 5Associate. Associate the CLI with your workspace from the device you will run on.Not currently offered — linking a device to your workspace remains held.
  6. 6Ready. Continue to the Evaluation walkthrough when the installed artifact is ready.

What you receive

Once access opens: a built, scanned, signed artifact at a fixed version — never a source tree. Each release has a recorded digest you can check against what you installed. Artifacts are immutable: a change to the implementation means a new version, never a silent patch of one you already hold.

Get the CLI

There is no public download. Sign in, then open Evaluation downloads to acquire the signed CLI artifact once your evaluation is approved. Qualified preview components are available through individually approved evaluations. General public distribution is not currently offered. A signed Aarmos CLI release is not currently available for public download on Windows, macOS or Linux. Installation has been technically tested on all three platforms using unsigned qualification builds. The complete installed approval workflow has been qualified on Linux. After download, check the published digest and signature, then install it. Associating an installation with your workspace, shown below, is not currently offered:

aarmos login         # associate this installation with your workspace
aarmos --version
aarmos status

You do not need Node.js or npm to run the CLI artifact. Public npm is not a supported distribution channel for Aarmos product or runtime packages. The open AVAR verification and conformance packages are the supported public npm surface.

Container image

docker run --rm \
  -v aarmos-state:/var/lib/aarmos/state \
  -v aarmos-evidence:/var/lib/aarmos/evidence \
  aarmos/runtime:<version> serve

A standards-compliant OCI image — the same runtime, packaged differently. It runs under Docker, Podman, containerd and Kubernetes with no separate build. It runs as a non-root user, supports a read-only root filesystem, and keeps state, secrets and evidence on separate mounts. The runtime container is available as a signed archive through individually approved evaluations; it is not published to a public registry.

Independent verification (optional)

You do not need this to run your first governed action. When you later want to check a record without trusting us, use the in-browser verifier or the open @avar-standard/verify library on public npm (Apache-2.0).

Next: evaluate one governed consequence

Installation ends when the CLI is verified, installed, and associated with your workspace. Continue with the Evaluation walkthrough to configure one supported path, run one governed consequence, inspect its evidence, and verify the result.