Why Gryt?
The questions people ask before they trust a chat app, with honest answers, including the ones that don’t make us look good.
What is Gryt, and what is it not?
An app for voice, video and text chat, with screen sharing and file sharing. It’s a lot like Discord, except that every community runs on its own server. You can run a server yourself, on your own computer or a machine you rent, or join one somebody else runs. We run one too, if you just want to try it.
Your community’s messages and files live on its server. The code is open, so you can read it, change it, or send a change back.
We aren’t chasing growth. There are no ads, no tracking, and nothing built to keep you scrolling. There’s no sales pitch either, so you’ll mostly hear about Gryt from people who already use it.
Do I need an account?
No. Download Gryt and you can join as a guest. Your device makes its own key and never sends it anywhere. You don’t sign up for anything, and there’s nothing in it we could trace back to you.
Guests get the full app. A guest proves who they are the same way an account does, and can own a server with the same roles. Your app makes a separate key for every server you join, so two servers can’t work out they’re talking to the same person.
An account does get you two things a guest doesn’t. You’re the same person on every Gryt server, so people recognise you somewhere new. And you don’t lose it with your device.
It also makes a ban stick. You can ban a guest, but a guest who wants back in can make a new key in about two seconds. So servers that allow guests control who gets in instead, with invites, approval, or by only letting in people on the same local network. Keep that in mind before you turn guests on. The rest is in the docs.
If you use Gryt in your browser at app.gryt.chat, the Privacy Policy covers what we hold.
What am I actually trusting?
Three things, and they’re not the same.
Whoever runs the server. If you join someone else’s server, they can get at what it stores. Messages, uploads, logs. If you host it yourself, that’s you.
The connection. Audio and video are encrypted on the way (WebRTC does this with DTLS-SRTP). Voice goes through a voice server, called an SFU, so it can reach everyone at once. That puts the SFU on the path too, and the server owner runs that as well.
Us, but only if you sign in. As a guest, you don’t use anything of ours. Your identity is signed by your own key, and no server calls us to check it. Signing in changes that. Login goes through auth.gryt.chat, and a separate service at id.gryt.chat gives you the certificate that servers check. Both are open source, and you can run both yourself.
Where does the server run?
Wherever you put it. The desktop app has a whole server inside it, so you can host one without touching a terminal. The same server runs under Docker Compose or Helm when you want it on a machine that stays on.
If people need to join from outside your own network, you’ll have to open a port, whichever way you run it. A Cloudflare Tunnel can carry the chat side without opening anything. But voice runs over UDP, and a tunnel can’t carry that. So voice needs one port, not a range, and it has to be reachable directly.
Self-hosting has the how, in more detail than this page should get into.
How does it fit together?
The server handles rooms, chat and uploads. The SFU passes voice and video between people. Storage and the database are separate pieces, and you can run all of it on your own machines. A guest never uses the dotted lines.
Voice goes straight from the client to the voice server, over UDP. Nothing in between carries it, and that's the one a tunnel can't do for you.
Can a server admin read my messages?
In a channel, yes. The server stores channel messages as they are, so whoever runs it can read them. The difference is you get to pick who runs it. Or run it yourself.
Direct messages and group chats are encrypted on your device, files included, so the server can’t read them. It can still see who you talk to and when. A message can go out unencrypted if someone hasn’t got a usable key yet, and the app marks it with a red dot. Older messages from before encryption may still be readable too.
Can I run this for a private group?
Yes, and that’s what most people do: one server for a community, a team, or a group of friends. Starting one from the desktop app takes a name and a button. If it needs to stay up when your computer’s off, it’s a single command on Linux. On a shared network, servers show up in the app without anyone typing an address.
The docs go further than this page does, including the full architecture.