Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

OpenCanary

github.com

  • Free plan
  • macOS
  • Linux
  • Self-hosted
7.6 Club score Visit github.com

What OpenCanary is

OpenCanary is free, self-hosted software that acts as a network honeypot: it imitates services and alerts 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. Webhooks support GET, POST, and PUT. The companion opencanary-correlator can group related events, such as repeated login attempts, 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. Deployment documentation covers Ubuntu, macOS, and Docker on Linux hosts. Linux offers the most options: SMB monitoring is unavailable on macOS, while portscan monitoring is Linux-only and disabled in Docker. The project advises making the configuration file root-owned and writable only by root because the process reads it with root privileges.

Who it suits

OpenCanary suits teams that can self-host a network honeypot and route alerts to their preferred logging or messaging destinations. Linux hosts offer the broadest module options.

Good to know, and what to watch

  • Imitates a range of network-accessible services.
  • Alerts can include source IP and possible breach location.
  • Correlator groups related events into email or SMS.
  • Can run on a Raspberry Pi or small virtual machine.
  • Webhooks support GET, POST, and PUT.
  • SMB monitoring is unavailable on macOS.
  • Portscan monitoring is Linux-only.
  • Portscan monitoring is disabled in Docker.
  • Configuration must be protected from writes by non-root users.

OpenCanary

Free

Free plan

Getting started

  1. Open the project website
  2. Install on Ubuntu or macOS, or deploy Docker on a Linux host using host networking
  3. Choose the service modules to emulate
  4. Configure logging and alert destinations
  5. Make the configuration file root-owned and writable only by root
  6. Start OpenCanary with uid and gid flags if it should drop root privileges after binding ports

Limits to check

The portscan module works only on Linux hosts because it modifies iptables rules, and it is automatically disabled in Docker. SMB monitoring is unavailable on macOS.

The Club's review

OpenCanary is a self-hosted honeypot that imitates network services to flag suspicious interaction on non-public networks. It suits defenders comfortable managing Linux or macOS systems and connecting alerts to an existing response workflow. Its broad set of decoys and alert routes costs nothing, but Linux is the stronger fit for full module coverage.

Overview

Running as a daemon, OpenCanary presents decoy services and alerts when someone interacts with them. Native modules cover SSH, FTP, Git, HTTP and HTTPS, HTTP proxy, MSSQL, MySQL, Telnet, SNMP, SIP, VNC, Redis, TFTP, NTP and TCP banners. Alerts can identify the source IP and offer clues about where a breach may have occurred, giving responders useful starting context rather than just a generic warning.

Its very low resource requirements make it practical to run on a Raspberry Pi or a minimally resourced virtual machine. The software is BSD-licensed and maintained by Thinkst Canary as the open-source counterpart to its commercial honeypot. Self-hosting keeps deployment under the operator’s control, but also means the team must manage the host, configuration and alert delivery.

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, which gives teams a way to send event data to an HTTP endpoint suited to their own workflow. The companion opencanary-correlator can combine related events, such as a series of brute-force login attempts, into one email or SMS alert; that can reduce noise when a decoy attracts repeated activity.

Optional modules extend monitoring beyond service interaction. SMB monitoring watches Samba logs for files opened in a Windows file share, while the portscan module uses iptables to detect scans. These capabilities come with dependencies and platform constraints: SMB monitoring requires Samba, the SNMP module requires Scapy, and portscan monitoring is Linux-only and automatically disabled in Dockerized OpenCanary. Portscan uses iptables rather than nftables, so it is not a fit for hosts relying on nftables for this function.

OpenCanary can be started with uid and gid flags to drop root privileges after binding to its ports. That does not remove the need to secure its configuration: the project recommends making the file root-owned and writable only by root, since a writable configuration can create a privilege-escalation risk.

Pricing

The OpenCanary plan costs nothing. It includes the open-source software for self-hosted deployment, with no paid tier or seat-based charge in this plan. That makes it suitable for teams able to supply and operate their own Linux or macOS host; it is less appropriate for readers seeking a managed service or a vendor-run alerting workflow.

Platforms

OpenCanary supports Linux, macOS and self-hosted deployment, with documented installation on Ubuntu and macOS and Docker deployment on Linux hosts using host networking. Linux offers the widest functionality: the SMB module is unavailable on macOS, and portscan monitoring is Linux-only. Docker is documented, but its portscan module is disabled there, so container deployment gives up that detection option.

Who it's for

OpenCanary is a good match for security teams and technically capable administrators who want lightweight network decoys on infrastructure they control, especially when they can route alerts into existing systems. Its low resource demands also make it viable for small labs or modest virtual machines. It is a weaker choice for teams that need a managed product, broad parity across operating systems, or portscan monitoring on a Dockerized host.

Pros and cons

  • Pros: A wide range of native service decoys helps cover common network-facing targets without substantial host resources.
  • Pros: Multiple alert destinations, configurable webhooks and event correlation support different response workflows and can consolidate repeated events.
  • Pros: Free, BSD-licensed software can run on modest self-hosted hardware, including a Raspberry Pi.
  • Cons: Linux is necessary for the portscan module, and Docker disables it; macOS also lacks SMB monitoring.
  • Cons: Optional modules depend on other software, including Scapy for SNMP and Samba for Windows file-share monitoring.
  • Cons: Operators must secure the configuration file carefully because unsafe write access can enable privilege escalation.

Alternatives

For a broader honeypot software comparison, consider what kind of decoy and deployment you need. Beelzebub is another free, self-hosted option, with API and Linux platform support. Canarytokens offers free tokens through its hosted service and supports web, mobile and desktop platforms, making it an alternative when token-based detection is the better fit.

Cowrie is a free, self-hosted Linux honeypot focused on SSH and Telnet. Honeyd is a free honeypot option for Linux, Windows and self-hosted environments. Heralding is a free, self-hosted Linux honeypot. Honeytrap is another free, self-managed Linux option under Apache License 2.0. T-Pot is a free, open-source self-hosted choice with Linux, macOS and Windows support, subject to hardware and network requirements. Dionaea is a free, self-hosted Linux honeypot under GPLv2+.

Verdict

Choose OpenCanary if you want a free, lightweight, self-hosted way to expose a varied set of network decoys and send useful alerts into systems your team already operates. Its breadth and low resource needs are compelling; look elsewhere if you require managed operation, equal module support across platforms, or portscan detection in Docker.

The verdict

OpenCanary offers a self-hosted way to detect interaction with decoy network services and route alerts to several destinations. Review the platform-specific module limits and protect its configuration file.

Questions people ask

Is OpenCanary free?

Yes. The OpenCanary plan is free, and the project is released under the OSI Approved BSD license.

Where can it run?

It supports Linux, macOS and self-hosted deployment. Docker deployment is documented for Linux hosts using host networking.

Which alert destinations are available?

Documented options include files, Syslog, SMTP email, HTTP webhooks, Slack, Microsoft Teams and HPFeeds-compatible daemons.

Does it provide e-mail or SMS correlation?

The companion opencanary-correlator combines related events into a single email or SMS alert.

Is it open source?

Yes. Thinkst Canary describes OpenCanary as its open-source honeypot, and the PyPI listing identifies it as BSD licensed.

What the maker publishes

Alert channels
The documentation lists Syslog, email, and the opencanary-correlator as alert destinations. source
Alert destinations
Documented logging and alert options include files, Syslog, SMTP email, HTTP webhooks, Slack, Microsoft Teams, and HPFeeds-compatible daemons. source
Alert details
Alerts can identify the threat source IP address and where the breach may have occurred. source
Chat integrations
Webhooks can post to Slack or Microsoft Teams channels. source
Correlator
The companion opencanary-correlator can combine related events into a single email or SMS alert. source
Deployment
The project documents installation on Ubuntu and macOS, plus Docker deployment on Linux hosts using host networking. source
Event correlation
The correlator coalesces multiple related events, such as individual brute-force login attempts, into one alert sent by email or SMS. source
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. source
License
The PyPI listing identifies OpenCanary as OSI Approved BSD licensed software. source
Maintainer and commercial relation
OpenCanary is maintained by Thinkst Canary and described as the open-source version of its commercial Thinkst Canary honeypot. source
Operation
It runs as a daemon implementing multiple common network protocols and sends alerts when attackers interact with it. source
Operation
It runs as a daemon that imitates network services and sends alerts when they are accessed. source
Optional modules
The optional SNMP module requires Scapy, while the Windows File Share module requires Samba. source
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. source
Portscan limit
The portscan module is supported only on Linux hosts because it modifies iptables rules, and it is automatically disabled in Dockerized OpenCanary. source
Privilege handling
When started with uid and gid flags, OpenCanary drops root privileges after binding to its ports. source
Protocol mimicry
It can mimic an array of network-accessible services for attackers to interact with. source
Protocols
Native service modules include SSH, FTP, Git, HTTP, HTTPS, HTTP proxy, MSSQL, MySQL, Telnet, SNMP, SIP, VNC, Redis, TFTP, NTP, and TCP banner. source
Purpose
OpenCanary is a multi-protocol network honeypot intended to catch hackers after they breach non-public networks. source
Purpose
OpenCanary is a multi-protocol network honeypot intended to detect attackers interacting with services on non-public networks. source
Resource needs
The project says it has very low resource requirements and can run on a Raspberry Pi or a minimally resourced virtual machine. source
Resource use
OpenCanary has extremely low resource requirements and can run on a Raspberry Pi or a minimally resourced virtual machine. source
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. source
Security guidance
The project recommends making the configuration file root-owned and writable only by root because writable configuration can allow privilege escalation. source

Checked against the maker's pages on 2 Oct 2026.