Canarytokens vs MedPot
Canarytokens
canarytokens.orgMedPot
github.comSide by side
| Figure | Canarytokens | MedPot |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Windows | Yes | — |
| Linux | — | Yes |
| iOS | Yes | — |
| Android | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Honeypot Software | 8.2 (#1) | 7.5 (#13) |
| Purpose | Canarytokens are decoy tokens placed in networks, computers, and cloud environments to alert when accessed. | MedPot is a honeypot that emulates HL7 / FHIR. |
Plans
In their own words
Canarytokens
Canarytokens are decoy tokens placed in networks, computers, and cloud environments to alert users when accessed. The hosted service lets users create tokens without installing software; they can provide an email address to receive an alert when a token is triggered. Some token types also accept a webhook address. Documented examples include HTTP, DNS, Windows directory, AWS API key, Kubernetes configuration, and WireGuard tokens. The Fake IdP SAML App token has setup instructions for Microsoft Entra ID and Okta. Fake App is a Progressive Web App that alerts when opened and can include device location if location access is allowed; it currently supports Safari and Google Chrome. Sensitive Command monitors execution of a specified command on Windows and requires importing its registry file with administrator permissions. The Slack API Token is deprecated, and new tokens cannot be created, though existing ones continue to work. Use of the hosted service through canarytokens.org costs nothing. The maker also publishes the server as open-source software and recommends Docker for self-hosting.
MedPot
MedPot is a free, open-source honeypot that emulates HL7 and FHIR services. It is intended for self-hosted use on Linux as an application-level decoy. The project documents running it with Go or a script, compiling it into a binary, and building a Docker container; installation requires Go 1.17 or newer. By default, it listens on port 2575 and writes logs to /var/log/medpot.log. Command-line arguments can change the listening port and log location, and choose between two boot logos. Templates and configuration files are located in /etc/medpot/. An example log record includes a timestamp, port, IP address, message, level, and captured data. Docker is the documented deployment option. The project does not specify a narrower target audience. Its README does not specify support terms, security certifications, or compliance standards.