Most Discord bots converge on the same feature list. The differences that actually change how a server runs are narrower than the marketing suggests, and they are usually about what sits behind a subscription, what you can do from a phone, and whether anyone answers when something breaks. This page is about those, in specifics rather than adjectives.
The AI features run on an API key you supply, from whichever provider you prefer: Google AI Studio, Anthropic, or OpenAI. Google’s free tier in particular is enough for a normal server, so “free AI” here means no subscription to us and no bill from the provider, not a trial that expires.
A server can add several keys. That is not padding: a free tier is rate-limited per key, so a handful of members using an AI command at once is exactly when one key runs out. The bot spreads requests across whatever keys you have added, and if a key fails it moves to the next one rather than failing the command.
The trade is honest. You own the key, so you own the quota and the provider relationship. We supply no AI of our own, which is why there is nothing to charge you for.
Moderation, automod, anti-raid, tickets, suggestions, leveling, economy, role panels and the AI commands are all in the free tier. Premium exists, and it buys cosmetic and convenience extras rather than the ability to run your server.
The reason to state this plainly is that “free” is the most overloaded word in this category. The question worth asking of any bot, including this one, is which specific feature stops working when you do not pay. Here it is the decorative ones.
Bans, kicks, mutes, jails, warnings and purges, with the usual case history, plus automod on keywords and spam, and separate anti-raid and anti-nuke layers for the two situations that actually damage a server: a flood of new accounts, and a compromised staff account deleting channels.
Every prefix command can be renamed from the dashboard, and a renamed command works as a bare phrase with no prefix at all. If your staff would rather typeshut upthan .mute, that is a setting, not a fork. Permission checks are unchanged: renaming a command does not hand it to anyone new.
A full ticket system with panels, categories, transcripts and staff routing, and a suggestions board with voting and staff responses. Both are set up in the dashboard rather than through a sequence of chat commands you have to get right in order.
Embassy relays a channel in your server to a channel in another one over webhooks, so two communities can share a room without either side handing over an invite or an account. Allied servers, sister communities and partner announcements are the obvious uses.
This is the feature most often absent elsewhere, and the one people are most surprised to find without a subscription.
Ask for a summary of recent conversation in a channel and get back what was actually discussed, rather than scrolling a thousand messages. There is a per-user version for moderation: a readable account of what one member has been doing across a channel, which is the difference between a report you can act on and a report you have to research.
Both run on your own AI key, so they cost you nothing beyond the provider quota.
Join a lobby channel and get your own room, which disappears when the last person leaves. The owner controls the limit, the name, who is allowed in and who is kicked out, from the channel itself. The common failure of this feature is a room you cannot rename or lock, which makes it useless for the private call it was created for.
There is a global currency and global XP that follow a member across every server the bot is in, and a completely independent per-server currency and per-server XP that belong to your community alone. They do not share balances and they do not share ranks.
This matters because the single-economy design forces a choice nobody wants to make: either your server’s rewards are diluted by every other server, or a member’s history means nothing when they arrive. Running both avoids the question.
Self-assignable role panels with buttons rather than reaction roles that break when an emoji is deleted. Interactive GIF actions (hug, slap, and the rest) with per-action permissions and channel rules, because the usual complaint about them is not the feature, it is that they cannot be limited to one channel.
Alongside those: starboard, giveaways, counting, confessionals, study rooms, a hall of legends for milestones, and live server-stat channels.
The bot and this dashboard are built in three languages, with Arabic rendered right-to-left properly rather than as left-to-right text that happens to be in Arabic. Generated images (welcome cards, profile cards, leaderboards) reshape and reorder Arabic text correctly, which is where most bots fall back to boxes.
Commands are always typed in English regardless of the server’s language. Only the responses change. That way a server can run in Arabic without its moderators having to relearn the commands.
Discord’s mobile app cannot upload a custom role icon image at all; that is desktop-only in their own client. The dashboard can, which means a server owner with only a phone is not locked out of their own server’s appearance. The same applies to the longer configuration flows, which are genuinely unpleasant to do as chat commands on a phone.
Support is the bot’s author, personally, in the support server. Bug reports tend to be fixed rather than triaged, and feature requests are answered by the person who would implement them.
This is an advantage of being small, and it is worth being clear that it is the same fact as the limitation in the next section.
A comparison page with no downside is an advertisement, so: this is a small project. If you need a formal uptime guarantee, a support contract, or a company that will still be answering tickets on a schedule when the author is asleep, a large commercial bot is the correct answer and no amount of feature list changes that.
If you already run a large, established setup on another bot, migrating levels and economy balances is real work for a benefit you may not need. And if the only thing you want is one narrow feature done extremely well, a dedicated single-purpose bot will usually beat a general one.
What this bot is good at is being the one bot a small or mid-sized community can run everything on, in three languages, without a subscription deciding which half of it works.
Nothing above needs a payment method to test. Add the bot, run the setup, and if it is not better than what you have, remove it.