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.
telesrv
one program for a Telegram-like 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.
- Single server program startup
- Desktop and Android multi-device sync
- Batched outbox and optimized hot paths
- Maintained with Telegram version tracking
This is an independent project. It is not affiliated with, endorsed by, or sponsored by Telegram.
For the complete version, contact Telegram @oomsvip.
Desktop and Android, side by side
A short silent demo showing Telegram Desktop and Android connected to the same telesrv server path, including login, chat list, messages, media, and multi-device sync.
What is telesrv?
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 Telegram clients evolve. New Telegram Desktop and Android version behavior is tracked through real client traces, compatibility notes, and targeted follow-up work.
API and source
telesrv 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.