Features
Everything in the current release, shown on a made-up game studio. Every name in the screenshots is demo data.
Talks
A Talk is a voice room you drop into, like the corner table at a LAN party. Click it and you are in; nobody gets called. After a reload within 30 seconds you are back in the call. To read a Talk's chat without joining, open it as a preview.
- Screen sharing up to 4K at 60 FPS where the hardware can capture it, with hardware encoding when your machine and connection manage it. Each viewer picks a quality or leaves it on Auto, and everyone sees who watches.
- Picture-in-picture, volume per person and per stream, push-to-talk and noise suppression.
- A lobby opens a temporary Talk for the raid that needs its own room, and it disappears when it is empty. In a Stage, such as a dev Q&A, only members with talk power speak; the others raise a hand.
- The server forwards the packets and never re-encodes them.
Chat
- Markdown with highlighted code, threads, replies, reactions, custom emoji, @mentions and link cards.
- Up to 10 files per message; several images show as a gallery.
- Pinned messages, polls, and drafts that survive a reload. An anonymous poll stores only that you voted, not what.
- Messages written offline are sent when you are back.
- A message can delete itself after 60 seconds to 30 days. A channel can delete old messages or files after 1 hour to 365 days; pinned messages and direct messages are exempt.
- Search filters, reminders, scheduled messages and up to 1,000 saved messages.
- Slash commands such as
/polland/thread, and/timeout,/banand/kickfor moderators.
Forums, wiki and events
- Forum channels collect things like bug reports from a mod test, as cards with tags. Posts can be pinned or marked solved.
- The wiki keeps every save as a revision, and an older version comes back in two clicks. Writing needs a permission.
- Events have RSVPs, a reminder 15 minutes before and a comment thread. A weekly raid night can repeat on its own, with places per role and a waitlist.
Direct messages
- Conversations of two to ten members, which moderators cannot browse.
- A blocked member is not told, and their messages fold away for you.
- You decide whether anyone may start a conversation with you.
- A reported message reaches the moderators as a copy with the messages around it. For a direct message, that copy is all they see.
- The Owner and administrators can turn direct messages off.
Roles and moderation
- The Owner can do everything. Roles get permissions, and categories and channels can allow or deny them per role or member; that is how private channels work.
- Timeouts from 5 seconds to 28 days, bans with a reason and a duration, and kicks, all in the audit log.
- Automod is on from the start and catches mention spam, links from accounts younger than 10 minutes, and raids.
- An admin can copy the channels and roles of an existing server from its template link. Messages are not copied.
- New members can be asked to accept rules before they write.
- View community as shows the channel list as a role sees it.
Bots and webhooks
Incoming webhooks use the common execute format, so most existing integrations work. Outgoing webhooks send signed events to your service. Bots get a REST API and a gateway and see only what their roles allow. There are official SDKs for TypeScript and Go. See the bots page.
Privacy and accounts
- Calls are end-to-end encrypted. Text messages and files are not; the server can read them. See the security page.
- Joining needs an invite, which can expire and have a use limit.
- E-mail is optional. Two-factor sign-in, your sessions, and export and deletion of your data are in the settings.
- There is no telemetry.
Apps
The browser app runs in Chrome and Edge 137+, Safari 17+ (also on iOS 17) and Firefox 129+, and installs on a phone with push notifications. Desktop apps for Windows, macOS and Linux are in beta; see Download. The interface is in English and German.
Running a server
Three containers (the app, PostgreSQL and SeaweedFS) with images for amd64 and arm64, a built-in TURN relay, Prometheus metrics, and backup and restore scripts that CI tests. Images are signed with cosign. On a 4-core Intel N100, 1,000 open chat sessions used about 0.7 CPU cores, and one screen share to 99 viewers about 0.6 cores (method). The hosting guide has the rest.