Telegram runs signal channels, private communities, and operations that don't welcome random bots. Bridging messages between chats — reliably, on your terms — used to mean fragile scripts or impossible trade-offs. Neon Forward exists to make that boring problem feel invisible.
It began as a hackathon challenge: design a forwarding layer that respects how Telegram actually works — not a bot in every group, but your session, your rules, your destinations. Something you could trust for real channels, not a demo.
What started as coursework hardened into a product mindset — ship something production-grade, secure enough to stake your name on, and honest about every byte that crosses the wire.
Our team came together around a university project in Toronto — a city packed with researchers, builders, and relentless pragmatists. That mix shows up in how we ship: rigorous where security matters, fast everywhere else.
We're not a faceless logo. We're engineers who run Neon Forward on our own accounts, sweat outages, and iterate from real feedback — the same grind as the power users we build for.
Core forwarding stays free because we keep infrastructure lean and the community helps through donations when the product earns it.
If Neon Forward replaces a brittle script or saves you hours a week, supporting us funds servers, security hardening, and the features on our roadmap.
We're positioning Neon Forward as a serious platform: tighter reliability, deeper automation, and eventually paid tiers for teams and power users who need SLAs, advanced controls, and priority support.
Revenue later only works if trust comes first — transparent engineering, sensible defaults, and zero dark patterns. We're here to build something people recommend, not something they tolerate.
“Great infrastructure disappears. You only notice that your workflows finally work.”
Connect in under a minute — or dive into the docs if you're the meticulous type.