Download

Get WorkloadWall

One machine that stays on, and about ten minutes. Thirty days with every feature, no card and no account — then it goes read‑only until you enter a key, and nothing is deleted.

Version 1.6.0 · published 2026-09-08

What’s new in 1.6.0Photos on requests: requesters can attach up to ten photos or PDFs on the wall form (shrunk in the browser first); staff can attach to notes; email attachments are kept on the ticket. Linux builds (x64/arm64) with a systemd installer.

Windows

The usual choice: any Windows 10 or 11 machine, 64‑bit, that stays on. The installer bundles everything — no database, no runtime, nothing fetched during setup — and registers a service that starts at boot whether or not anyone is logged in.

Download WorkloadWall 1.6.0

37.5 MB · WorkloadWall-Setup-1.6.0.exe

Verify the download

SHA‑256
ad437d6e96db43533844e7cccc0fdabd966c96beab54483893f4b8ad4ffeb9a4

In PowerShell: Get-FileHash .WorkloadWall-Setup-1.6.0.exe

Updates install themselves. Data lives in C:ProgramDataWorkloadWall.

What happens when you run it

Windows may warn about an unrecognised publisher — choose More info → Run anyway. Check the SHA‑256 if you want to be sure of the file.
Accept the defaults. The only choice is the port — leave 3000 unless something on that PC already uses it.
A browser opens on the setup page. You name the department, create the first account, and add a few categories.
You are handed the wall’s address on your network. That is the link you send the building.
The 30‑day trial starts, with every feature on.

Requirements: Windows 10/11 64‑bit, 4 GB RAM, ~500 MB of disk plus room for attachments.

Linux

A Raspberry Pi 4 or 5, a retired desktop, a NAS — anything 64‑bit with systemd and a gigabyte of RAM. Unpack, run the installer, and you have a workloadwall service that starts at boot.

Intel / AMD (x64) · 48.3 MB Raspberry Pi / ARM (arm64) · 48.2 MB

Verify the downloads

x64 SHA‑256
55325f7d65b7b6fa7ac579a00b0d9a2e561e609d0b9dca9d6ae6c1a2da0dc609

arm64 SHA‑256
442b4faf0d9f587d518bf367b0a54425c97e1818d055e2597728e88cfafbdcc8

sha256sum workloadwall-*.tar.gz

Install

tar -xzf workloadwall-<version>-linux-*.tar.gz
cd workloadwall-<version>-linux-*
sudo ./install.sh

Add a port as the first argument if 3000 is taken: sudo ./install.sh 8080.

Installs to /opt/workloadwall, data in /var/lib/workloadwall.
Upgrading is the same three lines with a newer tarball — your data stays.
sudo ./uninstall.sh removes it; --purge also deletes the data.
To try it without installing, ./run.sh runs it in the foreground.

Updates are not automatic on Linux. Admin → Updates tells you when a new version is out and links the tarball.

Docker

The image is dagazllc/workloadwall on Docker Hub, built for linux/amd64 and linux/arm64. The 1 tag always points at the latest 1.x.

docker run -d --name workloadwall \
  --restart unless-stopped --network host \
  -v workloadwall-data:/data \
  dagazllc/workloadwall:1

Update with docker pull dagazllc/workloadwall:1 and recreate the container. Your data is the workloadwall-data volume.

About host networking

Host networking is what lets workloadwall.local answer on your LAN, so people can reach the wall by name instead of an IP address.

If you would rather not use it, publish the port and turn the name off:

docker run -d --name workloadwall \
  --restart unless-stopped -p 3000:3000 \
  -e MDNS_DISABLE=1 \
  -v workloadwall-data:/data \
  dagazllc/workloadwall:1

People then reach it at http://<host>:3000.

Whichever way you install it, the data stays on your machine and the app is the same. Editions are set by the licence key, not the download — see pricing.

Questions people ask before installing

Does anything leave our network?

The app checks for updates and validates its licence file offline. Your tickets, photos, attachments and mailbox contents stay on the machine you installed it on. If you turn on AI intake with a local model through Ollama, the ticket text does not leave either.

Which one should I install?

Windows if you have a PC that stays on — it is the only one that updates itself. Linux if you would rather run it on a Pi or an old machine and do not mind running an installer again for updates. Docker if you already run containers and have opinions about where data lives.

Can I try it without pointing it at our real mailbox?

Yes. Email intake is optional and off until you connect a mailbox. You can run the whole trial on the request form alone.

What if we already have a pile of tickets somewhere else?

Local Pro imports them. Bring a CSV export from whatever you are leaving and it lands as tickets with their history intact.

What happens on day 31?

The app goes read‑only. Everything is still there and still readable; new tickets stop until a key is entered. Nothing gets deleted, ever, for lack of a licence.