HayChat is a self-hosted alternative to Discord: text rooms, direct messages and voice rooms on a server you run yourself, with a lightweight native client for Windows and Linux.
Important
HayChat is in early development and not yet ready for production use. The project is open-source and welcomes contributions from the community.
- Text rooms with persistent, paged history, shared by every account on the server.
- Direct messages between any two accounts on a server, with online presence.
- Voice rooms with Opus audio, voice activity or push-to-talk (also while another window has focus), per-user volume and mute, and automatic re-join after a reconnect.
- Unread counts kept by the server, so they follow you to every device.
- Several servers in one client, each with its own display name and settings.
- Administration from the client: create, edit and delete rooms (text, voice, or both), grant the admin role, rename, kick, ban and unban accounts, and give roles with delegated permissions (room management, invite codes, approving sign-ups) and per-room permissions.
- Open or invite-only sign-up: anyone may join, or only with an invite code (optionally approved by a person), with invite links, codes that give roles or a single room, and accounts restricted to that room.
- Encrypted transport: Ed25519 identities, X25519 key exchange and XChaCha20-Poly1305, with the server's key pinned on first connect. No passwords: your identity key is your account. Direct messages are end-to-end encrypted. (see docs/protocol.md).
- Small footprint: written in Odin, with its own immediate-mode UI on SDL3, a single-process server, and PostgreSQL for storage.
Windows and Linux are supported; macOS is planned.
- Your server, your data: open-source and self-hosted, with no data collection.
- Lightweight: a native client and server instead of a browser engine.
- Open development: extensible, and built in the open with community contributions.
-
Testing HayChat? Read the tester guide: download the client, connect, and report problems.
-
Running a server? Follow deploy/README.md to run the server image with PostgreSQL under podman, then give yourself the admin role.
-
Developing? Install podman and run:
./dev.sh ci # build the toolchain image and run every check ./dev.sh up # start PostgreSQL and a dev server ./dev.sh client alice # open a client window as "alice"
docs/development.md explains the dev environment, and CONTRIBUTING.md how to contribute.
| Document | Contents |
|---|---|
| User guide | Every screen and control of the client |
| Client configuration | config.json location and keys |
| Deployment | Server image, quadlet units, setup, backups, upgrades, releases |
| Server configuration | Environment variables, migrations, status log |
| Rooms and accounts | Server rules for accounts, sign-up, roles, rooms, admins, direct messages, unread counts |
| Development | ./dev.sh, checks, the dev pod, dependencies, CI |
| Protocol | Transport encryption and protocol versions |
The full index, including the testing harness, voice tests, and design plans, is in docs/README.md.
HayChat is licensed under the AGPLv3 License. See the LICENSE file for more information.
If you distribute modified versions of the software, you must also distribute the source code under the same license. Using HayChat in a commercial product requires complying with the AGPLv3, which may require releasing your own source code under the same license. Always make sure you have the right to use and distribute any code you contribute under the AGPLv3.
Modding. If you sell a mod publicly, it must be dynamically linked: your mod can interact with HayChat, but it cannot include the HayChat codebase. It should be a separate module that communicates with HayChat through defined interfaces or APIs, so the core HayChat code remains open while still allowing creative modifications and extensions.
Third-party credits. Release builds contain third-party code, libraries and fonts (the Odin
core library, pg, ENet, SDL3, SDL3_ttf, libopus, Inter and Twemoji).
THIRD_PARTY_NOTICES.md lists what each release artifact contains, with
each licence, copyright line, and required credit; every archive ships it as
THIRD_PARTY_NOTICES.txt beside a licenses/ folder.
Contributions are welcome! Read CONTRIBUTING.md before opening a pull request.