The Lounge

Self-hosted IRC for people who want IRC without the always-offline problem. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: MIT-licensed, self-hosted web IRC client that acts as a bouncer and client in one — your connection to IRC networks stays alive on the server even when your browser is closed [3].
• Who it’s for: Developers, open-source contributors, and privacy-conscious teams who live in IRC communities and are tired of missing conversations while offline [1][4].
• Cost savings: IRCCloud (the main SaaS alternative) charges for persistent connections. The Lounge runs free on a $5–10/mo VPS with no per-user or per-connection fees.
• Key strength: Genuinely modern interface on top of an ancient protocol — push notifications, link previews, PWA install, synchronized read position across devices, all with no desktop client required [3].
• Key weakness: No web UI for user management — adding accounts requires CLI commands. No DCC file transfer support. The project’s last active release period suggests it’s in maintenance mode rather than active development [4][5].

---

What is The Lounge

IRC has a structural problem: when you close your laptop, you disconnect from the network. Every channel message, every mention, every decision made in a developer channel while you were asleep — gone. Traditional solutions involve running a bouncer like ZNC on a server, then pointing a desktop client at it. That’s two pieces of software to configure, two failure points, and zero mobile support worth mentioning.

The Lounge solves this by combining the bouncer and the web client into a single Node.js application. You deploy it on any server that stays online. It maintains persistent connections to IRC networks continuously. You access it from any browser, on any device, and pick up exactly where you left off — full history, synchronized read markers, push notifications when someone says your nick [README][3].

The project describes itself as “a modern web IRC client designed for self-hosting” and is the official community-managed fork of Shout, an earlier project by Mattias Erming [README]. It sits at 6,194 GitHub stars and is MIT-licensed — meaning you can self-host, fork, or adapt it freely without commercial restrictions [README].

Two operating modes exist. Private mode — the one most self-hosters use — gives each user their own persistent IRC connections and logged history, behaving like a combined bouncer and client. Public mode opens it as an anonymous, registration-free web chat, useful for running a community chat room but with no persistent history per user [3].

---

Why people choose it

The core argument for The Lounge appears consistently across every source: IRC is irreplaceable for certain communities, but running a traditional IRC client on a personal machine makes you effectively invisible to those communities outside business hours.

From the Hostinger deployment guide: “Open-source contributors stay connected to project IRC channels around the clock, catching up on discussions that happened in different time zones without running a separate bouncer.” [1] This is the actual use case. Libera.Chat, OFTC, and private IRC networks for projects like major Linux distros, Python libraries, and open-source databases are still active. If you’re a contributor, you need presence.

The personal account from Thejesh GN [4] is the most honest: “If you are not online, you will miss the chats. So your desktop machine needs to be online all the time to capture those messages and save them for you. Or you need to use a hosted chat client service that is always connected.” His solution was installing The Lounge on a Synology NAS — the kind of always-on hardware that makes a cheap self-hosting platform. He notes the Synology Docker setup itself was smooth, though user creation required manual file editing (more on that under deployment).

The DANIAN managed hosting article [3] frames the appeal well: “Proprietary chat platforms explicitly restrict your access, aggressively limit your message history, and dictate exactly how you communicate.” For teams already using IRC who don’t want to migrate to Slack or Discord, The Lounge is the path of least resistance to modern usability without giving up self-hosted control.

The ElfHosted listing [2] positions it alongside a broader self-hosted stack, which suggests The Lounge is typically deployed alongside other infrastructure rather than as a standalone tool. People who are already running Jellyfin, Sonarr, and similar services on a home server are the natural adopters.

---

Features

Based on the README and independent deployment guides:

Core IRC experience:

• Always-on connections — the server maintains IRC presence regardless of browser state [README][3]
• Full message history with synchronized read markers across devices [README][1]
• Multiple simultaneous IRC network connections in one interface [1]
• Full-text search across message history [1]
• SASL and client certificate authentication for secure IRC connections [1]
• Automatic away message management [1]

Modern interface:

• Push notifications for mentions and highlights on desktop and mobile [README][1][3]
• Link previews with image, video, and media thumbnails [README][3]
• File upload and image sharing within channels [README][1]
• Responsive design that works on desktop, tablet, and smartphone [README][1]
• Progressive web app (PWA) — installable from any modern browser for a native-like feel [3]
• Customizable themes [1]
• Keyboard shortcuts [1]

Multi-user and access control:

• Multiple user accounts with separate IRC configurations and history [README][1]
• LDAP authentication for enterprise or team deployments [1]
• Nick and channel password management [1]
• Configurable notification rules and filters [1]

What’s missing:

• No DCC file transfer support [5] — a real limitation for anyone using IRC for file sharing
• No web UI for adding users — account creation is CLI-only [4]
• No built-in mobile app — the PWA is the mobile story

---

Pricing: SaaS vs self-hosted math

The Lounge itself is free software. There’s no cloud tier with a paywall and no commercial license to buy. The cost conversation is about infrastructure and what you’re replacing.

The paid alternative: IRCCloud IRCCloud is the most direct SaaS comparison — a hosted, always-on IRC client with message history and mobile apps. Pricing data from IRCCloud’s website was not available in the provided sources, but source [4] names it explicitly as the service The Lounge replaces: “There are some excellent providers like IRCCloud. They are always connected to IRC channels and save the messages for you.” The existence of a thriving market for managed The Lounge hosting (Hostinger [1], ElfHosted [2], DANIAN [3]) confirms that self-hosted The Lounge is price-competitive with paid IRC hosting services.

Self-hosted cost:

• The Lounge software: $0 (MIT license)
• Minimum VPS to run it: $5–10/mo (Hostinger’s listed entry plan is $8.99/mo [1]; Hetzner and Contabo run cheaper)
• Your time to install and maintain it: see deployment section

Managed hosting (if you don’t want to self-host):

• ElfHosted offers hosted The Lounge as part of their service [2]
• DANIAN offers managed hosting with a 7-day free trial [3]
• These options make sense if you want the always-on benefit without touching a server

Concrete math: The Lounge isn’t replacing a $100/mo Zapier bill. It’s replacing a $5–15/mo IRC bouncer/hosting subscription, or more importantly, replacing the productivity cost of missing conversations because your laptop was closed. For teams making real decisions in IRC channels, that second cost is the actual number.

---

Deployment reality check

The Lounge runs on Node.js and supports Docker deployment, which is the recommended path [README][1]. The project provides a dedicated Docker image at thelounge/thelounge-docker.

What you actually need:

• A VPS or always-on server (even a Synology NAS works [4])
• Docker installed, or Node.js LTS if you prefer native
• A reverse proxy (Caddy or nginx) for HTTPS if you want it accessible from outside your home network
• A domain or dynamic DNS if you want mobile access outside your LAN

What can go sideways:

The most significant pain point documented across the sources is user management. The Lounge has no web UI for creating user accounts. You must use CLI commands (thelounge add <username>), which means SSH access to your server every time you add someone new. On Synology NAS, Thejesh GN [4] had to go further: “I created the user [in a local Docker instance]. Copied this username.json and uploaded it to the correct path on Synology NAS docker volume. Restarted the docker on the Synology.” This is not a deal-breaker for a single-user or small team setup, but it’s friction that modern tools have eliminated.

The Reddit thread [5] documents a hard limitation: no DCC file transfer support. The poster explicitly installed The Lounge, loved it, but had to keep looking because DCC receives were essential to their workflow. This is the kind of thing you don’t discover until after deployment.

Development activity concern: The GitHub stars (6,194) are respectable, but the repository shows signs of reduced active development pace. The website still describes the project accurately, but there hasn’t been a major feature release cycle in some time. For a communication tool, this matters — IRC protocol is stable, so “maintenance mode” is arguably fine, but prospective users should check the GitHub issues and last commit dates before betting critical workflow on it.

Time estimate for technical users: 30–60 minutes to a working instance on a VPS with Docker. Add HTTPS + domain: another 30–60 minutes. For a Synology or NAS setup: 1–2 hours including the user creation workaround [4].

---

Pros and Cons

Pros

• MIT license. No restrictions, no commercial gotchas, no Fair-code ambiguity. Fork it, embed it, run it for a team without asking anyone’s permission [README].
• Genuinely solves the IRC offline problem. The bouncer-plus-client architecture is the right solution to the right problem. If you use IRC seriously, this is the tool that makes it practical [3][4].
• Modern interface that doesn’t look like 2003. Push notifications, PWA install, responsive design, link previews — these aren’t afterthoughts [README][1][3].
• Multi-network support. Libera.Chat, OFTC, private networks — all in one interface [1].
• Runs on minimal hardware. A Synology NAS, a $5 VPS, a Raspberry Pi — if it runs Node.js and stays online, it runs The Lounge [4].
• LDAP support. If you’re running a team deployment with centralized authentication, this matters [1].
• PWA works well on mobile. No separate app needed; install from browser, get push notifications, done [3].

Cons

• No web UI for user management. CLI-only account creation is an unnecessary friction point for anyone who isn’t comfortable with SSH [4].
• No DCC file transfer. If your IRC usage involves receiving files over DCC, this is a hard blocker [5].
• Development pace is slow. The project appears to be in maintenance mode. Security patches likely continue, but major new features are not on an active roadmap.
• Node.js dependency. On some NAS hardware or older VPS images, getting the right Node.js LTS version can be fiddly. The Docker path avoids this but adds its own surface area [README].
• Public mode has no persistent history per user. If you want an open community chat room with history, you’re better served by Matrix/Element [3].
• No REST API. Limited options for programmatic integration or bot management via the web client itself.

---

Who should use this / who shouldn’t

Use The Lounge if:

• You’re an open-source contributor or developer who participates in IRC communities on Libera.Chat, OFTC, or similar networks, and you’re tired of missing conversations while offline.
• You have a VPS or NAS that stays online and you’re comfortable with basic Docker commands or SSH.
• You want an MIT-licensed tool you can run for a small team without per-seat licensing.
• You’re replacing IRCCloud or a ZNC bouncer setup and want a cleaner web interface on top.

Skip it if:

• You do DCC file transfers — there’s no support [5].
• You need a web UI for managing users — you’ll be fighting the CLI setup repeatedly [4].
• You’re looking for a modern team chat platform. The Lounge is an IRC client, not a Slack replacement. If your team doesn’t already use IRC, don’t start with The Lounge.
• You need guaranteed active development and security patch cadence — check the GitHub commit history before committing.
• You’re not already in IRC communities. The switching cost from Slack or Discord to IRC just to use The Lounge makes no sense.

---

Alternatives worth considering

• ZNC — the traditional IRC bouncer. Pairs with any desktop or mobile IRC client. More configuration surface area, no built-in web client, but extremely battle-tested. Use ZNC if you prefer a native IRC client on desktop.
• WeeChat — terminal-based IRC client with a relay plugin that enables web access. Mentioned by the r/selfhosted Reddit thread [5] as a The Lounge alternative, though noted as “a bit complicated as it needs multiple other extensions.”
• IRCCloud — the paid SaaS alternative. Managed, mobile apps, solid history, no server to run. Pay for what The Lounge gives you free, but skip the deployment entirely [4].
• Quassel IRC — another self-hosted bouncer-plus-client setup. Uses a desktop client instead of web, more mature multi-user support, but the web interface (Quasseldroid/Quassel-web) is less polished.
• Matrix/Element — if you’re not tied to IRC specifically, Matrix is the modern federated alternative with proper room history, end-to-end encryption, bridges to IRC and Slack, and an actively developed client. Heavier to self-host, but if you’re building a new community rather than participating in an existing IRC one, Matrix is the better bet.
• Soju — newer IRC bouncer with multi-client support and a simpler deployment model than The Lounge, but no built-in web client.

For someone already embedded in IRC communities: The Lounge vs ZNC+native-client is the main choice. The Lounge wins on mobile and convenience. ZNC wins on flexibility.

---

Bottom line

The Lounge does one thing — keeps you connected to IRC and gives you a modern web interface to it — and does it well. The MIT license, the PWA mobile support, and the zero-per-user-cost model make it the right tool for developers and open-source contributors who live in IRC channels and need that connection to survive their laptop closing. The pain points are real: no web UI for user management, no DCC support, and a development pace that suggests the project is coasting rather than growing. But IRC itself isn’t growing either, so “maintenance mode that works reliably” might be exactly what this tool needs to be. If you’re already paying for IRCCloud or running a brittle ZNC setup, a one-afternoon deployment on a cheap VPS gives you the same always-on experience with no recurring subscription. If you’ve never touched IRC and are looking for a modern team chat, this is not your tool.

If deployment is the blocker, that’s exactly what upready.dev handles for clients — one-time setup, you own the infrastructure.

---

Sources

1. Hostinger — “The Lounge VPS Docker | Self-Hosted IRC Client”. https://www.hostinger.com/vps/docker/the-lounge
2. ElfHosted — “Hosted The Lounge - Cloud IRC Client”. https://elfhosted.com/app/thelounge/
3. DANIAN — “Managed The Lounge Hosting: Never Miss a Message”. https://danian.co/articles/post/managed-thelounge-hosting
4. Thejesh GN — “Self-hosted, Always Connect IRC client on Synology” (June 4, 2021). https://thejeshgn.com/2021/06/04/self-hosted-always-connect-irc-client-on-synology/
5. r/selfhosted — “self hosted web based IRC client that supports DCC file transfers”. https://www.reddit.com/r/selfhosted/comments/19b0ycg/self_hosted_web_based_irc_client_that_supports/

Primary sources:

• GitHub repository and README: https://github.com/thelounge/thelounge (6,194 stars, MIT license)
• Official website: https://thelounge.chat
• Documentation: https://thelounge.chat/docs
• Live demo: https://demo.thelounge.chat/