Moderation & Automod
Warn, mute, kick, ban and timeout with full case history. Anti-spam, anti-invite, link filters and raid protection that reacts in milliseconds.
Moderation, ticketing, giveaways, leveling, invite tracking and audit logging β in a single fast bot, running on hardware we own. No shared cloud database, no data resold, no surprises.
Each module is independent β enable what you want, disable the rest from the dashboard.
Warn, mute, kick, ban and timeout with full case history. Anti-spam, anti-invite, link filters and raid protection that reacts in milliseconds.
Button-driven panels, category routing, staff claiming, transcripts on close and an inactivity worker that tidies up abandoned tickets automatically.
Timed drops with role requirements, bonus entries, fair rolling and 24-hour re-rolls. Survives restarts β everything is persisted, not held in memory.
Text and voice XP with per-role multipliers, custom rank cards, level-up rewards and leaderboards that don't hammer your database.
Know exactly who invited whom, with fake/left detection, per-inviter leaderboards and automatic rewards when someone hits a milestone.
Message edits and deletions, role and channel changes, joins, leaves, nickname updates β routed to whichever channels you choose.
Personal and server-wide reminders, recurring announcements and scheduled embeds β all queued persistently so nothing is lost on deploy.
Button, dropdown and reaction role menus with exclusive groups, plus auto-roles on join and rules-screening support.
More Features might be coming soon based on our users feedback.
Every module is battle-tested under load, with caching, connection pooling and graceful restarts.
We control our ping, memory, CPU and guild count in real time. Stream logs, flip maintenance mode, push a broadcast, or disable a misbehaving command without ever SSH-ing in.
[Redis] Connected to cluster state store.
[Database] MongoDB connected (poolSize: 25).
Bot connected as Royal βΏ Bot#9865
[Presence] rotation refreshed β 4 entries
Autocomplete, subcommands, modals, buttons and select menus. No prefix clutter, no permission guesswork.
Every guild gets its own settings document. Change a log channel or an XP rate without touching anyone else's setup.
Deploys drain in-flight interactions, close the gateway, flush Mongo and quit Redis cleanly. Your members see a bot that simply never seems to go down.
Over 140 commands across every module. Here are the ones people reach for daily.
/ban
Ban a member with an optional reason, duration and message purge.
/timeout
Temporarily mute a member; auto-logged as a numbered case.
/warn
Issue a warning that decays automatically after your set period.
/case
Look up, edit or delete any moderation case by its ID.
/purge
Bulk-delete messages with filters for user, bots, links or attachments.
/ticket setup
Build a ticket panel with categories, staff roles and a welcome embed.
/ticket close
Close the current ticket and save a full HTML transcript.
/ticket add
Pull another member or role into an open ticket.
/giveaway start
Launch a giveaway with duration, winner count and role requirements.
/giveaway reroll
Roll a fresh winner within 24 hours of a giveaway ending.
/rank
Show your level card with XP progress, rank and voice time.
/leaderboard
Paginated server leaderboard for text XP, voice XP or invites.
/level-rewards
Map roles to levels and grant them automatically on level-up.
/invites
See who invited a member, plus joins, leaves and fake counts.
/remind
Set a personal or channel reminder in natural language.
/embed
Compose a rich embed through a modal, then post or schedule it.
/serverinfo
Server overview: members, boosts, channels, roles and creation date.
/config
Open the per-guild settings menu for every enabled module.
No commands match that search.
Royal Bot runs on a private, self-managed server. The database is never exposed to the public internet and is never shared with a third-party provider.
MongoDB runs locally on a dedicated machine we control, bound to 127.0.0.1.
There is no publicly routable database port β remote access is impossible without an SSH
session on the host.
Key-only SSH with password login disabled, a default-deny firewall, fail2ban, unattended security updates, and authentication enforced on the database with least-privilege application users.
Snapshots are encrypted before they leave the machine and stored on offline media. Backups are restore-tested and rotated; expired copies are destroyed, not archived indefinitely.
We store IDs and settings, not conversations. Message content is only retained where a feature you enabled requires it β like a ticket transcript or a deletion log β and it expires on a schedule.
Your data is never sold, rented, or handed to advertisers or analytics brokers. There are no third-party trackers embedded in the bot or in this website.
Remove the bot and your guild's data is purged on our retention schedule. Want it gone sooner? Ask in the support server and we'll wipe it, usually within 72 hours.
Read the full details in our Privacy Policy and Terms of Service.
Yes. Every feature listed on this page is free to use. If optional premium perks are ever introduced, existing functionality stays available at no cost.
The invite link requests the permissions needed for every module. You can uncheck anything you don't want during the invite flow, or restrict the bot's role afterwards β features you disable simply won't run.
It processes messages in real time to run automod and logging, but it doesn't store them unless a feature you turned on needs it β for example a ticket transcript or a message-delete log. Nothing is used for training or profiling.
On a private server we administer directly, with the database listening only on the loopback interface. It is not on a shared cloud database service, and no third party has query access.
Kick the bot and the associated guild data is purged on our retention schedule. For an immediate wipe, open a ticket in the support server from an account with Manage Server, or email us.
Check the repository for the current licence and setup notes. If the source isn't public, the support server is the place to ask.
Jobs like giveaways and reminders are persisted in the database, so scheduled work resumes as soon as the process is back. Status updates get posted in the support server.
Set-up takes under a minute. Invite the bot, run /setup, and you're live.