The IRC session keeper

Your nick stays online.
Your client comes and goes.

Session Keeper — an IRC bouncer — stays connected to the networks you choose, around the clock. It holds your nickname, identity and channels, buffers every message you miss, and plays it back the moment your client returns.

Open the web admin What it does Read the full guide

24/7

Always online

The keeper stays connected to your IRC networks and keeps your nickname, identity and channels — client attached or not.

Nothing lost

Buffers & playback

Channel and query history is buffered while you're away and replayed with the original timestamps. Optional module keeps it on disk, encrypted.

One nick,
many clients

Every client, one session

Attach several IRC clients at once; replies and events travel to the client that asked for them.

Away, handled

Away when offline

When your last client detaches, the keeper marks you away with your message — and clears it the moment one returns.

IRCv3

Negotiated end to end

server-time, batch, chathistory, monitor, echo-message and a whole shelf more — with your client and the upstream server.

CR-AVATAR

Emoji profiles

On networks with the ConferenceRooms avatar extension, users' emoji avatars are relayed live to capable clients — no WHOIS polling.

Built-in automation

Signs you inNickServ handshakes and upstream SASL happen automatically — your credentials live in the keeper, not in every client.

Retakes your nickIf someone sits on your nickname, the keeper watches and claims it the second it frees up.

Rejoin protectedKicked from a channel? The keeper rejoins after your own delay instead of leaving you behind.

Replies for youAn automatic reply for private messages while you're away or disconnected — the text is yours, substitutions included.

Abuse ShieldRate guards keep floods from reaching you or getting the upstream link dropped: outgoing throttles, join delays and CTCP limits.

DCC relayedDirect-client chats and file transfers pass through the keeper — nothing exposes your real address — and incoming files are stored until a client attaches.

Speaks IRCv3

Negotiated per client and per upstream server — a capable client gets the full modern surface, a plain client still sees everything it needs.

server-time batch labeled-response chathistory draft/read-marker monitor sasl away-notify account-notify extended-join echo-message setname chghost multi-prefix userhost-in-names message-tags message-ids standard-replies draft/multiline draft/event-playback draft/channel-rename

+draft/reply +draft/react +draft/typing client tags pass through, CHATHISTORY serves your keeper history locally, and MARKREAD keeps the read marker in step across every attached client.

CR-AVATAR emoji profiles

On an upstream network that implements the ConferenceRooms avatar extension, each identified user can carry a small emoji avatar and display name.

The keeper negotiates conferencerooms.org/avatar when the server offers it, then hands one AVATAR message for every visible user to capable clients — a burst right after each NAMES and live updates — and replays the ordinary WHOIS line for plain clients. Nothing is stored; the cache lives in memory and clears the moment the upstream link drops.

Online in three steps

1 — Create the accountSign up in the web admin and let the recommended setup fill in the sensible defaults.

2 — Add the networkName it and give the upstream server — +irc.example.net 6697, the plus meaning TLS — then join the channels you want kept.

3 — Point your clientSet the client's server to irc.sessionkeeper.chat, port 6697 with TLS, and account/network:password where the password used to go. Close it whenever you like; the keeper holds the line.

Never miss a line again.

Build the account, point a client at it — and let Session Keeper keep the session alive on every network you care about.