Get the GaragePro app

The same workshop, on whatever you are holding. Sign in with your GaragePro email once and the device stays signed in — jobs, check-ins and runs keep working when the Wi-Fi does not.

Android tablets and phones

Version 1.0.0 · 07-09-2026 · Needs Android 6.0
First native release. Arrival, technician jobs, driver runs and the workshop board — all working with the Wi-Fi off.
Signed by: CN=GaragePro App, O=Tuwatech (3D:0F:FA:7E:...:B1:B0)
SHA-256 (arm64-v8a): 8323d3d62ec4012523606029ec67d1e9cd090e6b505f0a3831955163efd79548
SHA-256 (armeabi-v7a): 1b050fc4fdf6a558b4b79ea4e69227260a9ed83c8b1d93623feaaa2d1ace0fe5
SHA-256 (x86_64): c976c8ba82479cfece10e8e10f2cc639e77b80fd0f321ea8d569b650ccbcf4b1

Windows desktop

Version 1.0.0 · 07-09-2026 · Needs Windows 10
First native release. Arrival, technician jobs, driver runs and the workshop board — all working with the Wi-Fi off. Unzip the whole folder and run GaragePro.
Signed by: Not code-signed (SmartScreen will warn on first run)
SHA-256 (x64): dc78d93888269f01a792c1dddeb8688d6a97867a3c51c567f20bba9af2e8c993

Linux desktop

Version 1.0.0 · 07-09-2026 · Needs Ubuntu 20.04 or newer
First native release. Arrival, technician jobs, driver runs and the workshop board — all working with the Wi-Fi off. Install with: sudo apt install ./garagepro_1.0.0_amd64.deb
Signed by: Not code-signed (Debian packages outside a signed apt repository are not)
SHA-256 (amd64): 89582ef8868dc2ca1f12e38bc535622802f6988be973ba365e28eb57b7bc3362

Which Android file?

Almost every tablet and phone made in the last ten years is arm64-v8a. Take armeabi-v7a only for an old 32-bit device, and x86_64 only for an emulator. Android will refuse to install the wrong one rather than misbehave, so a wrong guess costs a download and nothing else.

Installing the Android file

Open the downloaded file on the device and allow your browser to install apps when asked. That prompt is Android checking you meant it — the file came from your own workshop's server.

Checking you got ours

The SHA-256 above is the checksum of the exact file we built. On Windows run certutil -hashfile THEFILE SHA256 in Command Prompt; on Linux or a Mac run sha256sum THEFILE. It should match character for character.