Open Source Guilded Alternatives

Fluxer is a free and open source instant messaging and VoIP chat app built for friends, groups, and communities. It is a chat app that puts you first, made in Sweden and funded by Plutonium subscribers and donors rather than investors, which is the difference that shows up in what the product asks of you.

The shape is familiar to anyone who has used a community chat platform. Servers hold channels, direct messages and group chats sit beside them, and messages carry full Markdown. Voice and video calls include screen sharing, noise suppression and echo cancellation, running across 16 voice regions on six continents.

Communities get the controls they need to run themselves.

• Role based permissions: granular control over who is allowed to do what.
• Moderation tools: backed by audit logs, so actions stay accountable.
• Webhooks and bots: integrations that post into channels and respond inside them.
• Custom emoji: uploaded and used per community.
• CSS themes: the client's appearance changed by the people using it.
• File sharing: attachments with link previews.

Self-hosting is where it separates from the platform it resembles. You can run the whole Fluxer backend on your own hardware and connect to it with the same apps the project ships, and it is explicit that there is no license key and no cut-down community edition. Clients cover web, desktop and mobile and switch between instances. The code is licensed under AGPLv3.

This repository is the backend of Stoat, the collection of Rust services and libraries that run the service, published as a set of crates rather than one binary. The web client lives in a separate repository, so what you get here is strictly the server side.

The workspace splits along clear lines. A REST API server named delta and a WebSocket events server named bonfire sit in front of core crates covering configuration, database access, API models, permission logic, user presence and error types. Supporting services handle file storage, a link proxy and a Tenor proxy, while two daemons take care of scheduled data cleanup and push notifications.

Standing up the development environment pulls in everything it depends on.

• Data stores: MongoDB for records and Redis for transient state.
• Object storage: MinIO stands in for S3, with encryption logic in a dedicated crate.
• Messaging: RabbitMQ carries events between the services.
• LiveKit: a configuration file is copied from the supplied example before the stack starts.
• Tooling: mise, Docker and Git are required, mold is optional for faster compilation, and a default.nix is provided for Nix users.

Rust 1.86.0 or newer is the minimum supported version, and a few just recipes cut crate and binary releases. Configuration lives in a Revolt.toml file and the crates are still published under Revolt names, a reminder of where the project came from. Services are licensed AGPL-3.0-or-later.

Mezon is a live, work, and play platform for building custom spaces where people talk, play, and hang out. It claims sub-millisecond response times and support for millions of concurrent connections, aiming at the gap between a chat app fast enough for gaming and one an organization can run at scale.

That performance comes from owning the hot path end to end. The Android and iOS clients are native rather than hybrid, the desktop app is Rust and renders directly on the GPU, and the server stack is written in C over a custom WebRTC SFU, a C11 media engine, io_uring, and a binary data plane rather than generic HTTP and WebRTC middleware.

Features cover the communication layer and everything around it.

• Messaging: Markdown rich text with threads, reactions, and file sharing up to 500MB.
• Voice and video: HD calls for up to 1000 users, with screen sharing, recording, and streaming.
• Security: end-to-end encryption on messages, voice and video, a zero-knowledge architecture, and XSS protection.
• AI features: content moderation, real-time translation across 100 languages, and auto-generated meeting summaries.
• Organization: custom roles with granular permissions, notification filtering, and event scheduling with RSVPs.
• Extensibility: REST and WebSocket APIs, a bot framework with SDK support, and more than 100 integrations.

This repository is the web client, an Nx and React monorepo that starts with a yarn install and a dev command on port 4200. The desktop, iOS, Android, SFU, media engine, and protocol layers each live in their own repository, with builds published for every platform.

Valour organizes a community into planets, and a planet is more than a chat log. Each one can hold chat channels, thread feeds, wikis, voice and video calls, roles, an economy and a village where members walk around and meet, which collapses several separate community tools into one application.

It is written in .NET and Blazor. A shared Razor interface is hosted either as a browser WebAssembly client or as a native application, the server handles HTTP APIs and SignalR, Entity Framework owns the database schema, and bots use the same SDK and API contracts as the client. The client supports tabs, splits and several open conversations at once.

Running an instance is a Docker Compose job.

• Bundled services: the Compose file brings Valour, PostgreSQL, Redis, Caddy and filesystem media storage.
• Certificates: Caddy obtains HTTPS certificates and proxies the application once a domain points at the host.
• Configuration: an env file sets the domain, database password and bootstrap administrator, and only mapped values reach the container.
• Federation: a hub owns accounts and the planet registry while community nodes host planets on their own domains.
• Planet moves: an owner transfers a planet by importing a signed grant, verifying the destination and finalizing deletion at the source.

Self-hosted voice needs a LiveKit overlay and open media ports. The name Valour is a trademark, so forks may not reuse it, though bots, plugins and integrations may.