Every bot below is good at what it was built for. The difference is where the ceiling is — with a settings page, it is whatever that page happens to expose.
Why us · Discord bot comparison · 11 capabilities, 6 bots
01The evidence
| Capability | Custom Commands | MEE6 | Dyno | Carl-bot | ProBot | YAGPDB |
|---|---|---|---|---|---|---|
| 01Write your own command logic | Go templates | |||||
| 02Per-server custom database | key–value | |||||
| 03Image template editor with variable slots | rank cards | welcome only | ||||
| 04Buttons, menus and modals handled in your code | role buttons | menus only | ||||
| 05Scheduled jobs that run your own code | scheduled CC | |||||
| 06Upload and serve your own files | ||||||
| And the features everyone has | ||||||
| 07Welcome DM with its own embed and buttons | basic | basic | basic | images | basic | |
| 08Restore a returning member's old roles | ||||||
| 09One reaction that adds and removes roles | add only | add only | add only | add only | ||
| 10Reusable embed library, used by id anywhere | per message | per message | per message | per message | per message | |
| 11Scheduled post that decides its own content | timed | timed | timed | timed | scripted | |
A dash means the feature is not offered as described, not that the bot is weak. Rows are scoped narrowly on purpose and reflect each product's own public documentation as of September 2026 — competitors ship changes, so verify before relying on any row. If something here is out of date, tell us and it gets corrected.
02Bot by bot
The levelling bot: rank cards, XP roles, a polished dashboard.
You can set how much XP a message is worth, but not how levelling works. XP for voice minutes weighted by channel, or a rank card showing a member's most-used commands, has nowhere to live.
Levelling lives in your own database and the rank card is a template you design — XP per voice minute, weighted by channel, is a few lines of code instead of a feature request.
The moderation bot: automod, mod log, mutes, a long-standing free tier.
Its custom commands are text responders — a trigger and a canned reply with variables. The gap shows the moment a command has to decide something.
A command can branch, read and write your database, open a modal and post a button that runs more code — because it is code, not a canned reply.
The reaction-role and logging bot, and the best of them at both. Its tags system is the closest thing here to programmable behaviour.
Tags are string substitution, not a runtime: no data structures, no persistent per-server database, no async calls. And its buttons hand out roles — you cannot build an arbitrary button, menu or modal and run your own code on the click.
Reactions add and remove roles, hand the role back on unreact, and preview the real message before you save. Any button, menu or modal you build runs your own code on the click.
Presentation: welcome images, embeds, strong multi-language support.
Its welcome images are one layout with your text and background dropped in, and they are welcome images only — nothing renders a shop receipt or a tournament bracket.
The image editor is not welcome-only. The same canvas renders shop receipts, tournament brackets, profile cards and certificates, from any command, with your data in the slots.
The honest hard case. Genuinely scriptable commands, a database, scheduled execution and deep control.
Go templates instead of Python, a key–value store instead of a real SQL database, and control-panel forms instead of a visual editor with live preview.
Python instead of Go templates, a real database instead of key–value, and a visual editor with live preview instead of a panel full of raw template text.
03Everything you get
Everything that produces something a member can see or run.
08 featuresState that outlives a single command run.
04 featuresRunning it day to day, and finding out what happened.
04 featuresThe safety net under all of it.
04 features04What it costs
No card, no clock. Paid tiers raise the caps, unlock scripts and databases at scale, and take the daily run limit off entirely.
See the paid tiers05Questions
For commands, custom logic, your own data and generated images, yes — those are the things MEE6 has no place to put. For levelling you never want to configure, MEE6 is still the simpler pick.
Python instead of Go templates, a real per-server database instead of a key–value store, and a visual editor with live preview for images, components and messages. YAGPDB is open-source and self-hostable, which Custom Commands is not.
For commands and automation, yes. For a mature moderation stack, run one alongside — Discord bots do not conflict, and most servers migrate one feature at a time.
Yes, free forever with no card required: 5 slash commands, 2 events, 10 embeds, 5 image templates and 200 command runs a day.
No. Welcome messages, reaction roles, embeds, image templates and components are all built visually, and an AI helper writes the code with you when a command needs logic.
Free forever, no card, live in about a minute. Discord bots do not conflict — you can migrate one feature at a time.
