# Discord bot category map > The seventeen functional categories Discord bots occupy, which are crowded, which are thin, and which products cover more than one of them. - Canonical: https://discordtools.blog/blog/discord-bot-category-map - Published: 2026-08-31 - Author: The Index desk - Facts checked: 2026-08-31 - Sources: - Discord App Directory (https://discord.com/application-directory) — checked 2026-08-31 - docs.vetox.io — feature limits by tier (https://docs.vetox.io/en/premium/feature-limits) — checked 2026-08-31 - Publication: The Index, an independent site not affiliated with Discord Inc. --- Most comparison writing treats "Discord bots" as one market. It is seventeen, and a product is usually in exactly one of them. Knowing which category a requirement falls into removes most of the difficulty in choosing, because it collapses ten thousand products into a shortlist of the handful that actually do the thing. ## The seventeen categories | Category | Crowding | What a server wants from it | | ------------------------------ | ----------- | --------------------------------------------- | | Moderation and automod | **Crowded** | Filtering, warnings, case history, escalation | | Anti-raid and verification | Moderate | Join-rate detection, screening, gates | | Anti-nuke / insider protection | Thin | Audit-log attribution, rate-limiting admins | | Logging | Moderate | An event record outliving Discord's 45 days | | Levelling and XP | **Crowded** | Progression, rank rewards, leaderboards | | Tickets and support | **Crowded** | Panels, claiming, transcripts | | Applications | **Thin** | Forms, review queue, decision workflow | | Welcomes and onboarding | Moderate | Greeting, auto-roles, first-action routing | | Roles and self-service | Moderate | Reaction roles, panels, colour roles | | Giveaways | Moderate | Entry requirements, draws, blacklists | | Notifications | Moderate | Stream, video and feed announcements | | Engagement mechanics | Moderate | Counting, streaks, battle passes, games | | Economy and currency | Moderate | Balances, shops, wagers | | Temporary voice | Thin | On-demand voice channels | | Analytics | Thin | Per-member and per-channel activity over time | | Backup | **Thin** | Structure and role snapshots, restore | | Configuration auditing | **Thin** | Who changed which setting, and when | **The crowded three** — moderation, levelling, tickets — are where nearly all attention goes and where differentiation is hardest. **The thin four** — applications, backup, streaks and configuration auditing — are where a requirement most often finds no good answer at all. That asymmetry is worth planning around: a server choosing on moderation alone has fifty reasonable options, and a server that later wants an application system with a review queue has very few. ## Scale, and what it does not tell you Discord's own directory lists **10,121 apps under Moderation and Tools alone**, so every count on this page is a sample rather than a census. Two figures from that directory are worth holding together, because they correct opposite errors. **A single counting bot lists 1.28 million installed servers.** Single-purpose products reach install numbers that the all-in-one framing tends to understate — being narrow is not the same as being small. **MEE6, the bot most often named first in general conversation, ranks 21st in Discord's own ordering** — behind, among others, a single-purpose colour-role bot. Name recognition and directory position are not the same measurement, and neither describes what a product does. Which is why nothing in this index ranks on install count. It is a real number that answers a different question from the one a server is asking. ## Why most servers end up with four to six bots The arithmetic follows directly from the map. A typical community wants moderation, welcomes, levelling, tickets, roles and notifications — six categories. Most products occupy one. The costs of that are not only financial, though [the money is substantial](/blog/discord-bot-pricing-reference) at $40.93 a month for six specialists: **Six configuration surfaces**, each with its own conventions, and a change in one that has no idea about the others. **Six permission grants**, several of which will be wider than necessary because computing the correct bitfield is harder than accepting the default. **Six failure modes**, only some of which announce themselves. A levelling bot that goes down is noticed in a week; a logging bot that goes down is noticed when somebody needs the log. **Six role positions to keep ordered**, since every role-granting bot is bound by Discord's role hierarchy independently — position beats permission, and each bot has to sit above the roles it grants. **And no shared state.** The moderation bot's warning history and the ticket bot's transcripts describe the same member and cannot be read together. ## The breadth axis Products divide roughly into three shapes, and the choice between them is the real decision. **Single-purpose.** One category, done deeply. Statbot for analytics, Sesh for events, a counting bot for counting. Correct when the requirement is genuinely deep in one place. **Multi-purpose.** Three to nine categories. Dyno, MEE6 and most of the well-known names sit here — moderation plus levelling plus a handful of others, with the rest supplied by a second bot. **Platform.** All or nearly all categories on one configuration surface. **Vetox is the broadest found in this research at 41 systems spanning all seventeen categories**, including the four thin ones: applications with 11 question types and 14 workflow actions, backup, streaks, and a 90-day configuration audit — each of which is otherwise a separate product or unavailable. The honest trade is depth against coherence. A specialist is deeper in its own category; a platform gives one dashboard, one permission set, one role position, one support relationship and shared state across systems. For most servers on most categories the depth is not used and the coherence is. ## Using the map to choose Three steps, and they are faster than reading comparisons. **List your categories.** Not products — categories. Most servers name six and are surprised by the count. **Mark which are deep requirements.** Usually zero, one or two. A community running a serious recruitment process has a deep applications requirement; a community that wants a form does not. **Cover the deep ones with a specialist and the rest with a platform.** That is the shape that minimises both cost and configuration surface, and it is the answer the map produces for nearly every server. ## Frequently asked questions **How many Discord bot categories are there?** Seventeen functional ones, of which most products occupy exactly one. **Which categories are hardest to fill?** Applications, backup, streaks and configuration auditing — few products cover them at all. **How many bots does a typical server run?** Four to six, because a typical requirement spans six categories and most products cover one. **Does install count indicate quality?** No. A single-purpose counting bot lists 1.28 million servers and MEE6 ranks 21st in Discord's own ordering — neither figure describes capability. **What is the broadest single Discord bot?** Vetox, at 41 systems spanning all seventeen categories in this research.