Chat, peer-to-peer group calls and screen share, built for communities that would rather run the thing themselves. Call media goes straight between participants — there is no server in the middle of it.
Real screens from the desktop build — dense sidebar, glow-lined bubbles, the call docked beside the conversation instead of on top of it.
Call media never touches a server. Sessions can be told to expire and wipe the device. What isn't encrypted yet is written down plainly rather than glossed over — the code is public, so verify it instead of believing us.
Read the privacy notesSix things, done properly.
Reactions, edits, replies, voice notes, GIFs and files in DMs or groups.
Jump into the room in one tap. No lobby, no seat count, no waiting.
Whole-screen sharing for presenting, pairing and playing together.
Windows, macOS, Linux and Android — tray, badges, auto-updates.
One token, plain HTTP, webhooks. Ship a bot this afternoon.
One compose file: app, database, cache. Your box, your rules.
Most messengers give you two of the three: privacy, group calls, or control over the server. Dialog is built to give all three.
| CAPABILITY | DIALOG | MAINSTREAM MESSENGER | COMMUNITY CHAT PLATFORM |
|---|---|---|---|
| Group calls with no server in the middle | Yes | No | No |
| Screen share in a call | Yes | Limited | Yes |
| Sign up without a phone number | Yes | No | Sometimes |
| Run your own server | Yes | No | No |
| Full source published | Yes | Client only | No |
| Bot API without a review queue | Yes | Yes | With approval |
A token and an HTTP call is the whole onboarding.
POST /bot<token>/sendMessage
Content-Type: application/json
{"chat_id":"@grp:12","text":"deploy ok"}
Read the Bot API
App, database and cache in one compose file.
git clone github.com/VanylixCODER/Dialog cp .env.example .env docker compose up -dView the source
Call media is: audio, video and screen share go straight between participants and never reach a server. Messages are not — they travel over TLS and are stored on the instance you or we run. End-to-end encrypted DMs are on the roadmap, and we would rather say so than imply otherwise.
A username, a hashed password, your messages, and the routing metadata needed to deliver them. No phone number, no address book, no analytics. Self-host and that server is yours.
Calls are a peer-to-peer mesh — every participant sends to every other one. Small groups are comfortable; very large rooms are not what it is built for.
Yes, and open source under AGPL. No paid tier gating calls or screen share. If you would rather not use the hosted instance, run your own — same code, same clients.