Wick bot review: what it is good at and where it runs out
We make an AI moderation tool, so treat this as an interested party's assessment. Every claim about Wick below comes from Wick's own documentation, and the rating comes from a public page you can open yourself. Where we could not verify something, we say so instead of guessing.
The first thing to say is that Wick is not really our competitor. It is a security bot, and we are a content moderation bot. Understanding that distinction is most of what this review is for.
What Wick is
Wick protects the structure of a Discord server rather than policing what people say in it. Its documentation names its Anti-Nuke system as "the critical feature that differentiates Wick from all other Discord Bots", and describes it as a monitoring system watching channel and role creation and deletion, bans and kicks, and webhook creation and deletion. Its target is not the ordinary member. It is the rogue admin, the compromised account, and the person who was trusted with permissions.
Around that sit Panic Mode, a Restore System, Quarantine, Verification, Lockdown, Backups, and a moderation command set covering Ban, Kick, Purge, Timeout, Sanitize, Slowmode, Notes, Warn, plus case tracking through Cases, Modcases and Nuke Cases.
What Wick does well
Anti-nuke is a category of protection almost nothing else offers. Most bots moderate members. Wick watches the people who could destroy the server outright. It treats attempts to bypass quarantine, to add dangerous permissions to any role, or to change the vanity URL as quarantine offences in themselves, which closes the obvious escape routes rather than just the front door.
Panic Mode is properly engineered. On detecting a nuke attempt, Wick locks the server down and hands complete authority to the owner and itself. It then deploys a separate "miniWick" to retrieve pre-attack server state, deliberately isolated so that hundreds of simultaneous nukes do not degrade the main bot. That is a thoughtful piece of architecture, not a marketing feature.
The Heat system is a better model than fixed thresholds. Rather than "five messages in five
seconds", every action contributes heat that decays over time, so a burst of enthusiasm cools off
while sustained abuse accumulates. Wick describes it as "an adaptive algorithm that adjusts to the
user's current actions and scales properly with an increase in members and their activity". Heat
comes from message repetition, emojis, characters, new lines, mentions with @everyone weighted
heavily, attachments, inactivity in quiet channels, blacklisted words and links, advertisement,
NSFW websites, and malicious websites including ones carrying IP-grabbers and keyloggers. Auto
Timeouts then escalate, with a multiplier that makes each subsequent punishment harsher so that
raiders cannot simply wait out a fixed cap.
That is a genuinely better answer to spam than a counter, and Wick's claim that it "rarely generates false positives, unlike conventional methods" is at least mechanically plausible, because decay means ordinary chatter never accumulates enough.
The documentation is honest about failure modes. On the Restore System, Wick writes that without Imaging enabled restoration "is a finicky process and lacks a lot of information and the server may not be restored properly". Most products would not tell you that up front.
Where Wick runs out
Not flaws, just the boundary of what a security model covers.
Heat measures behaviour, not meaning. It counts how much, how fast, how repetitive, how many mentions, how many emojis. It does not ask what a message says. A single calmly written, correctly spelled message sent at a normal pace generates almost no heat regardless of its content. That is precisely the shape of a targeted threat, a grooming attempt, or a convincing scam.
The blacklists are lists. Words Blacklist and Links Blacklist catch what you wrote down, spelled the way you wrote it, in the languages you wrote it in. Leetspeak, homoglyphs, spaced-out text and invisible characters all get past.
There are no harm categories. Nothing classifies harassment, hate, threats or self-harm as categories. The advertisement, NSFW and malicious-website factors are about links, not about what one member is saying to another.
Nothing weighs conversation context. Heat accumulates per user, so a message that is only harmful given what preceded it looks identical to any other.
What users say
| Source | Score | Sample | Checked |
|---|---|---|---|
| top.gg | 84 out of 100 | 259 ratings | 29 August 2026 |
Note that top.gg rates on a 0 to 100 scale rather than out of five, so 84 there is not the same as 8.4 or 4.2 elsewhere. We did not find a Trustpilot profile to cross-check against, and we could not systematically sample individual reviews from sources we can cite, so rather than characterise themes we cannot evidence, that aggregate is what we are reporting.
Where Supervisor fills the gaps, and where it does not
Supervisor reads what a message means rather than measuring rate and matching strings:
- No blacklist to spell around, so leetspeak, homoglyphs and invisible characters are read as what they mean.
- 16 labels including harassment, hate, threats, scams, self-harm and illegal activity.
- Conversation context weighed when a message is ambiguous alone.
- Images and video moderated, not just counted as attachments.
- Over 100 languages without a list per language.
Where it does not fill the gap, and this list is long:
- Supervisor has no anti-nuke. No monitoring of role or channel deletion, no rogue admin detection, no vanity URL protection.
- Supervisor has no anti-raid, no panic mode, no lockdown and no verification gate.
- Supervisor cannot back up or restore a server.
- Supervisor has no quarantine, and cannot ban or kick. Its actions are Delete, Timeout and Warn.
- Supervisor has no case tracking, only an alerts channel.
- Supervisor has no maintained malicious-link database. Its link filter covers Discord invites, media, Nitro gifts, and your own domain allow and block lists.
If your problem is structural, Supervisor does not solve it at any price, and Wick does.
There is a full comparison of the two approaches if you want the mechanism side in depth.
Who Wick is right for
Wick is right for you if your risks are structural: raids, nukes, rogue or compromised admins, alt-account floods, or a need to verify people at the door and put the server back together if something goes wrong. If you run a large public server where a single compromised moderator account is a genuine threat, this is the category of tool you need, and Wick is the most focused one in it.
It is not sufficient on its own if your members are legitimate and the problem is what they are posting. Heat will catch the flooder and the advertiser. It will not catch the person quietly making one member's life miserable, because that person is not generating heat.
Running both is the normal answer, and here more than anywhere it is genuinely two halves rather than a compromise.
For developers and platforms
Wick is a Discord security bot, so it has no application outside Discord. Supervisor has a REST API with SDKs for Python, JavaScript, Go, Rust and Java, plus a Platform API. The API reference has the endpoints.
The quickest way to judge the content side is on your own content. Paste a message that gets past a keyword filter into the live demo and see whether it gets caught, or add Supervisor to your server.