Binary Downloads
Prefer to run the control server and sink directly (systemd, bare metal, your own image)? Download the raw binaries by platform. They are extracted from the exact same builds as the container images.
Latest binaries
Linux, statically linkable, for amd64 and arm64 (incl. AWS Graviton):
| Component | Platform | Download |
|---|---|---|
| Control server | linux/amd64 | tripwire-server_linux_amd64.tar.gz |
| Control server | linux/arm64 | tripwire-server_linux_arm64.tar.gz |
| Sink | linux/amd64 | tripwire-sink_linux_amd64.tar.gz |
| Sink | linux/arm64 | tripwire-sink_linux_arm64.tar.gz |
| Checksums | all | SHA256SUMS |
Install & verify
Download for your architecture, verify the checksum, and unpack:
# pick your arch: amd64 or arm64
ARCH=amd64
base=https://gettripwires.com/download
curl -fsSLO "$base/tripwire-server_linux_${ARCH}.tar.gz"
curl -fsSLO "$base/tripwire-sink_linux_${ARCH}.tar.gz"
curl -fsSLO "$base/SHA256SUMS"
# verify (only checks the files you downloaded)
sha256sum --ignore-missing -c SHA256SUMS
tar -xzf "tripwire-server_linux_${ARCH}.tar.gz" # -> ./tripwire-server
tar -xzf "tripwire-sink_linux_${ARCH}.tar.gz" # -> ./honeytoken-sink
sudo install -m 0755 tripwire-server /usr/local/bin/tripwire-server
sudo install -m 0755 honeytoken-sink /usr/local/bin/honeytoken-sink
The control server still needs its configuration (database URL, cookie domain, license)
and TLS in front of it — see Configuration.
The sink binary is named honeytoken-sink (the production sink runs it under
systemd as honeytoken-sink).
Which should I use?
Use the container images if you deploy with Docker/Compose or Kubernetes. Use these binaries if you run on bare metal / systemd, build your own image, or target arm64. Both come from the same source build, so behaviour is identical.