SSENTINELSECURITY PLATFORM
Checking bot
DISCORD SECURITY · INCIDENT RESPONSE · RECOVERY

Your community.
Under watch.

A security command center for Discord communities. Configure layered defenses, track suspicious activity, and keep recovery close when the unexpected happens.

Add Sentinel ↗Open dashboard →
Per-server security policies Owner-only controls API-backed live stats
S
SENTINEL CORESECURITY ENGINE
⌁
Threat monitoringEvent-driven detection
✓
Recovery readyStructural backup support
READY
DEFENSE IN DEPTH 01 — 04
DISCORD SERVERS—Servers where Sentinel is installed
COMMUNITY MEMBERS—Combined cached member counts
PROTECTED SERVERS—Enabled Sentinel configurations
SECURITY EVENTS · 24H—Aggregate events, no server details exposed
BOT UPTIME—Live API statistics
BUILT FOR REAL-WORLD COMMUNITIES

One console.
More control.

Security, visibility, and recovery workflows in one place—with clear controls instead of a maze of commands.

⌁
01 / DETECT

Threat detection

Monitor spam, raid signals, mass mentions, suspicious account patterns, dangerous permission changes, and destructive administrative activity.

SIGNALS → CONTEXT → ACTION
◈
02 / RESPOND

Configurable response

Choose Low, Medium, or High security and tune individual controls. Set the balance between alert-first visibility and automatic containment.

POLICY-BASED CONTROLS
▤
03 / INVESTIGATE

Owner audit trail

Review recorded security events, response outcomes, configuration changes, and backup activity for servers you own.

SEARCHABLE EVENT HISTORY
⟲
04 / RECOVER

Backup & restore

Preserve supported server structure—roles, channels, categories, and permission overwrites—so recovery can be started deliberately.

STRUCTURAL RECOVERY
⌘
05 / CONFIGURE

Per-server command center

Manage each eligible server separately, select a logging channel, tune thresholds, and manage scheduled backup settings.

SERVER-SCOPED SETTINGS
◉
06 / OBSERVE

Operational visibility

See bot availability and public aggregate statistics from the API, with clear status messaging when the service is unavailable.

LIVE API STATUS
CHOOSE YOUR POSTURE

Security that fits
your community.

Start with a baseline. Fine-tune individual defenses around your community’s size, trust model, and tolerance for false positives.

01OBSERVE FIRST

Low

Favor visibility and alerts, with restrained automated response.

  • Baseline monitoring
  • Conservative thresholds
  • Lower risk of false positives
02RECOMMENDED START

Medium

Balance automatic defenses with practical control for active servers.

  • Balanced detection
  • Configured responses
  • Useful for most communities
03AGGRESSIVE MODE

High

Use stronger automatic responses when the community can tolerate stricter enforcement.

  • Tighter thresholds
  • More aggressive containment
  • Test before production use

! No bot can guarantee prevention of every attack. Discord permissions, audit-log delays, API limits, role hierarchy, and outages affect response. High mode can create false positives; test changes in a private server first.

GET STARTED IN MINUTES

From invite to
informed response.

Set up the fundamentals first. Sentinel works best when its permissions and logging are configured intentionally.

01

Invite Sentinel

Add the bot and grant only the permissions needed for the features you enable.

02

Set your baseline

Choose a security profile, configure a log channel, and review thresholds for your community.

03

Verify coverage

Use the security scan and test key detections with a trusted team before enabling aggressive responses.

04

Review & recover

Check logs regularly, verify scheduled backups, and understand the limits of structural restoration.

OWNER-CONTROLLED BY DESIGN

Your server.
Your decisions.

Dashboard access is restricted to verified owners of servers where Sentinel is installed. Public stats are aggregated; server-specific logs and settings stay behind the owner access checks.

Go to the owner dashboard ↗
✓

Server-scoped configurationSettings are isolated by Discord server ID.

✓

Owner authorization checksOnly the actual Discord server owner can manage dashboard settings.

✓

Explicit recovery workflowStructural restoration is a deliberate action, not a silent background change.

✓

Transparent limitationsBackups do not include message history, attachments, or every Discord resource.

GOOD TO KNOW

Clear answers.
No surprises.

Understand what the platform can do—and where Discord’s boundaries still apply.

Can Sentinel stop every raid or nuke?

No. It can detect and respond to supported signals, but no Discord bot can guarantee prevention of every action. Audit-log timing, permissions, rate limits, and the actor’s authority affect outcomes.

Who can see my server’s logs?

The dashboard API checks that the signed-in Discord user is the actual owner of the selected server and that Sentinel is installed there. Keep your Discord account secure and review OAuth access.

What does a backup restore?

Supported structural data such as roles, channels, categories, and permission overwrites. It does not restore message history, attachments, integrations, webhooks, invites, or member role assignments.

Will High security ever flag a legitimate member?

Yes, aggressive thresholds can create false positives. Start with Medium, tune the thresholds, and test High in a private server before using it in a live community.

Why are public statistics sometimes unavailable?

Statistics depend on the bot process, Discord gateway cache, and database. When the API is unavailable, the page should show a temporary unavailable state rather than inventing numbers.

Does installing Sentinel replace Discord permissions?

No. Sentinel can only perform actions allowed by its granted permissions and role position. Configure least-privilege access and keep human administrator accounts protected.

READY TO SECURE YOUR COMMUNITY?

Stay ready.
Stay informed.

Install Sentinel, configure your baseline, and keep recovery in reach.

Add Sentinel ↗Open dashboard →