BotMux
Self-hosted Telegram bot management dashboard with real-time message logging to SQLite, inter-bot routing, and bridges to Slack, Discord, and webhooks
Overview
BotMux is an open-source web dashboard for managing and monitoring Telegram bots, purpose-built for operators who need to observe agent-driven conversations they are not directly part of. It connects to bots via the Telegram Bot API and logs every message, channel post, and chat event in real-time to a local SQLite database with WAL mode — no additional code required in your bot. The dashboard shows a live paginated feed with sender, timestamp, and content, plus full-text search across message history. Beyond passive logging, BotMux adds inter-bot message routing (with optional LLM-based smart routing), admin actions (send, pin, delete, ban/unban), and protocol bridges to Slack, Discord, Meshtastic, and HTTP webhooks. Released in 2026 under Apache 2.0 license.
The Verdict
Who Should Use BotMux?
Best For
- Developers running AI agents on Telegram who need passive, real-time message visibility
- Teams monitoring agent communications they're not directly part of
- Operators managing multiple Telegram bots from one dashboard
- Anyone needing a zero-cost, self-hosted alternative to commercial monitoring tools
- Setups bridging Telegram ↔ Slack or Telegram ↔ Discord
Not Ideal For
- WhatsApp monitoring — not supported
- Native Slack or Discord inbox (bridged through Telegram, not standalone)
- Teams needing LLM-layer observability (token usage, prompt traces) — use Langfuse/LangSmith
- Production-critical setups (project is early-stage, v0.2.0 with a small community)
What's Great
- Truly passive monitoring — logs all messages the bot can see with zero bot-side code changes
- SQLite with WAL mode: fast, local, queryable with any SQL tool
- Real-time message feed with full-text search across all history
- LLM-based smart routing between bots (optional)
- Bridges Slack, Discord, Meshtastic, and HTTP webhooks into Telegram-centric storage
- Audit logging for compliance
- Apache 2.0 — fully open-source, no vendor lock-in
Watch Out For
- Early-stage project (v0.2.0, launched March 2026) — expect rough edges
- Very small community — limited ecosystem support and few contributors
- WhatsApp is entirely unsupported
- Slack/Discord support is a bridge routed through Telegram, not a native inbox
- No SaaS option — requires self-hosting infrastructure
Pricing
View all features & details
Message Logging
- Real-time collection of all messages the bot can see
- Stores messages, bots, chats, users, audit logs
- SQLite with WAL mode for fast concurrent reads
- Full-text search across message history
- Paginated message feed (sender, timestamp, content)
- Tags and routing mappings stored alongside messages
Bot Management
- Multi-bot dashboard — manage multiple bots from one UI
- Long polling and webhook support
- Reverse proxy for legacy webhook bots
- Admin actions: send, pin/unpin, delete, ban/unban
- Session-based authentication with role controls
- Analytics and activity tracking
Routing & Bridges
- Inter-bot message routing with rule-based and LLM-based smart routing
- Slack bridge
- Discord bridge
- Meshtastic bridge
- HTTP webhook bridge
Supported Channels
- Telegram (primary, native)
- Slack (via bridge to Telegram)
- Discord (via bridge to Telegram)
- HTTP webhooks
- WhatsApp — not supported
How It Compares
| Feature | BotMux | Chatwoot | ChatBotKit | n8n |
|---|---|---|---|---|
| Telegram | Native (primary) | Native | Native | Via bot trigger |
| Not supported | Via gateway | Native | Via API | |
| Passive monitoring | Built-in | Requires webhook setup | Audit logs only | Custom setup |
| Real-time logging | Yes (SQLite) | Yes (DB) | Yes (platform) | Yes (custom store) |
| Self-hosted | Yes | Yes | No | Yes |
| Open-source | Apache 2.0 | MIT | No | Apache 2.0 |
| Cost | Free | Free tier | Free tier | Free (self-hosted) |
| Maturity | Early (v0.2) | Mature (2019) | Mature | Mature |