Winlink Express is the client most hams default to, but it’s Windows-only, which leaves Mac and Linux users, along with anyone running Winlink from a Raspberry Pi, looking for an alternative. Pat fills that gap: a free, open-source, cross-platform Winlink client that runs pretty much anywhere.
Why Pat exists
Pat was built to give non-Windows users a real Winlink client instead of relying on virtual machines or Wine compatibility layers to run Winlink Express. It handles the core Winlink workflow, composing and sending messages, connecting through ARDOP, VARA, or packet, and managing your message forms, with a clean web-based interface you access through a browser rather than a native desktop app.
Getting it installed
Pat installs as a standalone binary on macOS, Linux, or Windows, and configuration happens through a straightforward setup wizard that asks for your callsign and your preferred connection method. If you’re already running ARDOP or VARA for Winlink Express, pointing Pat at the same modem software is usually just a matter of matching the TCP port settings between the two.
Sending your first message
Once configured, composing and sending a message through Pat looks almost identical to Winlink Express: address it to another callsign or a standard email address, connect to a nearby gateway using whichever modem you’ve set up, and Pat handles the rest. It’s a genuinely solid option if you’re building a Raspberry Pi-based go-kit or just prefer not to run Windows for your Winlink station.
Related reading: What Is VARA? · ARDOP vs VARA · NBEMS and Practice Nets