Our own chat organization
Folders, archived chats, unread markers, and search organize conversations around everyday communication.
telesrv
one program for a complete MTProto service
telesrv is a Go server that brings MTProto edge handling, RPC routing, updates, media paths, language packs, and background dispatch workers into one service process after PostgreSQL and Redis are ready.
We are building our own client: meet telesrv-flutter →
- Single server program startup
- Desktop and Android multi-device sync
- Batched outbox and optimized hot paths
- Maintained across supported client releases
Telesrv is an independent open-source project.
The telesrv server code is open source. For custom IM features, deep product adaptation, or building a new IM system, contact Telegram @telesrv_net.
telesrv-flutter
From our server to our own client
We are reimplementing the client with Flutter. Chat lists, conversations, messages, media, and group information are already part of a running product.
Our own messaging experience
We build the interface and interactions for message bubbles, quoted replies, pinned messages, and media.
Our own desktop workspace
Chats, messages, and group information appear side by side. Layouts, themes, and window interactions can evolve together.
We can build the client and evolve it alongside the server.
Flutter powers the product interface. Our maintained TDLib fork handles protocol and local state, with telesrv providing the server. Together, they let us tailor an IM product to your needs.
Discuss client and IM customization →Desktop and Android, side by side
A short silent demo showing telesrv Desktop and Android connected to the same telesrv server path, including login, chat list, messages, media, and multi-device sync.
What is telesrv?
One program to run
The server starts as one Go program: RSA key preparation, database migrations, language pack seeding, MTProto edge, RPC router, media/files, updates, and outbox workers are wired together.
Multi-device by design
Desktop and Android clients share the same account state. Current session echoes, other online sessions, and offline difference recovery are handled as separate, testable paths.
Optimized hot paths
Batched reliable outbox delivery, warmed PostgreSQL pools, scoped session lookups, bounded RPC inputs, and seek-style pagination reduce repeated work on chat, sync, and media paths.
Maintained and tracked
telesrv is maintained as supported clients evolve. New Desktop and Android version behavior is tracked through real client traces, compatibility notes, and targeted follow-up work.
API and source
The telesrv server is open source and currently focuses on MTProto/TL compatibility research. It is not a hosted Bot API platform. Protocol progress, compatibility status, and module design are maintained in the repository docs.