---
title: "Essential Moderation Bots"
description: "Comparative overview, permissions, and deployment of primary bots for community security and governance."
---

import { Card, CardGrid } from '@astrojs/starlight/components';

No human moderation team can maintain 24/7 scrutiny over every inbound message. Automated bots serve as decisive force multipliers that empower and protect human staff.

---

## The 4 Pillars of Discord Bot Infrastructure

<CardGrid>
  <Card title="Wick (Anti-Nuke / Anti-Raid)" icon="shield">
    The benchmark in Discord server security. Defends against rogue administrators, bulk channel deletions, privilege escalations, and distributed raid floods.
  </Card>
  <Card title="Carl-bot (Logs & Automation)" icon="document">
    Renowned for its robust audit engine (message edits/deletions, member join/leave tracking, nick changes) and versatile reaction role systems.
  </Card>
  <Card title="Dyno (All-in-One Operations)" icon="setting">
    Reliable for fast command-line enforcement (`/warn`, `/mute`, `/ban`), automated announcements, and granular channel-specific filters.
  </Card>
  <Card title="Modmail (Direct Support Tickets)" icon="email">
    Enables community members to direct message a designated bot to initiate confidential support threads with the staff team.
  </Card>
</CardGrid>

---

## Third-Party Bot Security Best Practices

1. **Verify Official Developer Badges**: Only invite bots verified by Discord possessing the official bot developer checkmark.
2. **Audit Granted Scopes**: Never grant the full *Administrator* permission to bots that only require channel-specific write or message management access.
3. **Isolate Bot Command Panels**: Restrict configuration commands to hidden staff rooms (`#mod-bot-cmd`) to prevent curious users from probing prefixes or internal settings.