PeakBot

Why I Built It

Purpose and Scope

I wanted to give regular community members more control over voice spaces without requiring admin privileges, while also adding engagement mechanics and server management tooling.

Hardest Part

Technical Constraint

Coordinating two independent services (bot and dashboard) against a shared database while keeping reads/writes safe and consistent across concurrent activity.

What I Learned

Post-build Reflection

I improved my understanding of service boundaries, migration planning (SQLite to MariaDB), and multi-process system design for community tooling.

Key Features

Core Capability Set

• Temporary voice channels with automatic cleanup
• member controls for lock/rename/user limit access patterns
• XP and leveling with leaderboard support
• separate web dashboard process for guild configuration and bot invite flow
• shared persistent data across services.