Server Saver detects attacks, locks down your server, and helps you recover when things go wrong.
/restore is ever needed.
Server Saver is built around what actually happens during an attack: stopping it, containing it, and getting your server back afterward.
Detection and gating that keep threats out or catch them the moment they start.
Automatic containment the instant a threat is detected, with staff alerted immediately.
Versioned backups so a wiped server is a restore away, not a rebuild.
Suspicious activity is detected.
The attacker can be quarantined and the server can be locked down.
Staff are informed about what happened.
Use a backup to rebuild your server.
Detection runs on Discord's own audit log, pushed in real time — not on a delayed poll — so the response starts the moment an action happens.
Beyond automatic detection, you can shut a server down manually the moment something looks wrong.
One command denies @everyone the ability to send messages or connect to voice, across every channel, immediately. Lift it just as fast once it's safe.
Triggers automatically when joins spike past your configured threshold, or engage it yourself at any time with a single command.
While active, every new member is kicked on arrival — a full stop on the front door during an active raid.
A single incident can generate hundreds of events in seconds. Server Saver punishes each one immediately but batches the notifications, so your admins get a clear summary instead of a wall of pings.
/safetycheck any time to confirm.
Server Saver saves your server's structure — categories, channels, permission overwrites, roles, server name, icon, banner, and @everyone permissions — so it can be rebuilt if something goes wrong.
Rolling back a whole server is a big action. /restore shows exactly what will change, takes a fresh safety backup automatically before starting, and waits for a button press — never a typed command that could fire by accident.
If part of a restore fails, Server Saver says so — with the exact list of what didn't go through — instead of always reporting success.
Export any backup as a .json file with /exportbackup, keep it externally, and bring it into a different server with /importbackup.
Schedule recurring backups from every 15 minutes to once a day with /backupschedule, or take one manually any time with /backup. Retention is configurable, and /comparebackups shows exactly what changed between any two.
Message history and member-specific permission overwrites don't come back — member IDs and old messages aren't things a bot can reliably recreate.
/backups lists every saved snapshot with its ID and timestamp; /restorehistory shows past restores and their outcomes.
/status gives you the full picture in one command.
/status reflects its own configuration and history.Faster limits the damage from a real attack; slower tolerates routine admin work without tripping. Whichever you pick, put your trusted admins on the whitelist — the server owner is exempt automatically.
Waits for a clear pattern before acting — fewer false positives, slower to react.
A short burst still gets through before it reacts, but the window is tight.
Reacts on the very first unauthorized action — no pattern required.
@everyone gaining a dangerous permission it didn't have, and a mixed attack whose combined severity crosses the threshold even if no single action type does.
Detect suspicious activity and react automatically, without waiting for an admin to notice.
Quarantine attackers and lock down your server when necessary — before more damage is done.
Use saved backups to recover your server's structure, instead of rebuilding it by hand.
Choose how aggressive your protection should be, and who's exempt from it.
A Discord bot that detects destructive activity, contains it automatically, and keeps versioned backups so your server can be rebuilt if something gets through.
Mass channel deletion, role deletion, bans, kicks, permission escalation on any role or @everyone, and malicious bots joining without permission.
The attacker's dangerous roles are stripped and your configured punishment (kick, ban, strip, or quarantine) is applied immediately. The event is logged, and admins are alerted with a summary rather than one message per action.
Categories, channels, permission overwrites, roles, server name, icon, banner, and @everyone permissions.
/restore shows a preview of exactly what will change, takes a fresh safety backup automatically before starting, and asks for confirmation. The result honestly reports what succeeded and what failed.
No. Message history and member-specific permission overwrites aren't restorable — old messages and member IDs aren't things a bot can reliably recreate.
Administrator is recommended, since anti-nuke, restore, and moderation all touch roles, channels, and members across the server. See the Security page for the full breakdown.
Yes — choose lenient, balanced, or strict sensitivity, and pick the punishment applied when a threat is detected.
Whitelisted admins and the server owner are exempt from anti-nuke checks entirely, so routine server management never triggers a false positive.
Join the support server — link below — or open an issue on GitHub.
Every command is a slash command. /help lists all of them in Discord, grouped the same way.
Free to add. Takes about a minute to set up.