Download

Download Ollama Loader for Windows or Linux.

Current installers, signed update packages, SHA-256 checksums, and deployment notes for the oload control plane.

Install Track

Desktop install

Install the packaged Windows or Linux build when chat, model management, and local administration will run on the same machine.

Install Track

Server-backed install

Use this route when operators need the oload interface and gateway layer while Ollama or provider access is hosted elsewhere.

Install Track

Update and support path

Pair deployment with public release notes, signed update manifests, and install guidance so upgrades stay predictable and supportable.

Live Asset

Windows installer

OloadSetup.exe · 271.2 MB

Native Windows installer for the current packaged oload build.

Download file

Live Asset

Linux installer

OloadInstaller-linux-x64.run · 344.5 MB

Native Linux x64 installer bundle for the current packaged oload build.

Download file

Live Asset

Windows update bundle

Local mirror

oload-update-0.1.0.zip · 5.1 MB

Current Windows update package for the packaged 0.1.0 line.

Site-hosted mirror. Updater source: published GitHub release asset.

Download file

Live Asset

Linux update bundle

Local mirror

oload-update-0.1.0.tar.gz · 4.3 MB

Current Linux update package for the packaged 0.1.0 line.

Site-hosted mirror. Updater source: published GitHub release asset.

Download file

Release archive

Version 0.1.0

2026-04-28 · stable

oload

Operator platform wave with installer inventory tracking, signed manifest delivery, and expanded AI workspace tooling.

OloadSetup.exe

271.2 MB

SHA-256: 24514452288A852517521F515BC470E978FAAFDE5736C650CACD70BC35E37122

Download file

OloadInstaller-linux-x64.run

344.5 MB

SHA-256: 5E813EAC1550BD4B54BD7F4C6564D5A9D837BB24715B9D7DC208E6097882A20C

Download file

oload-update-0.1.0.zip

5.1 MB

SHA-256: B789483521874EA4A94435E229C54BE77E0FF24E1C3B2D0516FFFE54DA8E2BCC

Download file

oload-update-0.1.0.tar.gz

4.3 MB

SHA-256: EDA772555C097364CF2C8E32C1885B749B92E36DD61D1534BE3FF004B81F1C85

Download file

First Install Expectations

Step 01

Choose the right route

Desktop-first when the runtime lives on the same machine. Server-backed when the operator path depends on a managed host or separate runtime target.

Step 02

Install with the runtime in mind

Make it explicit what runs locally, what may call outward, what ports matter, and what the first successful launch should look like.

Step 03

Keep updates predictable

Pair installers with release notes, update guidance, uninstall notes, and support routes so operators are not forced into guesswork after the first install.

Manual And Support Files

Administrator manual PDF

Printable administrator manual covering installer setup, install footprint, updates, uninstall behavior, and GitHub self-service links.

Open PDF

GitHub repository

Open the source repository for install scripts, packaging docs, release history, and tracked implementation changes.

Open GitHub repo

GitHub releases

Fetch the packaged release artifacts directly from GitHub if you want the upstream self-service source instead of the mirrored site copy.

Open releases

Installer docs in repo

Read the mirrored install, update, and uninstall behavior directly in the repository packaging docs.

Open installer docs

Platform notes

Windows install and runtime defaults

Default install root is %LOCALAPPDATA%\Oload. Machine state is written to %LOCALAPPDATA%\OloadData, the runtime environment is stored in .env.runtime, and Oload-managed runtimes live under runtime\node, runtime\ollama, and runtime\ollama-models.

Linux install and launcher defaults

Default install root is ~/.local/share/oload. The desktop launcher is written to ~/.local/share/applications/oload.desktop, Linux machine state is kept under ~/.local/state/oload, and Oload-managed runtimes live inside runtime/node, runtime/ollama, and runtime/ollama-models.

Update publishing and manifest flow

The installer writes the update manifest URL, channel, and public key into .env.runtime. Update bundles validate with SHA-256 package checks and can be published through GitHub Releases with signed manifest delivery mirrored through GitHub Pages.

Storage, uninstall, and owned-path tracking

INSTALL-MANIFEST.txt and UNINSTALL-NOTES.txt record the install root, runtime paths, and dependency ownership before removal. Oload asks again before touching shared Node.js or Ollama, and isolated local Ollama shifts to port 11435 when 11434 is already occupied by a shared service.

Live Update Endpoint

The stable and versioned GitHub Pages manifests are now published from the release-updates workflow. The live stable manifest points to the GitHub Releases package URLs for v0.1.0, and the installers persist the manifest URL, channel, and public key for update checks.

Manifest URL: https://snowolfex.github.io/olaod/updates/stable/manifest.json

Repository: https://github.com/snowolfex/olaod

Channel: stable

Latest published version: 0.1.0

Manifest published at: 2026-05-08T19:26:48.501Z

Verification: Signed update manifest verification

Status: Live on GitHub Pages for v0.1.0 as of 2026-05-08 19:26:48Z.

Installer manifest env: OLOAD_UPDATE_MANIFEST_URL

Installer channel env: OLOAD_UPDATE_CHANNEL

Installer public-key env: OLOAD_UPDATE_MANIFEST_PUBLIC_KEY

GitHub Actions signing secret: OLOAD_UPDATE_MANIFEST_PRIVATE_KEY

Published GitHub release assets are the updater source of truth. Local mirrors are listed above.

Windows published update

Published GitHub release asset

oload-update-0.1.0.zip · zip

SHA-256: F0F54222A8CF097A62C098103D67640C0362D8B3B7505FF3E0B060F259CDE1AC

Open GitHub release asset

Linux published update

Published GitHub release asset

oload-update-0.1.0.tar.gz · tar.gz

SHA-256: 8A4BD146E530F7A8164E30DCFD959B03B7BD36BA38FB8D4E50CBE5A8F7297B7E

Open GitHub release asset