🔐
Kick login
Streamer connects their Kick account and sees their channel dashboard.
Development roadmap
From public website to real multi-channel Kick bot.
EzBot should grow step-by-step so the platform stays clean, stable, and ready to compete.
Build order
Do not jump straight into every feature.
The correct path is to make the SaaS foundation first, then connect modules one by one. That prevents logic mismatch between chat commands, dashboard, and public profile later.
1
Brand website
Landing, features, pricing, docs, dashboard preview, and official social brand.
2
Kick OAuth login
Streamer login, connected channel, user sessions, and secure token storage.
3
Dashboard core
Bot status, module status, command manager, settings, and activity logs.
4
Webhook + bot engine
Chat events, command parsing, response queue, and per-channel module routing.
5
Streamer modules
Giveaway, Slot Calls, GTB, Bonus Hunt, leaderboard, viewer profile, and overlays.
MVP scope
The first real bot release should include this only.
Small enough to build safely, strong enough to prove EzBot as a serious product.
⌘
Commands
Add, edit, enable, disable, and test custom commands from dashboard.
📜
Logs
Show command usage, webhook events, bot warnings, and channel activity.
🎁
Giveaway
Simple admin flow first, then weighted tickets and OBS draw overlay.
🎰
Slot Calls
Use the same logic for chat, website, viewer profile, and history.
🖥️
Overlay URL
Browser-source pages ready for OBS preview and realtime updates.