Quick Comparison
| Feature | Bot | Gateway |
|---|---|---|
| Use Case | Messaging platforms | Custom applications |
| Platforms | Telegram, Discord, Slack | Any WebSocket client |
| Users | Single-user conversations | Multi-user, multi-agent |
| Protocol | Platform-specific | WebSocket |
| CLI | praisonai bot <platform> | praisonai serve gateway |
When to Use Bot
Team Communication
Deploy to Slack/Discord for team assistants
Customer Support
Telegram bots for customer interactions
Personal Assistant
Single-user conversational AI
Quick Deployment
One command to production
When to Use Gateway
Web Applications
Custom chat interfaces and dashboards
Multi-Agent Systems
Coordinate multiple specialized agents
Real-time Dashboards
Live updates and streaming responses
Custom Protocols
Full control over communication
Architecture Deep Dive
- Bot Architecture
- Gateway Architecture
Key Points:
- Platform handles user authentication
- Bot receives messages via webhook or polling
- Single agent per bot instance
- Platform-specific features (reactions, threads, etc.)
Feature Comparison
Capabilities Support
| Capability | Bot | Gateway |
|---|---|---|
| Memory | ✅ --memory | ✅ Session state |
| Knowledge/RAG | ✅ --knowledge | ✅ Per-agent |
| Tools | ✅ --tools | ✅ Per-agent |
| Web Search | ✅ --web | ✅ Per-agent |
| Browser | ✅ --browser | ✅ Per-agent |
| Thinking Mode | ✅ --thinking | ✅ Per-agent |
| Multi-Agent | ❌ Single agent | ✅ Multiple agents |
| Custom UI | ❌ Platform UI | ✅ Full control |
Deployment
| Aspect | Bot | Gateway |
|---|---|---|
| Setup | Platform token required | No external deps |
| Scaling | One bot per token | Multiple clients per gateway |
| Auth | Platform handles | You implement |
| SSL | Platform handles | You configure |
Code Examples
- Bot (Telegram)
- Gateway (WebSocket)

