The Economics of Running an IRC Network in 2024

I've been paying for IRC infrastructure out of pocket since 2001. First it was a shell account on someone else's server. Then a dedicated box at a French datacenter. Then multiple VPS across three countries. At peak, our network had about 4,000 concurrent users across six servers. I can tell you exactly what it cost, because I tracked every invoice. What nobody talks about in IRC tutorials is the money. So let's talk about it.

The Real Question Nobody Asks

Before diving into line items, understand the real question: can you sustain this for years? IRC networks aren't projects you launch and move on from. Users build communities. Channels become meeting points. People depend on your infrastructure being there tomorrow. If you start a network and shut it down 18 months later because you can't afford it, you've disrupted dozens or hundreds of people's social spaces.

I've watched at least 20 networks die because the founder underestimated costs or overestimated their own patience. The technical setup is the easy part. The hard part is paying the bills year after year when enthusiasm fades.

Plan your budget for a minimum of three years. If you can't commit to that, run a channel on someone else's network instead.

Hosting and Server Costs

An IRC server is not resource-intensive. A single UnrealIRCd or InspIRCd instance handling 500 concurrent users uses maybe 200 MB of RAM and negligible CPU. You don't need powerful hardware. What you need is reliable hosting with good network connectivity.

Here's a realistic tier breakdown as of late 2024:

For a small network, a single Hetzner Cloud CX22 (2 vCPU, 4 GB RAM, 40 TB traffic) at about 4 EUR/month is more than enough. The IRCd, services, and a ZNC bouncer for staff can all run on one box. I ran a 200-user network on less hardware than a Raspberry Pi 4 for three years.

# Typical small network stack on one server
# OS: Debian 12 minimal
# IRCd: InspIRCd 4.x
# Services: Atheme
# Bouncer: ZNC (for staff)
# Web client: The Lounge
# Monitoring: simple systemd watchdog

# Memory usage (approximate)
# inspird:     ~50 MB (200 users)
# atheme:      ~15 MB
# znc:         ~30 MB (5 users)
# thelounge:   ~100 MB (10 users)
# Total:       ~200 MB, well within 4 GB VPS

When you grow beyond a single server, you need multiple locations. Having two servers in the same datacenter doesn't help much — a fiber cut or datacenter power event takes both down. Put your second server in a different city, ideally a different country. For European networks, I recommend one server in Germany (Hetzner or Netcup), one in France (OVH), and optionally one in the Netherlands or Finland.

Bandwidth: The Hidden Variable

IRC is text. The bandwidth per user is tiny — maybe 1-5 KB/s during active chatting. A 500-user network with 50 active channels generates perhaps 50-100 GB of traffic per month. Most VPS plans include far more than that.

Where bandwidth becomes a cost factor:

• Server-to-server links: If you have four linked servers, every message on every channel gets relayed to every server. The inter-server traffic scales with the number of servers and channels, not just user count.
• DDoS attacks: Even with mitigation, volumetric attacks consume bandwidth. Some providers charge for attack traffic that reaches your server before mitigation kicks in.
• File services: If you run DCC or file hosting through The Lounge, file transfers add up.

In practice, bandwidth is rarely the bottleneck for IRC. The 40 TB included with a Hetzner VPS is 100x what a mid-sized network needs. But read your provider's terms carefully — some "unlimited" plans throttle after certain thresholds.

DDoS Protection: The Expensive Reality

This is where the budget gets serious. IRC networks are magnets for DDoS attacks. Script kiddies, disgruntled users, botnet operators testing their tools — if your network has more than a few hundred users, you will get attacked. It's not if, it's when.

I first got DDoSed in 2004. A 400 Mbps UDP flood knocked our server offline for two days. The hosting provider threatened to null-route us permanently. That was a wake-up call. Since then, I've dealt with attacks ranging from simple SYN floods to sophisticated application-layer attacks targeting the IRC protocol directly.

DDoS protection options in ascending order of cost:

Free tier: Some providers include basic DDoS protection. OVHcloud's included anti-DDoS is decent for volumetric attacks up to a few Gbps. Hetzner has basic protection too. This handles casual attacks but not targeted ones.

Mid tier (20-100 EUR/month): Services like Path.net or BuyVM's DDoS-protected VPS offer better mitigation. Path.net is popular in the IRC community specifically because they understand IRC traffic patterns. A standard web-focused DDoS provider might block legitimate IRC connections during mitigation.

Premium tier (100-500+ EUR/month): Dedicated DDoS mitigation with GRE tunnels or a filtered IP range. This is what large networks use. You route your traffic through the mitigation provider, they filter it, and clean traffic reaches your servers. Companies like Voxility or custom setups with Cloudflare Spectrum fall here.

# Budget example: 1000-user network with DDoS protection
# 3x VPS (Hetzner CX22)      : 3 x 4 EUR  =  12 EUR/month
# DDoS protection (Path.net)  : 1 x 30 EUR =  30 EUR/month
# Domain name                 : 1 x 1 EUR  =   1 EUR/month (amortized)
# Total                       :               43 EUR/month
#                             :              516 EUR/year

TLS Certificates and Domain Names

TLS is mandatory for any modern IRC network. Users expect encrypted connections. Services like NickServ transmit passwords. Without TLS, those passwords cross the internet in plaintext.

Thanks to Let's Encrypt, TLS certificates are free. Renew them with certbot every 90 days via cron. The only cost is the domain name itself — typically 8-15 EUR/year for a .net or .org domain.

# Automated Let's Encrypt certificate renewal for IRC
# Crontab entry
0 3 * * 1 certbot renew --deploy-hook "systemctl reload inspircd" 2>&1 | logger -t certbot

# InspIRCd TLS configuration

If you need wildcard certificates (for *.irc.example.net with multiple server hostnames), Let's Encrypt supports those via DNS-01 challenge. This requires DNS API access with your registrar.

Some networks use multiple domain names — one for the network identity and separate ones for individual servers (e.g., hub.eu.example.net, leaf.us.example.net). Each needs its own certificate or you use a wildcard. Plan your naming before setting up TLS.

Admin Time: The Biggest Cost

Here's the cost nobody includes in their budget: your time. Running an IRC network is a volunteer job for most of us. But time has value, and the time commitment is not trivial.

Weekly admin tasks for a mid-sized network:

• Monitoring: Checking server health, disk space, certificate expiry — 30 min/week
• User support: Password resets, channel disputes, ban appeals — 1-3 hours/week
• Abuse handling: Investigating spam bots, drone networks, flood attacks — 1-2 hours/week
• Updates: OS patches, IRCd updates, services updates — 1-2 hours/month
• Community management: Talking to channel founders, mediating disputes — 1-2 hours/week

That's 4-8 hours per week for a network with a few hundred active users. For larger networks, it's a part-time job. At peak, I was spending 15 hours a week on network administration. That's unpaid labor that I could have billed at my consulting rate.

The solution is delegation. Build a staff team. Find reliable people who care about the community and give them operator access. Document your procedures so others can handle routine tasks. If you're the only person who can restart the IRCd or renew certificates, you can never fully disconnect.

For organizations that need professional IT infrastructure management — whether for IRC or broader web projects — working with a managed services provider can make sense. Companies like Koeki specialize in web infrastructure and digital strategy for small organizations, handling the technical overhead so you can focus on your community.

Donations and Sustainability

Most IRC networks run on donations. The standard model: put a page on your website explaining costs, accept PayPal or bank transfers, and hope enough people contribute. Some networks are more organized — they register as nonprofit associations (in France, an "association loi 1901" works well for this) and issue receipts.

Realistic donation expectations:

• A network with 200 active users might get 5-10 donors
• Average donation: 5-20 EUR
• Annual donation income: 100-400 EUR for a small network
• This covers basic hosting but probably not DDoS protection

Alternative sustainability models I've seen work:

Sponsored servers: A company or university donates a server. This is common for larger networks. Libera.Chat runs entirely on donated infrastructure. The downside: if the sponsor leaves, you lose the server.

Bouncer as a service: Offer ZNC accounts on network infrastructure for a small monthly fee (2-5 EUR). This isn't a money-maker but can offset hosting costs. Users get a bouncer, you get recurring income.

Founder funds it personally: This is the most common model for networks under 500 users. One or two people pay the bills. It works until they can't or won't anymore. If this is your model, have a succession plan. What happens to the network if you stop paying?

# Example donation page content (be transparent)
# Monthly costs:
# - 3 servers (Hetzner): 36 EUR
# - DDoS protection: 30 EUR
# - Domain renewal: 1 EUR (amortized)
# - Total: ~67 EUR/month, ~800 EUR/year
#
# Current coverage: 45% from donations
# Shortfall covered by: network founder

Transparency helps. People donate more when they can see exactly where the money goes. Publish your costs. Show what's covered and what isn't. Some networks publish quarterly financial reports — simple spreadsheets showing income vs expenses. It builds trust and encourages contributions.

Whatever model you choose, never let the network depend on a single point of financial failure. If one person stopping their 50 EUR/month donation kills the network, your funding model is too fragile. Diversify your income sources or reduce your costs to match what you can reliably fund long-term.