Hey Rubyists,

Excited to announce Telegem 3.0 is out of beta and officially launched! 🎉

For the past few months, I’ve been quietly rebuilding this Telegram bot framework from the ground up with one goal: eliminate the thread management headaches and blocking I/O that plague existing solutions.

The Vision: What if building a Telegram bot in Ruby felt as clean and modern as writing a Rails API? What if concurrency was handled for you, deployment was one-click, and multi-step conversations were a first-class feature? That’s Telegem.

What’s Different: While other gems bolt async patterns onto thread-based architectures, Telegem is async-native. It leverages Ruby’s powerful async gem and the excellent httpx HTTP/2 client to provide a truly non-blocking experience. The result is a framework that scales gracefully, uses resources efficiently, and feels idiomatic in a Ruby 3.0+ world.

Beyond the Tech: Telegem ships with something I felt was missing: real, copy-pastable examples. Not just “Hello World,” but a fully-functional pizza ordering bot, a crypto price tracker, and a support ticket system—all showcasing different patterns and ready to run.

A Call for Co-Creators: The core is solid and tested, but the real potential lies in what the community builds on top. I’m looking for developers to try it, break it, and help shape its future. Is there a killer feature missing? A deployment story that’s still rough? Let’s build it together.

Check it out, star it, fork it, or just browse the (quite comprehensive) docs: 👉 GitLab: https://gitlab.com/ruby-telegem/telegem

I’m passionate about improving the Ruby ecosystem’s tooling for modern applications. If you’ve ever built a Telegram bot or are curious about async Ruby patterns, I’d love to hear your thoughts.

Here’s to building better bots! 🤖