2026 · ACTIVE · BUILD

TeleFlow

Multi-account community operations that stay inside the rules

FastAPI
Telethon
Next.js 16
TypeScript
PostgreSQL 16
Redis 7
Docker

TeleFlow is a community management and member-onboarding platform for legitimate Telegram community managers, Web3 projects, DAOs and developer groups. It provides a multi-tiered architecture giving operators control over onboarding strategy through configurable risk profiles.

It is built strictly within Telegram's official server-side rules and official Telethon MTProto API capabilities, and documents its compliance and safety model as a first-class part of the system.

Problem

Telegram community operators managing multiple accounts hit two failure modes: brittle scripts that break on any API change, and tooling that quietly does things the platform prohibits, which ends with the accounts gone.

Question

Can multi-account community management and member onboarding be built so that the compliance model is part of the architecture rather than a warning in the README?

Approach

Build strictly within Telegram's official server-side rules and the documented Telethon MTProto capabilities, then make risk an explicit, configurable dimension of the system rather than an emergent property of how hard the operator pushes it.

System

Open any stage to see what it does.

CONTROL SURFACE — Next.js 16 App Router dashboard, deployable to Vercel while the backend stays on a VPS.

FASTAPI — The orchestration layer. Typed, documented, and the only thing that talks to Telegram.

TELETHON / MTPROTO — Official MTProto client. Multi-account session handling within documented API capabilities.

RISK PROFILES — Configurable risk tiers make the compliance posture an explicit setting rather than an accident of pacing.

REDIS — Queueing and rate coordination across accounts, so pacing is enforced centrally.

POSTGRESQL — Durable state for accounts, campaigns and onboarding history, with a documented backup and disaster-recovery runbook.

Demo

A hybrid deployment — frontend on Vercel, backend on a VPS — with CI/CD, a documented production deployment guide, and a backup and recovery runbook.

Result

Built strictly within Telegram's official server-side rules and documented Telethon MTProto capabilities, with the compliance and safety model written into the documentation.
Configurable risk profiles make onboarding pace an explicit operator decision.
Ships CI/CD, a hybrid Vercel + VPS deployment path, and a backup and disaster-recovery runbook.

Lesson

The interesting design work was subtractive. Every feature I did not build because the platform rules did not clearly permit it made the remaining system easier to reason about — and a tool in this category is only useful if it does not get its users banned.

Source

github.com/BakulBd/TeleFlow ↗

Connected

Bazario — Both are WEB and SECURITY and SYSTEMS work, and both are built with Next.js, TypeScript, PostgreSQL.
GUB Portal — Both are WEB and SYSTEMS and CLOUD work, and both are built with Next.js, TypeScript.
hdgame.me — Both are WEB and SYSTEMS and CLOUD work, and both are built with Next.js, TypeScript, Docker.
CausalGuard — Both are SYSTEMS and CLOUD work, and both are built with FastAPI, PostgreSQL, Docker.