Discord Bot + Web Dashboard: Architecture That Actually Works

The biggest mistake in bot + web projects is treating the dashboard as a separate app. It should be a remote control for the same session the bot already has in Discord.

I use a single source of truth in the bot process for playback state. The API reads and writes through the bot's internal queue manager — never duplicate queue logic in the web layer.

Redis handles rate limits and short-lived tokens. PostgreSQL via Prisma stores guild settings, playlists, and analytics. OAuth ties Discord identity to dashboard access per guild.

For clients, I document the env vars, deploy targets, and failure modes up front so nothing breaks silently after launch.