No feature bloat. No crazy configs. Just the stuff most people actually need: ✅ send text + media ✅ receive messages via webhooks ✅ multi-session support ✅ QR login with session persistence ✅ web dashboard ✅ fast async runtime with Tokio The goal: cover ~90% of automation use-cases without turning into a monster system. If you’re building WhatsApp automation, bots, or internal tools — would love for you to try it and tear it apart 😄 Feedback, issues, and PRs are more than welcome.
Finally shipping something I’m really excited about 🚀
I just released RustWA — a WhatsApp Web API built in Rust, using headless Chrome to send & receive messages via a clean REST API.
I kept it intentionally simple.
No feature bloat. No crazy configs. Just the stuff most people actually need:
✅ send text + media
✅ receive messages via webhooks
✅ multi-session support
✅ QR login with session persistence
✅ web dashboard
✅ fast async runtime with Tokio
And very intentionally not doing:
❌ complex group management
❌ status/story
❌ contact sync
❌ reactions
The goal: cover ~90% of automation use-cases without turning into a monster system.
If you’re building WhatsApp automation, bots, or internal tools — would love for you to try it and tear it apart 😄
Repo here 👇
https://gitlab.com/buyungb/rustwa
Feedback, issues, and PRs are more than welcome.
#rust #opensource #whatsapp #buildinpublic #devtools #automation
Solid choice with the Rust + Tokio stack! 🦀 Managing headless Chrome instances is usually a memory nightmare, so using Rust here makes perfect sense for efficiency.
Quick question: How does it handle session persistence if the container restarts? Do I need to re-scan the QR code every time, or does it save the session state locally?
Yes — sessions are persistent. The service saves the session state locally and automatically reloads and reconnects when it restarts, so you don’t need to re-scan the QR code each time.
If you want to see it in action, just download the binary that matches your OS and give it a try — would love to hear your feedback after!
Report
Congrats on the launch — clean, focused WhatsApp automation with Rust is super promising 👏
RUSTWA
@buyung_bahari
Solid choice with the Rust + Tokio stack! 🦀 Managing headless Chrome instances is usually a memory nightmare, so using Rust here makes perfect sense for efficiency.
Quick question: How does it handle session persistence if the container restarts? Do I need to re-scan the QR code every time, or does it save the session state locally?
Congrats on the launch!
RUSTWA
@arsene94 Thank you! I really appreciate that 🙌
Yes — sessions are persistent. The service saves the session state locally and automatically reloads and reconnects when it restarts, so you don’t need to re-scan the QR code each time.
If you want to see it in action, just download the binary that matches your OS and give it a try — would love to hear your feedback after!
Congrats on the launch — clean, focused WhatsApp automation with Rust is super promising 👏
RUSTWA
@zeiki_yu Thank you for your support