Released 15 September 2026. Trial builds are identical to production builds; the account token decides which plan applies. Older releases are kept for two years and are listed in the changelog.
| Platform | File | Size | SHA-256 (short) |
|---|---|---|---|
| Windows 10/11, Server 2019+ | tripleguard-agent-3.8.2.msi | 61.4 MB | a71c9f4e… |
| macOS 13+ (universal) | tripleguard-agent-3.8.2.dmg | 74.8 MB | 4db0e215… |
| Debian, Ubuntu (amd64) | tripleguard-agent_3.8.2_amd64.deb | 38.2 MB | 9c51a7b8… |
| RHEL, Alma, Rocky (x86_64) | tripleguard-agent-3.8.2.x86_64.rpm | 39.1 MB | 2f84dd60… |
| Linux arm64 (NAS, SBC) | tripleguard-agent_3.8.2_arm64.tar.gz | 35.7 MB | c0e39a17… |
Builds are served to signed-in customers from get.tripleguard.ru. Sign in to the dashboard and open Downloads, or use the repository:
curl -fsSL https://get.tripleguard.ru/install.sh | shTripleGuard is sold to teams, and accounts are created by the team administrator. New members get an invitation by email with a one-time code; there is no open sign-up form, which keeps stray machines out of a paid seat count.
If you need access and do not know who administers your account, write from your work address to support@tripleguard.ru and we will point you to the right person. For a new team, request a trial at sales@tripleguard.ru — trials run for 30 days on the Team plan limits.
Every release is signed. On Linux the repository key is installed by the setup script; to check a downloaded file by hand:
sha256sum -c tripleguard-agent_3.8.2_amd64.deb.sha256
gpg --verify tripleguard-agent_3.8.2_amd64.deb.ascSigning key fingerprint: 3F7A 55C1 9E02 4B8D 6A11 77E5 2C90 D4B3 8AF6 1C22. The key is rotated every two years; the previous key stays valid for verification of old releases.