Request access

Download

Four builds. None of them signed yet.

Version 2.0.0-alpha.2, published 6 September 2026. Take the one for your machine, then read what your operating system is about to say about it — because it will say something, and it is right to.

TZX Desk 2.0.0-alpha.2 — desktop builds
PlatformWhat it isSizeFile
WindowsInstaller — sets up the service, the shortcuts and the uninstall entry25.0 MBtzxdesk-1.4.9-win-x64.msi
WindowsPortable — runs from wherever you put it, installs nothing24.7 MBtzxdesk-1.4.9-win-x64.exe
macOSApple silicon — M1 and later, disk image26.3 MBtzxdesk-1.4.9-mac-arm64.dmg
LinuxDebian and Ubuntu on x86-64 — Debian package23.7 MBtzxdesk-1.4.9-linux-x64.deb

macOS on Intel and Android are not built yet. The Linux package is Debian and Ubuntu only — no RPM, no AppImage, no ARM. The file names carry the client build number, 1.4.9; the release they come from is 2.0.0-alpha.2.

Your computer will warn you

We have not bought code-signing certificates yet, so none of these files carry a publisher signature. The warning you get is your machine telling you the truth, and you should treat every unsigned download the same way: check the hash below before you run it.

Windows — SmartScreen

A blue panel says “Windows protected your PC” and hides the run button. Choose More info, then Run anyway. The publisher shows as unknown, because it is.

macOS — Gatekeeper

The first launch is blocked outright, and double-clicking will not get past it. Right-click (or Control-click) the app in Applications, choose Open, then Open again in the dialog. macOS remembers the decision after that.

Debian and Ubuntu will install the package you hand them without checking a signature, so the checksum is the only check you get there. When the certificates are bought and the builds are signed, these warnings go away and so does this section.

Check what you downloaded

SHA-256 for the four files above. The same list is served as SHA256SUMS, next to the builds.

f05c3d48a4b76ac5974d48098f0a4dd75832cc796d7270794751e2f11b5713fe  tzxdesk-1.4.9-win-x64.msi
9911bab4ae00a89609461a95b483df4010a00b2414d4a4075629eea622d1737d  tzxdesk-1.4.9-win-x64.exe
3113b2b7c8972b5f7481d91edf4a7af336f6bd96ed7cc34c90197a0142f34880  tzxdesk-1.4.9-mac-arm64.dmg
867b879476a6c40067a7b80ffce9ac022893c033b6c08a3158dcb7c7c68b7a97  tzxdesk-1.4.9-linux-x64.deb
  • macOS and Linux — shasum -a 256 -c SHA256SUMS — run it in the folder holding both the build and SHA256SUMS. It prints OK for every file it finds.
  • Windows — certutil -hashfile tzxdesk-1.4.9-win-x64.msi SHA256 — run it in Command Prompt and compare the result with the matching line above.

A hash that does not match means the file changed on the way to you. Do not run it — tell us at hello@tzxdesk.com.

After you install it

There is nothing to configure. The build already points at this deployment.

  1. It knows where to call

    The server address and its public key are compiled into the build. Open the app and it registers on its own — you are never asked for a server, an ID or a key.

  2. It arrives waiting

    The device shows up in the console marked PENDING. Nothing can pair with it while it sits there, and that includes us.

  3. An administrator approves it

    Someone with rights on the tenant approves the device at app.tzxdesk.com. Only then will the server admit a session to it.

No console account yet? Request access and we will set the tenant up with you. These are pre-release builds meant for pilot use — when one misbehaves we want to hear about it, at hello@tzxdesk.com.

You still need somewhere to approve it.

Personal is free for up to five devices. Team is $19 per technician a month.

Request access