Skip to main content

Installation

Get access​

Ogoron is distributed to customers directly.

Repository access for the CLI is granted per organization.

The repository token is issued in the personal cabinet of the organization owner or another organization member who manages billing/access for that organization:

Prerequisites​

  • Access to the Ogoron releases page via the personal cabinet
  • Git (recommended for CI/CD and for working with feature branches)
  • OGORON_REPO_TOKEN for your organization
  • For BYOK trial access only: OGORON_LLM_API_KEY

Install (CLI installer)​

Download the installer for your platform from the personal cabinet:

The cabinet links to the current Ogoron releases page where platform-specific installer artifacts are published.

Windows​

  1. Download the Windows installer executable from the releases page.
  2. Open PowerShell in the download directory.
  3. Run the installer:
.\ogoron-installer-windows-amd64.exe
  1. Verify:
ogoron --version
ogoron --help

Linux​

  1. Download the Linux installer from the releases page.
  2. Open a terminal in the download directory.
  3. Make it executable and run it:
chmod +x ./ogoron-installer-linux-amd64
./ogoron-installer-linux-amd64
  1. Verify:
ogoron --version
ogoron --help

On Linux, the installer places the runtime under the user-local Ogoron directory and creates a launcher in the user-local binary directory. If the launcher directory is not yet in PATH, the installer prints the exact path to add.

Run with Docker​

Ogoron can be distributed as a container image that runs the same CLI.

Recommended pattern: mount your repository and run Ogoron inside it.

docker run --rm \
  -e OGORON_REPO_TOKEN="$OGORON_REPO_TOKEN" \
  -v "$PWD:/repo" \
  -w /repo \
  "$OGORON_IMAGE" \
  ogoron --version

OGORON_IMAGE is provided during onboarding.

Configure repository access​

Ogoron reads the repository token from:

  1. OGORON_REPO_TOKEN
  2. OGORON_KEY (legacy alias)

It can also load environment values from a .env file in the current working directory.

Recommended: set OGORON_REPO_TOKEN in CI secrets and in your local shell profile.

BYOK trial only​

If your organization is on a BYOK trial, also set the LLM API key:

  1. OGORON_LLM_API_KEY

Recommended: set OGORON_LLM_API_KEY in CI and local shell profiles so the Ogoron-specific intent is explicit.

Update​

If you use the installer distribution, update with:

ogoron self update

If you use a container image, update by pulling a newer image tag.