Convos Hosting
Stay connected to IRC networks through a responsive, persistent web chat client.
- One click deploy
- 1 GB RAM Memory needed
- 15 GB Disk Space Needed
- From 2 € Price
Official links
Convos’s official links and original website
Convos Website
More
Tech
- Docker image
- nordaaker/convos:latest
- Default port
- 3000
How Convos works
Convos connects from the hosted server to IRC networks and presents channels, private messages, mentions, search, media previews, and settings through a responsive web interface. Its server-side bouncer remains connected when a browser closes, recording activity that the user can review later. This model reduces missed channel context and lets the same session continue across desktop and mobile browsers.
Users still need an IRC network and any required network account. Convos does not create a new IRC service, grant channel permissions, or control remote moderation. The hosted package stores configuration, logs, and uploaded material in its application data. External networks can impose connection limits, account requirements, bans, or policies that affect the service even when Convos itself is running correctly.
Key Convos features
Convos supports multiple connections and can display rich media or link information alongside IRC text. It also includes video-chat functionality that depends on browser, network, and participant conditions. Message archives may contain sensitive conversations, account names, host information, and uploaded files, so user access and backup handling deserve the same care as the live chat session.
The catalogue does not pre-create user credentials. Administrators should complete the first account workflow through the application and verify that registration or account creation matches the intended audience. Application email is disabled, so any feature depending on email delivery cannot be assumed to work. A public registration setting should be reviewed before the address is shared.
Who uses Convos
Project communities keep support-channel history available, IRC regulars move between laptop and phone without disconnecting, and small trusted groups use one server-side client for several networks. The persistent bouncer is useful when local connectivity is intermittent or when a member wants to review messages received while their browser was closed.
Convos is not an end-to-end encrypted team messenger, an IRC network, a moderation service, or a guarantee that history exists before the bouncer joined. Remote servers and channel operators remain authoritative. People sharing an installation should understand who can create accounts and how long logs and uploads are retained.
Self-hosting Convos: requirements and cost
Convos resource use depends on users, IRC connections, joined channels, message volume, archived history, media previews, uploads, video-chat activity, and concurrent browsers. PostgreSQL and MariaDB are Not required in the catalogue template; the application uses its own persistent data. Quiet personal use is light, while active communities and long message archives can increase storage and ongoing connection work.
On AvaHost, Convos uses Plan 1 at €2. The hosted Convos package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. Complete the first account and registration configuration after deployment. IRC networks, NickServ credentials, channel permissions, moderation, network compliance, email delivery, and participant connectivity are not supplied. Review who may register, protect stored logs and uploads, and test remote-network reconnection after planned changes.
F.A.Q
Convos starts at €2 on Plan 1. That plan fits personal use or a small trusted group with moderate IRC activity. Users, networks, joined channels, archived messages, media previews, uploads, video sessions, and simultaneous browsers are the main reasons to review storage and memory as the installation becomes busier.
Convos is a browser client and server-side bouncer; it does not include an IRC network. Add your own supported network details and credentials, then follow that network’s registration, channel, connection, and moderation rules. Availability of a channel, nickname, or historical messages remains controlled by the remote network and what the bouncer received.
A custom domain can point to Convos, with automated HTTPS protecting the web login and browser session. The connection from Convos to each IRC network follows that network configuration separately. After DNS activation, verify account access, network connections, channel logs, uploads, media previews, and reconnection from each browser or device.
AvaHost applies Convos application updates automatically and includes scheduled backups for persistent configuration, logs, and uploads. After a significant release, test account access, registration settings, IRC connections, channels, private messages, search, history, media previews, file access, and mobile layouts. Remote-network changes can still require separate connection or account adjustments.