Backup bot or anti-nuke bot: which one protects your server?

Owners often ask which to install first. The honest answer is that they guard different moments, and the moments before and after an attack matter most.

Short answer

An anti-nuke bot reacts once an attacker is already inside. A backup bot only helps afterwards, and only with structure unless it also restores members. RestoreCord covers the door and the aftermath: it screens members at verification and rebuilds channels, members and roles.

Every attack has three moments

MomentWhat happensWho handles it
BeforeA raider or alt tries to join and get a roleRestoreCord verification and firewall
DuringMass bans, channel deletions, webhook spamAnti-nuke bots such as Wick or Security Bot
AfterStructure, members and roles must come backRestoreCord snapshots, member pulls, Restore Roles

Anti-nuke tools are good at the middle row: Wick and Security Bot both react to mass bans and deletions as they happen. The catch is that every reaction comes after the attacker is already a member, and neither publishes a way to bring members back once the damage is done.

Before: decide at the door

RestoreCord moves the decision to the verification page. Each newcomer is checked in one pass before any role is granted:

  • Captcha and authentication checks on every plan, Free included
  • Anti-VPN and proxy blocking, alt detection, blacklists and auto blacklist on ban from Premium
  • ASN blocking and rules based on the other servers a member is in, from Business
  • Minimum account age and cellular connection blocking on Enterprise

Combine those with country and IP rules and most raid accounts never reach a channel, which leaves far less for anything inside the server to clean up.

After: rebuild in the right order

When something does get through, order matters more than speed. RestoreCord's recovery guidance follows the same sequence every time:

Incident runbooktext
1. Contain   secure the owner account, revoke unknown roles,
             integrations and webhooks, rotate bot tokens
2. Record    save audit-log entries and UTC timestamps
3. Restore   pick a snapshot from BEFORE the first bad change
4. Pull      bring back members who verified earlier
5. Roles     run Restore Roles (mapping kept for 7 days)
6. Reopen    staff first, then a small group, then everyone
Step 1
Contain

Secure owner, revoke access, rotate tokens

Step 2
Restore structure

Channels, roles, permissions, messages

Step 3
Pull members

Prior-authorized members only

Step 4
Restore roles

Re-assign saved roles to members who returned

Step 5
Reopen

Staff first, then the community

Do not start a restore while a compromised admin, bot token or webhook can still change the server. You would only be rebuilding for the attacker.

So which should you install first?

Small or new servers

Start with RestoreCord. The Free plan gives you verification with a captcha, one snapshot and member restores at no cost, and the restorable member list only grows while verification is running. That list is the one thing you cannot create after an attack.

Large or frequently targeted servers

Add the firewall layers on Premium or Business and schedule backups so a recent restore point always exists. If you also want automated reactions inside the server, an anti-nuke bot can run alongside RestoreCord; they act at different moments and do not overlap.

For the full buyer's view, read the ten questions for any backup bot or how RestoreCord compares with Xenon, and see the best backup bot comparison for plans.

Layered protection checklist

Six things that should be true on any server you care about.

Verification is mandatory

No role is handed out until a member passes the RestoreCord verify page, so every member is screened and restorable.

Firewall rules match your audience

Country, IP and ASN rules plus anti-VPN and alt detection, tuned so real members aren't caught.

Banned means blocked

Auto blacklist on ban stops a removed raider from verifying again on the same account.

A known-good snapshot is pinned

Pinned snapshots survive schedule rotation, so a clean restore point is always there.

Admin access is tight

Owner and admins use MFA, and staff help through sub-users instead of shared logins.

The restore has been rehearsed

You have restored into a spare server once and pulled your own account back in.

Anti-nuke and backup questions

Cover the before and the after

Turn on verification today, take a snapshot, and your server already has two of the three moments handled.