Discord and Telegram,
on the same wire.
Flake bridges your communities, automates the rest, and respects the time of the operator running them. Built for admins who outgrew the beginner bots but never wanted to run their own.
The whole console,
not the demo.
Six surfaces, one identity model. You configure each thing once and it runs on both platforms. The shape of the product is the shape of the work, not the shape of a feature page.
- 01live
Bridge
Two platforms, one conversation.
Real-time channel sync between Discord and Telegram. Rich media, attachments, reactions, replies. Author identity is preserved on the far side.
- 02live
Captcha
Bots stop at the door.
Cloudflare Turnstile gates every join. Role and permission gates run after verification. Auto-kick on timeout. No friction for humans, none of the slop for spammers.
- 03live
Automations
Event in, action out.
Triggers and actions composed across both platforms. Welcome sequences, scheduled posts, role lifecycles, custom event hooks. The same builder for both surfaces.
triggersmulti-stepcross-platform - 04live
Moderation
Auto-mod that does not embarrass you.
Spam filters, role sync, custom rules, audit logs. Tuned defaults that hold under real community load, not just the demo channel.
auto-modrole syncaudit log - 05live
Announcements
Schedule once, ship to both.
Compose with rich formatting, target channels on either platform, schedule or send. Edits propagate. No more triple-copying the same paragraph.
scheduledrich mediaedit-sync - 06q3 2026
Tickets
Support, off the DMs.
Cross-platform ticket system with priority, assignment, and a single inbox for staff. Currently in private testing with a handful of mid-sized communities.
private beta
Same message, both rooms,
no copy-paste tax.
One operator, two platforms, one source of truth. Point one or more channels from your server at a single destination channel, and the bridge keeps authors, reactions, replies, edits, and deletions in sync across Discord and Telegram. The receiving side never wonders who said what.
- #general
- →
- tg/community
- #announcements
- →
- tg/community
- #raid-night
- →
- tg/community
many channels in, one channel out
not a recording. live demo state, reseeded each visit.
The category settled
for stuck-in-2016.
We did not.
Naming the anti-references is part of the design. If a screen of Flake ever drifts into the lane on the left, treat that as a bug.
the operator clause
flake.team / 2026
We have all sat in front of MEE6 at 2am, trying to figure out which dropdown actually saves the welcome message. We built Flake because that experience is not the price you should pay for running a community. The operator is the customer. The operator is also one of us.
Every screen in Flake is built against a simple test. Could a community manager with three years of Dyno muscle memory land on it, find what they need without reading docs, and leave with the job done? When the answer is no, the screen is wrong, not the manager.
signed, the people who actually ship this