English
InspIRCd Hosting
InspIRCd is a modular IRC daemon whose container image accepts chat clients on the usual plaintext port and on the TLS port.
- One click deploy
- 15 GB Disk Space Needed
- 1 GB RAM Memory needed
- From 2 € Price
No setup fees
Official links
InspIRCd’s official links and original website
- Go to Repository
InspIRCd GitHub
- More
InspIRCd Website
What you get
on AvaHost
One-click deployment, a custom domain, free HTTPS, automatic application updates, and scheduled backups come with every Cloud App. You can run multiple apps on one server, and terminal access is included.
This template does not include a database container.
Tech
- Docker image
- inspircd/inspircd-docker:latest
- Default port
- 0
How InspIRCd works
InspIRCd is a modular IRC daemon. The Docker image documented by the project is inspircd/inspircd-docker. Its default client ports are 6667 for plaintext and 6697 for TLS. Server linking uses 7000 and 7001 in that same table. The image can generate a self-signed certificate on start when none is mounted, and it can take a TLS common name from the environment. Operator password hashes and services passwords are environment values you set. There is no bundled services package and no requirement for PostgreSQL or MariaDB in the default container.
Clients connect to a hostname and a port. A website on 443 is optional and is not the chat session. If you publish plaintext 6667 on the public internet, you are choosing a risk the Ergo manual, for a different ircd, argues against. InspIRCd will do it because the image exposes the port. Prefer 6697 with a real certificate for anything beyond a private test.
Key InspIRCd features
Modules cover extra commands, filtering, and linking behaviour. You enable what the network needs and you read the module list rather than assuming a fixed feature set. Services, if you want nick registration, are a separate project you connect with the password the image can be given. The container is officially discussed around Docker 17.06 and later in its README. A current Docker engine is what AvaHost runs. Treat the old version line as upstream's historical support note, not as a pin.
AvaHost updates the image automatically and backs up the configuration and any persisted data on a schedule. A dedicated public IP is required so clients have a stable address for 6697. Application mail is not included with InspIRCd. Linking two servers is your design. This page does not build the link for you.
InspIRCd vs UnrealIRCd
InspIRCd
InspIRCd and UnrealIRCd are both long-lived modular ircds with different module names, config syntax, and release trains. Pick UnrealIRCd when your operators already know it or you want its specific modules. Pick InspIRCd when this daemon and its Docker port map are the one you intend to run.
UnrealIRCd
Ergo, also available here, is a different kind of server, with accounts inside the ircd. It is not the comparison for people shopping classic modular daemons.
Who uses InspIRCd
IRC communities and private company networks that still want a classic daemon use InspIRCd. It is a poor fit if you wanted built-in accounts and you have not planned a services package, and it is a poor fit if port 6697 cannot be published on a public address.
Self-hosting InspIRCd: requirements and cost
The baseline is 512 MB of RAM and half a CPU core, image inspircd/inspircd-docker, no separate database container. On AvaHost the recommended minimum for InspIRCd is Plan 1 at €2. The InspIRCd package includes one-click deployment, a hostname, automatic updates, and scheduled backups. Automated HTTPS covers a browser page if you add one. IRC clients use 6697. This deployment requires a dedicated public IP so those listeners sit on a stable address.
F.A.Q
InspIRCd starts at €2 on Plan 1. The price is the daemon and its config, not a services package and not a web client. A large channel list, lots of history bots, or several linked servers can need more RAM. User client apps are not part of the plan.
Give them the hostname and port 6697 with TLS. Point that name at the dedicated address. A certificate on a website port does not answer IRC. You set the operator hash and you decide if 6667 is published at all. DNS stays in your control.
AvaHost updates InspIRCd automatically and backs up the config you persist, on a schedule. After an update, connect a client and confirm an operator can still authenticate. If you mounted your own certificate, keep a copy of it outside the container. Module choices you made in the config should be in that backup.
Yes. Clients need a stable public endpoint for the IRC ports, especially 6697. AvaHost requires a dedicated public IP on this package for that reason. The address does not install services or choose your operator password. Server-link ports should stay closed until you actually link a second server.