Tools/ergochat/ergo

ergo

A modern IRC server (daemon/ircd) written in Go.

3.3kemergingGoMIT Licensetrending

The Lens

By Erik Loyd, SaaS CEO and former COO/CFO of an AWS Premier Partner.

Updated Aug 2026

Ergo is an IRC server that ships with the parts you used to bolt on yourself. A traditional setup means an ircd, a separate services package for nickname and channel registration, and a bouncer per user so nobody loses scrollback when they close the laptop. Ergo is one Go binary covering all three. MIT, free, no paid edition.

Setup is a binary and a YAML file that rehashes at runtime, so most config changes never drop a connection. History sits in memory by default; point it at MySQL, PostgreSQL, or SQLite to survive restarts. TLS, SASL, bcrypt password hashing, and host cloaking are built in. A small VPS runs it fine.

Solo and small private groups: cheapest self-hosted chat you can stand up in an evening. Teams already on IRC: the built-in bouncer alone justifies dropping ZNC. Anyone shopping for a Slack replacement wants mattermost/mattermost, zulip/zulip, or RocketChat/Rocket.Chat instead.

The catch is IRC. No threads, no file uploads, no reactions you can count on, and what each person sees depends on the client they picked. Ergo modernizes the protocol as far as IRCv3 allows and stays honest about the ceiling. Watch the security releases: the August 2026 patch fixed an account verification bypass.

Free vs Self-Hosted vs Paid

fully free

Free

Everything. MIT license, no paid edition, no hosted service, no gated features. The ircd, the services layer (NickServ and ChanServ), the bouncer with history replay, always-on clients, TLS, SASL, cloaking, and Tor hidden service support all ship in the same binary.

Paid

Nothing to buy. No commercial support contract, no enterprise build, no cloud tier.

Self-Hosted Costs

A $5 to $6 per month VPS handles a private server for a few dozen users. In-memory history is free but disappears on restart; SQLite persistence is free and local, and managed Postgres runs about $15 a month if you would rather not operate one. Budget an hour for the initial YAML config and about 15 minutes per security release, which is not optional here.

When to Pay

Never, because there is no vendor to pay. Put the money into managed Postgres and into someone actually watching the release feed.

Free forever with no vendor and no paid tier; the only real cost is a small VPS and the discipline to apply security releases.

What to do by team size

Solo
free; one binary and a YAML file on a $5 VPS
Small team
free; add SQLite or Postgres history so nothing vanishes on restart
Medium team
free, but budget time for TLS, spam controls, and staying current on security releases
Large team
free is not the problem, IRC is; mattermost/mattermost or zulip/zulip fit a large org better
Self-hosting ops:moderate

Get tools like this every Wednesday

One featured tool, three on the radar. No fluff.

Score
74/100 · B+
Adoption17/30
Maintenance25/25
Community7/20
License15/15
Analysis10/10

A low score is not a verdict on quality. Young and niche tools start low by design. How we calculate scores

Trust Signals

Organization account (17 public repos)

License: MIT License

Use freely, including commercial. Just keep the license.

Commercial use: ✓ Yes

About

Owner
ergo.chat (Organization)
Stars
3,302
Forks
241

Explore Further

More tools in the directory