OpenCanary
github.com
What it is
OpenCanary is free, self-hosted software that acts as a network honeypot, imitating services so it can alert when someone interacts with them after entering a non-public network. It runs as a daemon and can report details such as a source IP address and a possible breach location. Service modules cover SSH, FTP, Git, web protocols, databases, Telnet, SNMP, SIP, VNC, Redis, TFTP, NTP, and TCP banners. Alerts can go to files, Syslog, email, HTTP webhooks, Slack, Microsoft Teams, or HPFeeds-compatible daemons. Its companion correlator can combine related events into a single email or SMS alert. The project says it has very low resource requirements and can run on a Raspberry Pi or a minimally resourced virtual machine. Documentation covers Ubuntu, macOS, and Docker on Linux hosts. Linux supports the broadest set of options: SMB monitoring is unavailable on macOS, and portscan monitoring is Linux-only and disabled in Docker. The project advises restricting write access to its configuration file because it is read with root privileges.
Spec sheet
- Purpose
- OpenCanary is a multi-protocol network honeypot intended to detect attackers interacting with services on non-public networks.Read 2 Oct 2026 · github.com
- Deployment
- The project documents installation on Ubuntu and macOS, plus Docker deployment on Linux hosts using host networking.Read 2 Oct 2026 · github.com
- Support
- Bug reports are requested through GitHub, security vulnerabilities through the project security policy, and feature requests through the project tracker.Read 1 Oct 2026 · github.com
- License
- The PyPI listing identifies OpenCanary as OSI Approved BSD licensed software.Read 1 Oct 2026 · pypi.org
- Alert channels
- The documentation lists Syslog, email, and the opencanary-correlator as alert destinations.Read 1 Oct 2026 · github.com
- Alert destinations
- Documented logging and alert options include files, Syslog, SMTP email, HTTP webhooks, Slack, Microsoft Teams, and HPFeeds-compatible daemons.Read 2 Oct 2026 · opencanary.readthedocs.io
- Alert details
- Alerts can identify the threat source IP address and where the breach may have occurred.Read 1 Oct 2026 · github.com
- Chat integrations
- Webhooks can post to Slack or Microsoft Teams channels.Read 1 Oct 2026 · github.com
- Correlator
- The companion opencanary-correlator can combine related events into a single email or SMS alert.Read 2 Oct 2026 · opencanary.readthedocs.io
- Event correlation
- The correlator coalesces multiple related events, such as individual brute-force login attempts, into one alert sent by email or SMS.Read 1 Oct 2026 · github.com
- Extra modules
- Optional SMB monitoring watches Samba logs for files opened in a Windows file share, and optional portscan monitoring uses iptables to detect scans.Read 2 Oct 2026 · opencanary.readthedocs.io
- Maintainer and commercial relation
- OpenCanary is maintained by Thinkst Canary and described as the open-source version of its commercial Thinkst Canary honeypot.Read 2 Oct 2026 · github.com
- Operation
- It runs as a daemon that imitates network services and sends alerts when they are accessed.Read 2 Oct 2026 · github.com
- Optional modules
- The optional SNMP module requires Scapy, while the Windows File Share module requires Samba.Read 1 Oct 2026 · github.com
- Platform limits
- Linux offers the most options; the SMB module is unavailable on macOS, and portscan is Linux-only and uses iptables rather than nftables.Read 2 Oct 2026 · github.com
- Portscan limit
- The portscan module is supported only on Linux hosts because it modifies iptables rules, and it is automatically disabled in Dockerized OpenCanary.Read 1 Oct 2026 · github.com
- Privilege handling
- When started with uid and gid flags, OpenCanary drops root privileges after binding to its ports.Read 2 Oct 2026 · github.com
- Protocol mimicry
- It can mimic an array of network-accessible services for attackers to interact with.Read 1 Oct 2026 · github.com
- Protocols
- Native service modules include SSH, FTP, Git, HTTP, HTTPS, HTTP proxy, MSSQL, MySQL, Telnet, SNMP, SIP, VNC, Redis, TFTP, NTP, and TCP banner.Read 2 Oct 2026 · opencanary.readthedocs.io
- Resource needs
- The project says it has very low resource requirements and can run on a Raspberry Pi or a minimally resourced virtual machine.Read 2 Oct 2026 · github.com
- Resource use
- OpenCanary has extremely low resource requirements and can run on a Raspberry Pi or a minimally resourced virtual machine.Read 1 Oct 2026 · github.com
- Security configuration
- The project recommends making its configuration file root-owned and writable only by root because it is read while the process has root privileges.Read 2 Oct 2026 · github.com
- Security guidance
- The project recommends making the configuration file root-owned and writable only by root because writable configuration can allow privilege escalation.Read 1 Oct 2026 · github.com
- Security reports
- Thinkst accepts vulnerability reports at [email protected] or through GitHub and says it will request a CVE on the reporter’s behalf for reported security bugs.Read 2 Oct 2026 · github.com
- Support and participation
- The project directs bug reports to GitHub and welcomes pull requests and feature requests.Read 2 Oct 2026 · github.com
- Webhook integration
- A customizable webhook logging handler sends data to an HTTP endpoint and supports GET, POST, and PUT methods.Read 1 Oct 2026 · github.com
Plans and prices
Strong points and limits
Strong points
- Free, self-hosted deployment
- Imitates a broad range of network services
- Alerts support email, Syslog, webhooks, and chat
- Can run on a Raspberry Pi
Limits
- SMB monitoring is unavailable on macOS
- Portscan monitoring is Linux-only
- Portscan monitoring is disabled in Docker
- Configuration must be protected from writes
Who it suits
OpenCanary suits teams that want a self-hosted decoy for detecting activity on non-public networks. It is also suited to low-resource deployments such as a Raspberry Pi.
OpenCanary in depth
Read the full write-up
OpenCanary is a self-hosted honeypot that imitates network services to detect intruders inside non-public networks. It suits security teams able to manage a host and respond to alerts. Its broad protocol coverage and low resource demands make it a strong free option, but Linux is needed for its fullest set of modules.
Overview
OpenCanary runs as a daemon, presenting decoy network services and alerting when they are accessed. Native modules span SSH, FTP, Git, HTTP and HTTPS, HTTP proxy, MSSQL, MySQL, Telnet, SNMP, SIP, VNC, Redis, TFTP, NTP and TCP banner. That range lets teams create lures across several common service types rather than relying on a single-protocol honeypot. Alerts can identify the source IP and indicate where a breach may have occurred, providing a useful starting point for investigation.
Resource requirements are low enough for a Raspberry Pi or a minimally resourced virtual machine. This makes OpenCanary practical for adding network decoys without dedicating substantial compute capacity. The project is maintained by Thinkst Canary as the open-source version of its commercial honeypot, and the PyPI listing identifies it as OSI Approved BSD-licensed software.
Key features
Alert routing is a particular strength. Documented destinations include files, Syslog, SMTP email, HTTP webhooks, Slack, Microsoft Teams and HPFeeds-compatible daemons. The customizable webhook handler supports GET, POST and PUT, so teams can direct event data to an HTTP endpoint; webhooks can also post to Slack or Teams channels. These choices are useful for fitting alerts into existing monitoring workflows, though configuring those destinations remains part of operating a self-hosted service.
The companion opencanary-correlator can combine related events, such as repeated brute-force login attempts, into one email or SMS alert. That can reduce noisy alert streams while retaining a summary of a related sequence. Optional modules add Samba-log monitoring for files opened in a Windows file share and portscan detection through iptables.
Privilege handling deserves attention. When started with uid and gid flags, OpenCanary drops root privileges after binding to its ports. The project recommends making the configuration file root-owned and writable only by root: because the process reads it with root privileges, a writable configuration could enable privilege escalation. This is a meaningful deployment requirement, not an optional hardening detail.
Pricing
OpenCanary costs nothing. The OpenCanary plan is open-source software for self-hosted deployment, with no software charge. That makes it a fit for teams prepared to run and configure their own honeypot; the trade-off is that operation and alert setup are their responsibility.
Platforms
OpenCanary supports Linux, macOS and self-hosted deployment. Linux offers the broadest module choice: the SMB module is unavailable on macOS, while portscan monitoring is Linux-only because it modifies iptables rules and does not use nftables. Portscan monitoring is also automatically disabled in Dockerized OpenCanary. Docker deployment is documented for Linux hosts using host networking, so container users should not assume every module remains available.
The project documents installation on Ubuntu and macOS. Optional SNMP monitoring requires Scapy, and the Windows File Share module requires Samba. Those dependencies and platform restrictions matter when selecting a host and deciding which decoys to enable.
Who it's for
OpenCanary is best suited to defenders who want several network-service decoys on modest self-hosted infrastructure and can maintain a protected configuration file. It is particularly compelling when low resource use and flexible alert destinations matter. It is a weaker fit for teams that need the portscan module on macOS or in Docker, or that cannot manage host permissions and alert routing themselves.
Pros and cons
Pros: Broad native protocol coverage gives defenders multiple service types to imitate with one daemon.
Pros: Low resource needs make deployment on a Raspberry Pi or minimally resourced virtual machine practical.
Pros: File, Syslog, email, webhook, chat and HPFeeds-compatible destinations provide multiple ways to route alerts.
Cons: Linux has the fullest feature set; SMB is unavailable on macOS and portscan monitoring is Linux-only.
Cons: Portscan detection relies on iptables and is disabled in Dockerized deployments, limiting its fit for nftables-based hosts and containers.
Cons: Configuration permissions require care because a writable file can create a privilege-escalation risk.
Alternatives
Honeypot Software is the broader category to browse. Among individual options, Beelzebub is another free, self-hosted choice, with Linux and API platform support and a free trial. Canarytokens is worth considering when free tokens deployed through its hosted service are a better fit than operating a multi-protocol daemon; it spans web, mobile, Windows and self-hosted platforms.
Honeyd is another free Linux and Windows self-hosted option, while T-Pot offers a free open-source self-hosted deployment across Linux, macOS and Windows, with hardware and network requirements applying. Cowrie is a free BSD-licensed SSH and Telnet honeypot for Linux self-hosting, a narrower protocol focus than OpenCanary's. Honeytrap is a free Apache-licensed self-managed option for Linux, and Heralding is a free GPL-3.0 licensed Linux self-hosted honeypot.
Thinkst Canary is the paid alternative from the same maintainer, with five canaries for $7,500 a year and hardware, virtual, cloud or container deployment options. It is the option to consider when those deployment choices justify a paid commercial product rather than self-managing OpenCanary.
Verdict
Choose OpenCanary if you want a free, resource-light honeypot with a wide range of service decoys and can operate it securely on a self-hosted system. Its strongest case is breadth without a software charge; look elsewhere if your required module is unavailable on your platform or you cannot take responsibility for careful configuration and alert handling.
Verdict
OpenCanary offers broad protocol coverage and alert options without a software charge. Platform-specific module limits and careful configuration-file permissions matter before deployment.
Where Specifiction places it
- Honeypot Software#2 of 218.2