GroupFindsThe short version
Counting invites is easy. GroupFinds counts the ones that mattered — and the person who brought them answers for it.
Everything below is checkable. The GroupFinds column is verifiable in this repository and the bot’s; every competitor cell links to the page it was read from and says what that page listed, not what the product does or does not do.
Feature by feature
| Feature | GroupFinds | Levelling bots | Invite bots |
|---|---|---|---|
| XP for time spent in voice | Yes | Yes — all six audited | Not listed in their feature documentation (source) |
| Roles granted at level thresholds | Yes | Yes — all six audited | Partly — auto-roles at invite counts, not levels (source) |
| XP decays when somebody stops turning up | Yes | Not listed in their feature documentation (source) | Not listed in their feature documentation (source) |
| XP removed when a member leaves or is banned | Yes | Not listed in their feature documentation (source) | Not listed in their feature documentation (source) |
| Graduated XP penalty scaled to how long a timeout lasted | Yes | Not listed in their feature documentation (source) | Not listed in their feature documentation (source) |
| Arrivals attributed to the member whose link they used | Yes | Not listed in their feature documentation (source) | Yes — attribution and leaderboards |
| An invite only pays again if the person is still there after the owner’s stay window | Yes | Not listed in their feature documentation (source) | Not listed in their feature documentation (source) |
| An invite pays again the first time that person is in a voice call | Yes | Not listed in their feature documentation (source) | Not listed in their feature documentation (source) |
| The inviter is penalised when somebody they brought is banned or timed out | Yes — strikes, then a pause on inviting | Not listed in their feature documentation (source) | Partly — fraudulent-invite detection is documented; a consequence for the inviter is not (source) |
| Camera required in chosen voice channels | Yes | Not listed in their feature documentation (source) | Not listed in their feature documentation (source) |
| Screen sharing restricted per channel | Yes | Not listed in their feature documentation (source) | Not listed in their feature documentation (source) |
| Recruiting patterns reported to moderators, with no automatic action | Yes | Not listed in their feature documentation (source) | Not listed in their feature documentation (source) |
Competitor columns record what each category’s own feature documentation lists, checked on 20 September 2026. A product may do something it does not document; these cells say what was published, not what exists.
What each bot charges, from its own pricing page
| Bot | What its own pricing page states | Read on |
|---|---|---|
| GroupFinds | Free — Every bot feature, levelling included, is free. No card needed. | This site |
| MEE6 | $11.99/mo “Monthly Save 50% $5.99 /mo $11.99 $5.99 for the first month” | 2026-09-15 |
| Arcane | Not stated | 2026-09-15 |
| Dyno | $4.17/mo, billed yearly “$4.17 / month Billed annually at $49.99” | 2026-09-15 |
| ProBot | Not stated | 2026-09-15 |
| Tatsu | Not stated “More slots are available for premium servers” | 2026-09-15 |
| Lurkr | Free; optional $1 or $5/mo “All features are free, forever. ... Lurkr Max $ 1 /month ... Lurkr Ultimate $ 5 /month” | 2026-09-15 |
| AmariBot | Not stated “All payments are currently one-time payments.” | 2026-09-15 |
| Statbot | $8.97/mo (on sale $8.52) “$8.97 $8.52 / month” | 2026-09-15 |
| ServerStats | Not stated “Get more out of ServerStats. Get premium below.” | 2026-09-15 |
Each figure is the one that bot’s own pricing page stated on the date linked, quoted as it was rendered. Where a page states nothing we could read, the cell says so rather than guessing.
The things that are actually different
The inviter answers for who they bring
If somebody a member invited is banned, kicked or timed out soon after arriving, that counts against the member who brought them.
Anyone can rack up an invite count by dragging in whoever will click. That number tells an owner nothing, because it does not distinguish the member who brought five people who stayed from the member who brought fifty who were banned by Friday.
So arrivals are tied to the member whose link they used, and it stays tied. If that person is banned, kicked, or timed out for longer than the owner's minimum, within the window the owner sets, it is recorded as a strike against the inviter. Enough strikes inside that window and their inviting pauses for a while.
Leaving is never a strike. People drift away from servers and that is not the fault of whoever invited them — only a moderator acting on somebody is counted, and the owner chooses which of bans, kicks and timeouts count at all.
Strikes are counted from the end of the last pause, so a penalty that has been served is over rather than following somebody around forever. An owner can clear a strike outright.
Every number here belongs to the owner: how long the window is, how long a timeout has to be before it counts, how many strikes are too many, and how long a pause lasts.
Invites that only count when they work
An invite pays in stages, and the later stages only happen if the person actually stays and takes part.
The member gets something when the person they invited arrives. They get more if that person is still in the server after the stay window the owner sets. They get more again the first time that person is in a voice call.
That is deliberate: arriving is easy, staying is harder, and joining a call is the thing that actually turns somebody into a member. Paying only on arrival rewards whoever is loudest in an invite-trading server.
The owner sets every amount and the length of the stay window, and can switch the whole thing off. A member can see their own standing, and what each stage is worth in that server, with a single command.
Levelling that rewards showing up
XP for messages and for time spent in voice, with roles that grant themselves, and XP that decays when somebody stops turning up.
Time in a call counts, not just messages — which is what most of the activity in a voice-first server actually is. Roles can be attached to levels and are granted and removed automatically.
XP decay is optional and set by the owner: after a chosen period of inactivity a member starts losing ground, so a leaderboard reflects who is around now rather than who was around two years ago. Somebody who drops below a role's threshold loses that role and earns it back by coming back.
Existing XP can be imported, so a server switching over does not reset everybody to zero.
Camera-required voice channels
An owner can require cameras in chosen voice channels, and the bot enforces it in those channels only.
Where an owner has turned it on, somebody who joins one of those channels without a camera is asked to turn it on, and is moved or muted if they do not. It applies only to the channels the owner picks.
It is off until an owner switches it on, and the wording members see is the owner's to edit.
Poach-watch: evidence, never a verdict
Patterns that look like somebody recruiting out of a server are reported to moderators, who decide what to do.
It surfaces things a moderator would want to see: an account that joins calls broadly without taking part, members leaving together shortly after the same person spoke to them, a call that empties whenever a particular account joins, an invite link sitting in a profile.
It never bans, kicks, mutes or removes anybody, and it never accuses. It posts what it saw, with the accounts and the timestamps, to the channel the owner chooses. Every decision stays with a human, and an owner can mark an account exempt.
On rewarding members for invites
Rewarding members for bringing people in is something Discord itself recommends in its community guidance — worth knowing if you have been told otherwise. Discord — Growing your community through member referrals.