20+ Platforms
5.6. 20+ Platforms — The Full Landscape and How to Pick the Right Channel
The complete list
Besides the 5 platforms covered individually, Hermes also supports: Signal, Matrix, Mattermost, SMS, DingTalk, Feishu/Lark, WeCom (+ WeCom Callback), Weixin, BlueBubbles (iMessage), QQ Bot, Yuanbao (元宝), Home Assistant (covered in 11.5), Microsoft Teams (+ Teams Meetings, Graph Webhook), Google Chat, LINE, ntfy, SimpleX Chat, Buzz (Block’s Nostr-based workspace), Open WebUI, and generic Webhooks — plus the OpenAI-compatible API server (4.6) for any other frontend.
Why this list keeps growing without breaking the architecture
Recent platforms (Yuanbao, Google Chat) all use a shared generic platform-plugin hook that lets new adapters plug in without touching the core — this is why the platform count has grown fast (7 → 20+ in just over a year) without the system becoming complex or unstable.
How to pick the right platform — not “more is better”
| Need | Suitable platform |
|---|---|
| Personal, quick texting from the phone | Telegram, WhatsApp, Signal |
| Team, group conversation with shared context | Slack (thread-based sessions) |
| Community, public server | Discord |
| Enterprise, Microsoft ecosystem integration | Teams, Graph Webhook |
| Chinese market | DingTalk, Feishu, WeCom, Weixin, QQ, Yuanbao |
| Custom internal system integration | Generic Webhooks, API server (4.6) |
Notes
- Do not enable all platforms “just to be safe” — every additional platform enabled adds another surface to manage allowlist/pairing (6.1, 6.2) and another point to watch when an incident happens (even though circuit breakers isolate failures well, monitoring is still needed).
- For integrating a company-internal chat platform that has no ready-made adapter, use generic Webhooks or the OpenAI-compatible API server (4.6) instead of waiting for Nous Research to build a dedicated adapter — this is the always-available “escape hatch” for cases not in the official 20+ list.
- Before adding a new platform, think about what the real need is in the table above — choosing the right platform by its session characteristics (per user or per thread) matters more than choosing by familiarity alone.