Learn what ZNC, the free open-source IRC bouncer, offers: persistent connections, multi-client support, modules, SSL, and how to self-host it.
ZNC is a free, open-source IRC bouncer that maintains a persistent connection to IRC networks so users never lose their place in a conversation or their nickname, even when their own client goes offline.
Written in C++, the project's history dates back to its first commit in July 2004, and it has remained an actively maintained open-source project since, now hosted on GitHub under the znc/znc repository.
ZNC is released under the Apache License 2.0, making it free to download, self-host, and modify with no commercial licensing fees.
ZNC stays connected to configured IRC networks and channels at all times, buffering messages per channel so that when a user's client reconnects, they can replay everything they missed while disconnected.
Multiple client connections, from a phone, laptop, or desktop, can attach to the same ZNC account simultaneously and appear as one continuous presence on IRC under the same nickname.
The tool includes a built-in web interface, support for multiple user accounts on one instance, transparent DCC bouncing for file transfers, and native SSL/TLS and IPv6 support. Its functionality can be extended with modules written in C++, Python, Perl, or Tcl, including community modules for push notifications and logging.
ZNC is entirely free and open source under the Apache License 2.0, with no paid tiers or commercial edition.
The only cost associated with running ZNC is the infrastructure needed to host it, typically an always-on server or virtual private server.
Support comes from the open-source community through GitHub, the project wiki, and IRC channels rather than a paid support plan.
ZNC is used as an IRC bouncer, keeping a persistent connection to IRC networks so a user stays connected and can reconnect from multiple devices without losing channel history.
Yes, ZNC is completely free and open source under the Apache License 2.0.
Yes, ZNC is a self-hosted application typically run on an always-on server or virtual private server.
Yes, a single ZNC instance supports multiple separate user accounts, each with its own configuration.
ZNC modules can be written in C++, Python, Perl, or Tcl.
Yes, ZNC automatically supports SSL/TLS connections when the host system has OpenSSL installed, along with IPv6.
ZNC's first commit dates back to July 2004, making it one of the longest-running IRC bouncer projects still actively maintained.
Yes, ZNC includes a built-in web interface for configuration and administration.