A quieter kind of security.
Filter spam, unwanted links, blacklisted terms, and suspicious reward messages. Set the rules that fit your server.
Explore protection → BUILT FOR YOUR COMMUNITYGood conversations.
Good conversations.
Better protection.
Keep the chaos out and the community in. Protection, moderation, and support — all in one Discord bot.
Configure everything right inside Discord.
↯
Spam filteringLess noise. More conversation.
◇
YOUR COMMUNITY. YOUR RULES.Private supportA little space to solve things.
01 Protect your space02 Support your members03 Stay in control
ONE BOT, MANY HELPING HANDSBuilt for the everyday.
See every command ↗Built for the everyday.
Ready for the unexpected.
Clear actions. Clear records.
Warn, timeout, kick, or ban with permission checks and a saved case history your moderators can follow.
Find your commands →A place to get things sorted.
Private tickets for your members. Structure backups for your server. Useful tools for the people behind it.
Get started →Small details.
Stronger communities.
Enable the protections you need. Every setting belongs to your server and is saved across restarts.
Message protection
Anti-spam uses a configurable message threshold and a 60-second timeout. Anti-link filters links and invites. Word, domain, and user blacklists work independently.
Administrators are exempt from message filters. Edited messages are checked too. Domain blocks include subdomains.
Raid response
Rapid joins trigger an @everyone text-channel lockdown. Staff can restore the previous overwrite settings with /lockdown enabled:false.
Explicit role permissions may override the lockdown. It does not stop people joining or restrict voice channels.
Anti-nuke & webhooks
Three audited channel deletions, role deletions, or bans by one actor in 10 seconds trigger removal of editable roles with dangerous permissions.
Webhook protection removes newly created webhooks from untrusted actors. Audit attribution and role order limit what the bot can do; deleted content cannot be prevented or recovered automatically.
Account review
Set a minimum account age to kick new accounts below your threshold. Anti-alt flags young accounts without custom avatars for human review.
Discord does not expose the information needed to prove that two accounts belong to one person.
Moderation & cases
Ban, kick, warn, timeout, untimeout, unban, and purge. Actions check staff permissions and role hierarchy. Warnings are recorded even if a member’s DMs are closed.
Send case notifications to a staff log channel and view the latest cases with /cases.
Private support tickets
Configure a staff role and category, then let members open a private support channel. Staff can claim tickets, close access, and export up to 500 recent messages as a text transcript.
Closed channels remain available to staff until manually deleted. Server administrators retain access.
Structure backups
Save roles, channels, and permission overwrites. Download JSON copies or recreate missing objects with a confirmed restore command.
Messages, member assignments, integrations, files, and webhooks are excluded. Existing objects are retained; review role order after restoring.
Optional AI tools
Rule-based scam filtering works without an API key. An operator-configured OpenAI key and server opt-in unlock additional scam classification and conversation summaries.
AI sends selected message text to OpenAI and can make mistakes. Summaries and checks are rate-limited; API usage may incur charges.
A command for
the moment.
Search the full command list. Use /help in Discord for a friendly, single-page guide.
No matching commands. Try another search.
Make yourself
at home.
Create your Discord application
Open the Discord Developer Portal, create an application, and enable Server Members Intent and Message Content Intent on its Bot page. Keep the bot token private.
Connect the bot
Copy .env.example to .env in the project root. Set DISCORD_BOT_TOKEN and DISCORD_CLIENT_ID. Use Node.js 24, run
npm ci, thennpm run deployto register slash commands andnpm startto launch the bot and site.Invite & arrange permissions
The operator must configure a public application ID before the invite button can connect.
Add to Discord ↗Move the bot role above members it should moderate. Grant only the permissions required by the enabled tools. Anti-nuke requires View Audit Log and Manage Roles; private tickets require Manage Channels.
Give your bot some direction
Run
/config logsand/config tickets. Enable each filter using/protection. Review/protection status. Protections start disabled so staff can choose the server’s rules.Keep your records safe
Use persistent storage for DATA_DIR. Back up the database and download structure snapshots. Run one bot instance per database. The website can also be hosted separately by uploading the website folder to your web host.
All server management happens through Discord slash commands. The public website has no login or dashboard.
A quick
pulse check.
Checking availability…
Checking this website’s connection to the bot.
- Gateway latency
- —
- Bot uptime
- —
- Last checked
- —
This reports the connected bot process, not a history of incidents. A static copy of this site may not have live bot status.
Privacy,
in plain language.
GuardBot Pro stores server configuration, blacklist entries, trusted user IDs, ticket metadata, moderation cases, and server structure backups in the operator’s database. Moderation cases include Discord IDs, actions, reasons, and timestamps.
Messages & AI
Message text is processed to apply enabled filters. The bot does not archive general chat messages in its database. Staff-requested ticket transcripts contain up to 500 recent messages and attachment URLs and are sent privately in Discord. Staff should handle exported transcripts carefully.
Optional AI features send selected message text to OpenAI when both the operator and server staff have enabled them. Summaries include recent text from the channel where requested. Scam classification sends candidate messages. Review OpenAI’s privacy and API data policies before enabling these features.
Access & deletion
Authorized server staff can view configuration, cases, and backups. The server owner can delete stored server data with /config reset after closing tickets and unlocking the server. The bot deletes its stored records when it receives a server removal event. Offline removals, exported files, hosting backups, Discord’s own data, and staff log messages may require separate deletion by the operator or staff.
The website
The application adds no analytics, advertising cookies, or account system. The hosting provider may process request metadata. Discord and GitHub links are governed by those services’ policies.
Contact
Use the operator’s support channel to request access, correction, or deletion. Do not post tokens or private message content in public issues. Operators should provide their own private contact route before a public launch.
Use it
with care.
GuardBot Pro provides automated Discord moderation and community tools. Server staff choose its configuration and remain responsible for reviewing actions, permissions, exports, and member appeals.
Responsible use
Use the bot only in servers you are authorized to manage. Follow Discord’s terms and community guidelines. Do not use the bot to harass people, collect credentials, or bypass another community’s rules.
Automation has limits
Filters and AI can flag legitimate messages or miss harmful activity. Discord permissions, role hierarchy, audit attribution, API limits, and service availability affect protection. Keep human moderators available and maintain independent backups.
Backups & availability
Structure snapshots do not contain messages, members, files, or complete server state. Restores may be partial and require manual review. Availability is not guaranteed. Operators control hosting, support, retention, and any optional AI costs.
Support & changes
Report problems through the support channel. Operators should adapt these terms to their service and announce material changes before relying on them for a public launch.
Let’s get
things sorted.
Start with the setup guide and command reference. If something still needs attention, share the command you used and the error you received.
Keep your bot token, API keys, and private server messages out of public support requests.
The bot doesn’t respond to commands
Run npm run deploy, check the application ID matches your token, and confirm the bot is online. Global commands may take time to appear; a test guild can make registration faster.
A protection isn’t taking action
Check /protection status, the bot’s permissions, and role order. Administrators bypass message filters. Audit-based protections need View Audit Log.
The bot loses settings on redeploy
Point DATA_DIR to a persistent disk. A host’s temporary filesystem will not preserve the database across deployments.