DentiGrid vs MedPot
DentiGrid
dectrax.comMedPot
github.comSide by side
| Figure | DentiGrid | MedPot |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Linux | — | Yes |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Honeypot Software | 7.8 (#5) | 7.5 (#13) |
| Integrations | Listed SIEM integrations include Splunk, Microsoft Sentinel, Elastic, and IBM QRadar; the page also describes ArcSight event export. | The maker's README documents Docker as a deployment option and does not list other product integrations. |
| Purpose | DentiGrid is a SIEM-native honeypot platform for MSSPs and enterprise SOC teams that uses decoy assets to detect adversary activity. | MedPot is a honeypot that emulates HL7 / FHIR. |
Plans
In their own words
DentiGrid
DentiGrid is a paid, hybrid SIEM-native honeypot platform for MSSPs and enterprise SOC teams. It uses synthetic decoys such as SSH keys, S3 buckets, Postgres tables, Kubernetes secrets, API keys, and fake Active Directory accounts to detect unauthorized activity. Dectrax says deployment is agentless, takes under five minutes, and uses RMM, Microsoft Intune, Jamf, or Ansible tooling. Lures are stated to consume 0% CPU or memory. Triggered alerts can include origin IP, process tree, and target node, with delivery to SOC webhooks. Listed SIEM integrations include Splunk, Microsoft Sentinel, Elastic Security, IBM QRadar, and ArcSight. Telemetry is encrypted and HMAC-signed, and verified adversary IPs can be added to Palo Alto and Fortinet External Dynamic Lists. Enterprise organizations can provision self-hosted decoys in AWS, Azure, and on-premises subnets via Docker. Commercial licensing includes multi-tenant management, telemetry pipelines, connectors, and SLA-backed support. The listed maximum is three decoys with 30-day retention.
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.