Download

OrgKit is distributed from this page and nowhere else. There is no app store listing and no third-party mirror, so the SHA-256 printed with each file is what tells you the download is the one published here. Every hash on this page is also in SHASUMS256.txt, which sha256sum -c and shasum -a 256 -c both read.

macOS

Open the .dmg and drag OrgKit to Applications, then open it the ordinary way. The build is signed and notarized, so there is no right-click, no unidentified developer warning, and nothing to click through.

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 you have is not the one published here. 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, choose Open, then Open again. Where the dialog offers only "Done", go to System Settings → Privacy & Security, scroll to the bottom, and click Open Anyway next to the message about OrgKit.

Linux

Take the AppImage for your machine. Intel / AMD is an ordinary desktop or laptop; ARM is a Raspberry Pi 4 or 5, or another 64-bit ARM board. If you are not sure, it is the Intel / AMD one.

Save it, make it executable, and run it:

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

There is nothing to install and no package manager involved. The file carries its own browser engine and asks nothing of the system beyond an ordinary desktop's graphics libraries, so it needs no network at any point and it runs on a machine whose root filesystem is read-only: Steam Deck, Silverblue, Bazzite. It adds no menu entry either, so keep the file somewhere you will find it again.

It needs glibc 2.35 or newer. That is Ubuntu 22.04, Debian 12, Fedora 36, and anything more recent. An older system will refuse to start it, and the source archive is the route there.

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

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

Same app, no FUSE required.

Nothing is signed on Linux, and that is deliberate rather than an omission. The SHA-256 is the whole authenticity story here, the same as it is beside the disk image.

Windows

Not published yet. It builds from the same source as everything above, and lands on this page once it has been run on the hardware it ships to. Until then the source archive builds on it, and the changelog is where a new platform gets announced.

The firewall prompt

The first time you host a board, macOS and Windows ask whether OrgKit may accept incoming network connections. Say yes. That permission is what lets the other people in the room reach your board. Denying it doesn't break the app for you, but nobody else will be able to join.

Linux asks nothing. On most desktop installs there is no inbound firewall running and it simply works. Fedora and its relatives are the exception: they ship firewalld with inbound traffic denied, which stops everyone else joining and says nothing about it.

OrgKit listens on two ports, 3883 for the app itself and 8080 for live editing. Both accept connections from your local network only; neither is reachable from the internet unless you deliberately forward it. If you missed the prompt, clicked Deny, or are on one of the systems that never asked, the help page has the commands for each.