Social Posting — Telegram Stories Scheduler
Role
Technical Project Manager: specs, prototypes, project plan, development coordination.
Tech
| Layer | Stack |
|---|---|
| Backend | FastAPI, PostgreSQL 16, Redis 7, Celery (4 queues), SQLAlchemy 2.0, MinIO |
| Frontend | React 19, Vite 6, Tailwind CSS v4, shadcn/ui, Zustand, React Query |
| Telegram | TDLib (MTProto) + Bot API — separate microservice, persistent sessions |
| Infrastructure | Docker Compose (10 services), Nginx + SSL, isolated networks, zero-downtime deploy |
80+ REST endpoints with OpenAPI documentation. 20+ PostgreSQL tables. Production-ready.
Key features
- 01Secure account connection. The owner scans a QR code or connects a Business Bot. The password never leaves their phone — ever.
- 02One-click publishing. Photo or video, caption, clickable link with visual tap zone editor. Media is automatically adapted to 9:16 (resize, blurred background, H.265).
- 03Scheduling. Weekly/monthly calendar — pick a time and the system publishes automatically. A reconciler catches any stuck tasks.
- 04Team collaboration. Workspaces, three roles (owner / manager / observer), granular access per account. Full audit trail: who, when, what.
- 05Billing and referral program built in. Subscription plans with limits, referral program with tiers and automatic commission payouts.
Problem
Telegram Stories is one of the highest-converting formats. But businesses have no proper way to delegate publishing. A manager or agency has to hand over account credentials — a security hole that doesn't scale and can't be controlled.
The alternative is manual: one by one, no schedule, no history, no visibility into who published what. Manageable with 5 accounts. Chaos with 20.
Audience
| Who | Why |
|---|---|
| SMM agency | Manages 10–100 client accounts from one interface. The client doesn't hand over a password — they connect via QR and see what's happening. |
| Business owner | Delegates publishing while keeping control: audit, roles, access. Can disconnect an account at any time. |
| In-house marketer | Plans a weekly content calendar, uploads creatives, and forgets — everything goes out on schedule. |
| Corporate team | Department isolation, role separation, action log for compliance. |
What's different
vs. manual approach: No manual media resizing. No switching between accounts. No Excel scheduling spreadsheets. One interface — all accounts, all statuses, all publications.
vs. existing tools: Most auto-posting services work with channels and groups via Bot API. Stories is a separate format requiring MTProto (TDLib). Social Posting implements both protocols and does it securely: sessions are persistent, encrypted, and isolated in a dedicated microservice.
By architecture: This is not a script or an MVP. A multitenant B2B SaaS with RBAC, distributed locks, retry with jitter, a reconciler for stuck tasks, and healthchecks on each of 10 containers.
Screenshots
Customization
- 01Plans — account, member, and publication/day limits. Individual overrides for enterprise clients.
- 02Referral program — tier thresholds, commission percentages, custom terms.
- 03Access — ACL at the level of individual Telegram accounts within a team.
- 04Admin panel — three roles (superadmin, billing, support), 2FA, full platform management.
- 05Payments — architecture ready for Stripe or any other provider.
- 06Deploy — your own installation on your domain, `git push` → auto-deploy.
Other projects
Need something like this?
Tell me about the task — I'll suggest an approach, pick a stack and scope it out.