Beelzebub vs MedPot
Beelzebub
beelzebub.aiMedPot
github.comSide by side
| Figure | Beelzebub | MedPot |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | Yes | — |
| Open source | — | — |
| Linux | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Honeypot Software | 8.1 (#3) | 7.5 (#13) |
| Integrations | The platform routes structured events and investigation context through APIs and webhooks and lists SIEM, SOAR, identity, firewall, and cloud integrations. | The maker's README documents Docker as a deployment option and does not list other product integrations. |
| Purpose | Beelzebub deploys realistic decoys and canary credentials to detect attacker movement and provide investigation context to security teams. | MedPot is a honeypot that emulates HL7 / FHIR. |
Plans
In their own words
Beelzebub
Beelzebub deploys decoys and canary credentials to help security teams detect attacker movement and investigate activity. Its decoys cover HTTP, SSH, Telnet, MCP and other protocols. Specialized agents investigate decoy sessions for triage, threat hunting, malware analysis, incident response and reporting. Each session yields a plain-English account of attacker actions, observed techniques and captured artifacts, tied to the original session. Structured events and investigation context can be routed through APIs and webhooks, with integrations listed for SIEM, SOAR, identity, firewall and cloud systems. The core framework is open source and can be self-hosted for free. The maker says it runs with Docker or Kubernetes in cloud and on-premises environments, and offers local model options for restricted or air-gapped evaluation. Active testing can be restricted to an approved scope; exploitation requires human approval, with evidence retained for review. The managed platform has a 14-day free trial, and enterprise customers can request a 30-day proof of concept.
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.