Orkeon installs on your machine, whatever your system.
The first trial then runs on a local model, with no API key. For a server, see the Deploy page.

Install the CLI
dotnet tool install -g Orkeon.Scripting.CliRequires the .NET 10 SDK. An .ork.ts script also requires esbuild (npm install -g esbuild); a YAML team does not.
sudo apt install orkeon orkeon-archive-keyringBefore the first install, add the signed source once.
Verify the archive’s checksum before extracting it:
shasum -a 256 --check --ignore-missing SHA256SUMSDownload the archive from the releases page (new tab): osx-arm64 for Apple Silicon, osx-x64 for Intel. The Homebrew formula is not published yet.
tar -xzf orkeon-cli-*-osx-arm64.tar.gz && cd orkeon-cli-*-osx-arm64 && ./install.shThe archive is neither signed with an Apple Developer ID nor notarized: install.sh removes the macOS quarantine itself. If macOS still refuses: xattr -dr com.apple.quarantine ~/.local/lib/orkeon.
Here for Studio? Once the CLI is installed, come back to download Orkeon Studio.
The .msi installer is unsigned: Windows SmartScreen asks for confirmation (More info → Run anyway). First compare its checksum with its line in SHA256SUMS.msi:
Get-FileHash .\orkeon-*-win-x64.msi -Algorithm SHA256The zip archive, without an installer
Take orkeon-cli-*-win-x64.zip, whose checksum is in SHA256SUMS, then double-click install.cmd.
Run this on your workstation.
First trial, on a local model
Install the prerequisites
Ollama (new tab), installed once. The .NET 10 SDK is only needed for the
dotnet toolroute.Download the local model
ollama pull qwen2.5:1.5bInstall Orkeon
Or by another install route.
dotnet tool install -g Orkeon.Scripting.CliCreate the team, then run it
The quickstart example has one agent, and its configuration already points to Ollama.
orkeon quickstart && cd orkeon-quickstartorkeon run crew.yaml --mount ./out:/output:rwrefusedThen the same folder, mounted read-only: the write is refused. orkeon run crew.yaml --mount ./out:/output:rofile_write [FAIL]: Error: Access denied for '/output/hello.md': required Write, effective ReadOnly. Mounts granting Write: (none).
For your own teams, orkeon init configures the model provider; orkeon doctor says what is missing.
The installation guide (new tab) covers the container, the prerequisites, checksum verification and rolling back to an earlier version.
Debian and Ubuntu: add the signed source
This block verifies the key’s checksum before installing it, then adds the source for the stable channel (apt guide (new tab)).
sudo apt-get update && sudo apt-get install -y ca-certificates curl
curl -fsSL -o /tmp/orkeon-archive-keyring.gpg \
https://github.com/Orkeon/orkeon/raw/apt/orkeon-archive-keyring.gpg
echo "0cc5e804e1ee49c50ec5b23145ee7ee65d4834a08b8dc38914674249dfcc6a21 /tmp/orkeon-archive-keyring.gpg" | sha256sum --check
sudo install -m 0644 /tmp/orkeon-archive-keyring.gpg /usr/share/keyrings/orkeon-archive-keyring.gpg
sudo tee /etc/apt/sources.list.d/orkeon.sources > /dev/null <<'EOF'
Types: deb
URIs: https://github.com/Orkeon/orkeon/
Suites: raw/apt/stable/
Include: orkeon orkeon-archive-keyring
Signed-By: /usr/share/keyrings/orkeon-archive-keyring.gpg
EOF
sudo apt-get updateThen:
sudo apt install orkeon orkeon-archive-keyringContainer, NuGet package, source
In a container: the image ships the example teams, and the command opens a shell in it.
docker run -it --rm -e ORKEON_ENTRYPOINT=shell ghcr.io/orkeon/orkeon:1.0.0Take a tag from the releases page (new tab), never latest. The image carries no provenance attestation: on a server, pin it by its digest (@sha256:…).
In your .NET application: dotnet add package Orkeon, and Orkeon.Tools for the built-in tools (NuGet packages (new tab)).
From source: git clone https://github.com/Orkeon/orkeon.git, then dotnet build Orkeon.sln.
- The Windows installer (
.msi) is unsigned and the macOS archive is not notarized: verify their checksum before running them. - The container image carries no provenance attestation.
- The Homebrew formula is not published yet.