Is AEGIS for you?
AEGIS is built for servers that need more than “ban the obvious troll.” It’s a good fit if:- You’ve had — or worry about — coordinated raids, mass-ping floods, or invite spam.
- You want protection against a compromised staff account or a webhook being used to nuke channels and roles, not just protection against ordinary members.
- You need moderation actions to leave a real record: who did what, why, and whether it actually applied — even when Discord itself rejected it.
- You want an incident-response process for anything bigger than a single warn or ban.
- Your team is more than one person, and who can approve what actually matters to you.
What it protects against
Raids
Tracks join activity for coordinated bursts and escalates containment in stages instead of
jumping straight to a lockdown.
Anti-nuke
Per-actor action budgets catch mass channel/role destruction, webhook abuse, and unauthorized
permission grants — including from a compromised staff account.
Malicious links & spam
Catches malicious/impersonating links, spam, mention floods, and invite spam with a
progressive response, not an instant ban.
What it gives your team
Case management
Warnings, notes, and every moderation action land in a durable, sequential case record —
even when Discord itself rejects the action.
Incident response
Raids, anti-nuke events, and other security incidents get a timeline, a commander, and
optionally a private incident room.
Dashboard
A web command center for cases, incidents, detection signals, audit search, and
configuration — read access mirrors your AEGIS permissions.
What it deliberately does not do
- No opaque ML risk scores — every score is a visible, deterministic list of factors, shown to moderators alongside the flag.
- No mass bans purely from join velocity — raids need corroborating signals, and lockdown defaults to a human approving it first.
- No identity correlation, doxxing, or tracking beyond what Discord already exposes.
- No claims of perfection: detection is tunable, and new protections start in a log-only or approval-required mode so your team can review before anything enforces.
How it is built
Detection explains itself. Sentinel’s risk scoring is deterministic, not a black-box model. Every contributing factor is a plain-language reason, and the factor list — not just a number — is what moderators see when they investigate a member or review an approval panel. Nothing escalates without permission. Every protection has an enforcement mode, set per guild, and new protections start cautious rather than enforcing immediately. See Configuration for how that works.Start here
Add AEGIS to your server and run the first-time setup.