Install CryoZen on your machine.
Latest release v1.1.0, published August 25, 2026. Builds come straight from GitHub Releases. If a button below opens the releases page instead of downloading, that platform's file is not attached to this release.
macOS
Disk image (.dmg) · 109 MB
A self-contained app: drag to Applications and launch. The server starts locally and CryoZen opens in your browser.
Requirements
- macOS 13 Ventura or newer (Apple Silicon; Intel build below)
- No Python install needed - it is bundled
After downloading
- 1Open CryoZen.dmg and drag CryoZen to Applications.
- 2If macOS says the app cannot be opened, right-click CryoZen, choose Open, then Open again: unsigned builds need this once. Signed and notarized builds open normally.
- 3Your browser opens at http://127.0.0.1:7860 when the server is ready. Data lives in ~/Library/Application Support/CryoZen.
Windows
Installer (.exe) · 74 MB
A standard installer: Program Files, a Start Menu shortcut, and an entry in Apps & Features. Prefer the portable zip to run from a folder without installing.
Requirements
- Windows 10 or newer (64-bit x64)
- No Python install needed - it is bundled
After downloading
- 1Run CryoZen-Setup-x64.exe and follow the prompts. Silent install for scripts: CryoZen-Setup-x64.exe /S
- 2If SmartScreen appears on an unsigned build, choose More info, then Run anyway. Signed builds do not prompt.
- 3Launch CryoZen from the Start Menu. Your browser opens at http://127.0.0.1:7860 when the server is ready. Data lives in %LOCALAPPDATA%\CryoZen and survives uninstall.
Linux
AppImage (x86_64) · 120 MB
A single self-contained executable that runs on any distribution. Also available as .deb, .rpm, and a portable tarball.
Requirements
- A 64-bit distribution with glibc
- No Python install needed - it is bundled
After downloading
- 1Make it executable: chmod +x CryoZen-x86_64.AppImage
- 2Run it: ./CryoZen-x86_64.AppImage
- 3Your browser opens at http://127.0.0.1:7860 when the server is ready. Data lives in ~/.local/share/cryozen.
Docker
Container image
The recommended path for servers, GPUs, and anything long-running. Runs the full stack, including SearXNG and ChromaDB, from the published image (linux/amd64 and linux/arm64); no build step.
- Docker with Compose v2
- A host you control
Images are also published to ghcr.io/shreejitverma/cryozen on every tagged release.
git clone https://github.com/cryozenai/cryozen-releases.gitcd cryozen-releases && cp .env.example .envdocker compose up -dThe stack comes up on http://localhost:7000. Create the first administrator account when prompted, then connect a model on the integrations page.
The desktop builds are not code-signed yet
macOS Gatekeeper blocks the first launch of an unsigned app. Right-click CryoZen in Applications, choose Open, then confirm. Windows SmartScreen shows a similar prompt: choose More info, then Run anyway.
What a desktop build includes, and what it does not
Every desktop build bundles its own Python runtime. Your data lives in your user folder, so upgrading is replacing the app, and uninstalling never touches your data.
SearXNG and ChromaDB come with the Docker stack, not the desktop builds. Without them, web search goes directly to DuckDuckGo, and document search is unavailable unless you run ChromaDB yourself. Some features still assume the Docker port and data path, including model auto-stop and image editing; that fix is planned.
Looking for an older version? Browse every release on GitHub.