Skip to content
JacqOS
Request beta access

Installation

Private Beta Distribution

Section titled “Private Beta Distribution”

JacqOS Studio, the CLI, and Cloud organization access are currently distributed through the private beta. Public download links and self-service account signup are paused.

Request beta access

Private beta access is reviewed by the JacqOS team.

Accepted beta teams receive installation and access instructions for the exact release they are evaluating. Those instructions include the package location, release identity, integrity metadata, supported platform, and the organization or workspace to use during onboarding.

What The Beta Package Includes

Section titled “What The Beta Package Includes”

Depending on the evaluation path, the team may provide:

  • JacqOS Studio for macOS — the native review surface for facts, proposals, blocked effects, provenance, replay, and verification evidence.
  • The JacqOS CLI — the scriptable path for scaffolding, replay, verification, evidence export, and approved Cloud workflows.
  • Curated example workspaces — deterministic and live scenarios matched to the beta release.
  • Organization access — an approved Cloud scope for evaluations that need hosted publishing or runtime evidence.

The access email is the authority for which surfaces are included in a given beta evaluation. A Studio package does not by itself imply Cloud organization access, and an approved Cloud organization does not imply unrestricted runtime capabilities.

Supported Evaluation Environments

Section titled “Supported Evaluation Environments”
  • macOS 13 or later on Apple Silicon for the native Studio path.
  • Linux x86_64 or arm64 for approved CLI evaluations.
  • Windows x86_64 when the current beta release includes the Windows CLI path.

Exact availability can change between beta releases. Include your required platforms in the access request so the team can confirm the right path before onboarding.

Verify What You Received

Section titled “Verify What You Received”

Use the release identity and integrity metadata supplied with your beta invite. After installation, confirm that the local version matches the approved release:

Terminal window
jacqos --version

Do not substitute an older package or a release URL from another evaluation. Studio, CLI, example workspaces, and Cloud capabilities are tested as a matched release surface.

Section titled “What To Read Next”
  • Getting Started — prepare the workflow and refusal condition for your beta request.
  • Studio Demo — preview the first guided blocked-action walkthrough.
  • Trust — review the boundary, evidence, and operational limits.

If you do not yet have an approved release, request private beta access.