managed eggdrop · kire network
We put the bot in the channel.
You don’t compile anything.
No Linux. No Tcl. No “which .conf was it.” Our admins install, harden, and keep it running. You are the owner. DCC, telnet, or just sit in the channel and tell it what to do.
$./what
This is the managed product. If you already compile Eggdrop for fun, that is the shell. This page is for everyone else.
We build it
Install, config, ident, vhost, the boring parts. You pick nick, network, and channels at order time.
You are the owner
DCC chat, telnet to the bot, or talk to it on IRC. Add users, channels, scripts. Change it later. You are not locked into the order form.
Vanity PTR included
The bot shows up as something amusing, not dhcp-12.isp.net. Same pool as the rest of KIRE.
DDoS in front
Channel fights still involve packets. The filter sits in front of the bot, not as a footnote after it drops.
TCL without the compiler
Trivia, custom scripts, the usual channel toolkit. Tell us what you want loaded. You do not have to know where tclsh lives.
The actual job
Auto-op, kick/ban lists, flood protection, takeover protection. The reason people still run Eggdrop.
$./why
You wanted a bot, not a VPS
Compiling Eggdrop is a weekend for some people. For everyone else it is how the channel dies on a Tuesday.
Userfile restores are our problem
Disks die. Processes stop. We run the machine. You run the channel.
Not a toy “IRC bot” app
Partyline, userfile, TCL, the real thing. You can grow into it. You do not have to start there.
It sits on KIRE
Same DDoS, same vhosts, same people who have been doing this since 1997. The domain is eggdrops. The backbone is not a surprise.
$whois eggdrops
KIRE’s managed Eggdrop offering. Order, tell us the nick and the channel, wait for it to join. Typically the same business day. Then you own it.