Xattix vs Wick: anti-impersonation meets anti-nuke.
Wick is the standard for Discord anti-nuke and server lockdown. Xattix is purpose-built for identity protection: copied admins, fake signal callers, stolen profile pictures, and cross-server scammer intelligence. They protect different attack surfaces, and most serious communities run both.
Side-by-side comparison
The fastest way to see which bot owns which risk in your Discord server.
| Capability | Wick | Xattix |
|---|---|---|
| Anti-nuke (mass channel/role abuse) | Yes — primary focus | No |
| Permission escalation lockdown | Yes | No |
| Anti-raid burst protection | Yes | Reduces alt-account staging via Join Portal |
| Name impersonation scoring | No | Jaro-Winkler with Unicode normalisation |
| Profile-picture similarity (pHash) | No | Yes |
| Bio similarity scoring | No | Yes |
| Cross-server scammer blacklist | No | Yes |
| Identity-Bound Join Portal (OAuth + access codes) | No | Yes |
| Roleless cleanup with consent | No | Yes |
| One-click Kick / Whitelist / Dismiss alerts | For permission events | For identity events |
When Wick is enough on its own
Wick remains the right standalone choice in a few clear scenarios.
Small private servers
Friends-only or NDA-only servers where members are vetted out-of-band. Anti-nuke covers the rare insider permission risk; identity attacks have nowhere to land.
Servers without public staff
If you do not have visible signal callers, mods, or support roles that members would trust on sight, identity scoring offers limited extra value.
Servers without member DMs at risk
If your members never DM each other and never act on staff DMs, the impersonation risk profile drops sharply.
When you need Xattix on top of Wick
Three signals that anti-nuke alone is not enough for your community.
Public staff identities
Owners, moderators, signal callers, support, or creators are listed in public channels. Their names, avatars, and bios are easy to copy.
Money or trust at stake
Trading calls, crypto airdrops, paid education, or VIP support — the kinds of conversations where one fake DM can cost a member real money.
Repeat scammer activity
You have already seen lookalike accounts, fake-mod DMs, or cross-server scammers cycling through your community.
How they work together
Run them in parallel. Each has its own alert channel, its own audit log, and its own job.
Wick handles the perimeter
- Mass channel deletion, role wipes, webhook abuse.
- Privilege escalation by compromised mods.
- Bot account intrusion and integration spam.
- Server-wide lockdown when something looks wrong.
Xattix handles the trust layer
- Names, avatars, bios that copy your protected staff.
- Account age and join-pattern scoring on suspicious profiles.
- Cross-server reputation when a scammer enters a new community.
- Identity-Bound Join Portal for high-trust spaces.
Pricing and access at a glance
Two different commercial models for two different risk profiles.
| Item | Wick | Xattix |
|---|---|---|
| Free tier | Yes (limited) | No (paid only) |
| Paid tier | Wick Premium | Xattix Shield — $29/mo or $279/yr |
| Web dashboard | Yes | Yes — alerts, joins, kicks, blacklist, audit log |
| Setup | Command-driven | 7-step interactive wizard, ~60 seconds |
Frequently asked questions
The questions server owners ask before adding Xattix to a Wick-protected server.
Will Xattix conflict with Wick’s anti-nuke?
No. Xattix never modifies channels, roles, or permissions. Its only writes are kicking flagged impersonators (when you allow it) and updating its own alert channel.
Do I need to disable Wick’s verification?
No. If you use Wick’s verification gate, keep it. Add the Identity-Bound Join Portal only if you want OAuth + one-time access codes for high-trust spaces.
Can Xattix kick automatically?
Yes, but only on high-confidence matches you opt into. Most servers start in alert-only mode, then enable auto-kick once moderators trust the signal.
Keep Wick. Add the identity layer.
Xattix takes about a minute to set up alongside an existing Wick deployment. Start with alerts, tune sensitivity, then enable automation when your team is ready.