Download

OrgKit is only published on this page. To check that a download is the one published here, compare its SHA-256 with the hash printed beside it. You can check every file at once with SHASUMS256.txt and sha256sum -c or shasum -a 256 -c.

macOS

Open the .dmg, drag OrgKit to Applications and open it from there. The build is signed and notarized. macOS opens it without a warning.

If macOS does refuse ("cannot be opened because it is from an unidentified developer", or "Apple could not verify it is free of malware"), the file is probably not the genuine build. Check its SHA-256 against the hash above before going further. If you are sure of the file and want to open it anyway, right-click the app in Applications and choose Open, then Open again. If the dialog only offers "Done", go to System Settings → Privacy & Security, scroll to the bottom and click Open Anyway next to the message about OrgKit.

Linux

Pick the AppImage for your machine. Intel / AMD is for ordinary desktops and laptops. ARM is for a Raspberry Pi 4 or 5 and other 64-bit ARM boards. If you are not sure, you want Intel / AMD.

Save it, make it executable and run it:

chmod +x OrgKit-v1.6.5-linux-x86_64.AppImage
./OrgKit-v1.6.5-linux-x86_64.AppImage

The AppImage is the whole app and needs nothing else installed. It also runs on systems with a read-only root filesystem like the Steam Deck, Silverblue and Bazzite. It does not add itself to your applications menu. Keep the file somewhere you will find it again.

It needs glibc 2.35 or newer: Ubuntu 22.04, Debian 12, Fedora 36 or later. On an older system, build it from the source archive.

If it refuses to start with a FUSE error, unpack it and run it from there:

./OrgKit-v1.6.5-linux-x86_64.AppImage --appimage-extract
./squashfs-root/AppRun

The Linux builds are not signed. Check the SHA-256 before you run one.

Windows

There is no Windows build yet. One will appear here once it has been tested on real Windows machines. Until then you can build it yourself from the source archive. New platforms are announced in the changelog.

The firewall prompt

The first time you host a board, macOS and Windows ask whether OrgKit may accept incoming connections. Say yes so that other people in the room can reach your board. If you say no, the app still works for you but nobody else can join.

Linux does not ask. Most desktop installs need no changes. Fedora and its relatives block incoming connections by default and need two ports opened by hand.

OrgKit uses port 3883 for the app and 8080 for live editing. Both accept connections from your local network only. Neither is reachable from the internet unless you forward it on your router. If people cannot join, the help page has the firewall commands for each system.