Prevention first: a join-gate tuned to your server's normal, anomaly detection on the curve, and a lockdown that triggers without waiting for a human to be awake and available.
3
layers: gate, detect, contain
<5s
to automatic lockdown
0
false bans left standing
A captcha that stops nobody, or a verification flow so annoying that real newcomers give up and leave.
Coverage gaps are predictable — weeknights, holidays, exam season. Attackers pick those on purpose.
Locking the whole server kills the conversation for the 4,000 people who did nothing wrong.
The raid config was set up by a mod who left. Nobody's sure what it does now, and nobody wants to touch it.
There's no dry run for raid defense. Usually you learn your setup is wrong during a raid.
Every legitimate member turned away at the gate is a member your community never gets.
Containment is scoped: new and suspicious accounts get paused, your community keeps talking.
Not a confidence score. A sentence your mod team can read, argue with, and overturn in one tap.
A meme that gets you banned in a corporate Discord is just Tuesday in a gaming one. Wardn learns which one you are — from your team's own calls.
Borderline cases go to your mods with context attached, instead of quietly removing a real member.
Most bots only see the words in a message. The stuff that actually gets past them is in a picture, behind a link, or sitting in someone's display name.
Tone, intent and context — including the sarcasm, the in-jokes and the borderline calls your server actually allows.
Screenshots, memes, QR codes and text baked into pictures. Wardn looks at the image itself, not the filename.
Where a link really goes: look-alike domains, redirect chains, fake giveaway pages and drainer sites.
Usernames, nicknames and display names — offensive handles and names used as free advertising, caught on join.
Anyone who spams for a living knows keyword filters read words. So they post a screenshot, a QR code, or a link that looks fine until you follow it. Wardn opens the picture.
Caught on the picture itself, hidden instantly, and logged so a mod can confirm the call without the whole channel seeing it first.
Twitch, YouTube and "DM me for cheap" ads posted as a screenshot to dodge link filters. Wardn reads the words inside the picture.
The code gets decoded and the destination checked — the same way one of your mods would if they had the time and the patience.
Redirect chains, fake giveaway pages and one-character-off domains, resolved before your members click them.
Right now
Two weeks inEvery horror story about AI moderation starts the same way: someone gave it permissions on day one. We don't. Here's the whole process.
Before anything gets installed, we sit down with the people who actually do the banning. What sets you off, what you let slide, where the line is on this server.
Wardn joins with zero powers and just watches. No deletes, no warns, no timeouts. It's gathering what your server normally sounds like.
Your mods point at what they banned, warned, or ignored — and why. That's the training signal. Not a generic filter list. Your standards.
We replay your real history through the trained system. Every flag, the action it would've taken, the reason, the member, and their prior warnings — all laid out.
You read the whole sandbox before a single permission is granted. Too aggressive on memes? Tune it. Missed the crypto DMs? Teach it. Zero risk, because nothing has happened yet.
Activation is your call, one channel or all of them, with the scope you choose. And every action stays undoable.
You never have to take our word for it.
By the time Wardn can delete a message, you've already read every decision it would have made on your own server.
Moderation you can audit at a glance — plus the same commands right inside Discord, because nobody wants to open a browser mid-raid.
Mod team audit log
Mods are accountable too. Everything is logged, both directions.
In Discord, too
/wardn history @lex_09
/wardn undo last
/wardn lockdown 10m
The old bots match strings. The new ones are aimed at developers and token communities. Neither of them is built for a mod team of six volunteers running a 40,000-member gaming server.
Word lists, regex, thresholds. Great until the spam changes one character — then it's your weekend.
Powerful, configurable, and written for people who enjoy YAML. Your mod team does not enjoy YAML.
Trained per server on your own moderation history, reviewed in a sandbox before it gets a single permission, and explained in plain language.
Every action is reversible in one tap, from the dashboard or a slash command. And the reversal is a training signal — it won't make that call again.
No. You set the scope, you approve every new pattern, and your mods can override anything. Wardn does the volume; you keep the judgment.
Usually a week of watching, then a sandbox review, then activation. Most teams see the difference in the first few nights.
Every server gets its own quote. Message volume, how you want it set up and how deep the integration goes all change the work involved — so there's a one-off setup fee plus an ongoing fee that covers running it. You'll get exact numbers on the first call, before anything is installed.
We onboard in batches of five servers at a time, because each setup is trained and tuned by hand. When a batch is full, the next one waits. Reaching out early is how you get into the current batch.
Wardn isn't a bot you invite and forget. Each server is trained on its own moderation history and tuned by hand with your team, so we take on five at a time and finish them properly before the next batch starts.
When the current batch is full, the next one waits. If your nights are bad now, early is the only way in.
A 4,000-member server with a quiet chat and a 90,000-member server pushing a hundred thousand messages a day are not the same job. Your offer is built for your server.
The setup fee covers the training, tuning and sandbox review for your server. The ongoing fee covers actually running it — the models, the watching, the support. Both are quoted up front, in plain numbers, before you commit to anything.
Tell us about your server and we'll walk through where the gaps are — before anything is installed.
What a moderation bot has to get right in 2026 — and where the classics stop.
The training loop: every override your mods make becomes a rule you never write.
Why wordlists lose to one swapped character, and what reads intent instead.
Unmasking redirect chains, fake giveaways and QR drainers before members click.
Telling the artist sharing work apart from the person farming your members.
NSFW, gore and slurs handled the same way at 3am as at 3pm.