Consistent enforcement with persistent context
Warnings, case history, mod-log flows, and escalation policies are designed so staff can act with traceability instead of improvisation.
About NotNicePool
A Discord operations stack built to reduce bot sprawl and improve control.
NotNicePool combines moderation, leveling, invite tracking, AutoMod, premium workflows, and a browser-based dashboard in one system. The goal is straightforward: give serious communities one place to manage the parts of Discord that usually get split across multiple bots.
60+ commands
Slash-first, prefix fallback
Dashboard-first
Configure from your browser
Free core
12 modules included
Optional premium
From $3/mo, cancel anytime
What the product isA combined moderation, growth, utility, and dashboard platform for Discord communities that want fewer moving parts.
How it is usedSlash commands are the main interface, prefix fallback is supported, and the dashboard handles most configuration work.
What changes as you growStart with the free operational stack, then add premium systems like tickets, analytics, badges, embeds, and scheduled workflows when needed.
60+Commands discovered from the bot modules
12Command categories currently organized in the project
>=20 <23Target Node runtime for deployment compatibility
Slash + PrefixPrimary slash UX with compatibility fallback
What We Built
The product is organized around real server operations
NotNicePool is not positioned as a single gimmick feature. It is structured around the day-to-day work of running a Discord community well.
Retention tools that feel visible to members
Leveling, rank cards, invite tracking, leaderboards, role rewards, achievements, and profile-related features help make progress visible.
Configuration belongs in the browser, not in memory
Server owners and admins can manage channels, toggles, policies, rewards, and premium modules without depending on command memorization.
Why It Feels Credible
The offer is grounded in real scope, not inflated claims
The strongest reason to trust a tool like this is when the product promise matches the actual implementation and upgrade model.
Core functionality stays in the free tier
Moderation, leveling, invite tracking, AutoMod, utility commands, and dashboard configuration are part of the main product, not a teaser hidden behind premium.
Premium expands workflows instead of blocking essentials
Tickets, starboard, reaction roles, scheduled messages, giveaways, custom embeds, message analytics, custom badges, and extended achievements are positioned as add-ons for teams that need more depth.
The command surface is broad and documented
The site pulls from the real command modules and exposes a searchable reference so admins can verify scope instead of trusting vague summaries.
The workflow is built for operators, not just demos
Slash-first usage, prefix fallback, dashboard configuration, and per-server control are all signs that the product is meant to be administered repeatedly over time.
Operational Principles
How the product is intended to be run
Everything on the public pages points to the same operating model: stable moderation, visible engagement, browser-based configuration, and an upgrade path that stays easy to understand.
One system, fewer overlaps
The product is designed to reduce the need for stacking multiple bots just to cover moderation, growth, and utility basics.
Admin clarity over feature clutter
Features are grouped by practical use: moderation, channels, levels, invites, setup, utility, giveaways, and premium workflows.
Configuration should be recoverable
The dashboard-first approach matters because staff turnover and server growth make memory-based setup impossible to maintain well.
What You Can Verify Today
The public site already exposes the core evidence
Read the product, verify the scope, then decide.
Start with the free stack, inspect the docs and features, and upgrade only when your server actually needs the premium workflows.