Kengesh Reviews and Details

Questions & Answers

1. What makes Kengesh unique?

   Over 20 games run inside the voice channel itself. You start one while you're already talking — nobody leaves the channel or switches to another app, and the chat keeps running beside it.

   The second one is meetings: guests join by link with no account at all, and the host admits them from a waiting room. Screen sharing is offered rather than imposed — it arrives as an invitation, and each person decides whether to watch instead of having a window appear in front of them.

2. Why should a person choose Kengesh over its competitors?

   It opens in a browser. Nothing to install, nothing to configure before the first conversation, and guests you invite to a meeting don't need an account.

   The free tier is a working product rather than a time-limited trial: voice, video, screen sharing, servers and the full game library are all in it.

   And the games are built in and available to everyone, so playing together never costs you the conversation.

3. How would you describe the primary audience of Kengesh?

   Friend groups and small communities that spend hours in voice together — gaming clans, study and project groups, small teams. Built Turkey-first, with the interface available in Turkish, English, Arabic, German and Russian.

4. What's the story behind Kengesh?

   I built it alone, in Turkey.

   Discord has been blocked here since October 2024, so joining a community suddenly meant setting up a VPN first — and the people who wouldn't bother simply stopped showing up. That loss is invisible: nobody counts the person who never arrived. I wanted somewhere that opens in a browser and just works.

   While building it, a second idea turned out to matter more. If you're already sitting in a voice channel with your friends, the games should be there too, rather than everyone leaving to open something else and the conversation ending.

5. Which are the primary technologies used for building Kengesh?

   Flutter for the client — the Windows app and the web version come from one codebase. Go for the backend. LiveKit as a self-hosted WebRTC SFU for real-time voice, video and screen sharing. PostgreSQL and Redis for data, Caddy in front, everything running in Docker on a single OVH server with Cloudflare at the edge.