An open-source alternative to Appeal.gg
Both run Discord ban appeals. One is a hosted appeal portal; the other is a bot you can read, fork and run yourself. Which is better depends on something specific, and this page tries to be straight about what.
Side by side
| Appeal.gg | Appealy | |
|---|---|---|
| Ban appeals | Yes | Yes |
| Mute and warn appeals | Yes | No |
| Shape | Hosted web portal, one link per server | Discord bot plus a dashboard |
| Where appeals are reviewed | In Discord or the web dashboard | The same queue as your staff applications |
| Accepting an appeal | Handled in the portal | Lifts the Discord ban directly |
| Source available | No | Yes — AGPL-3.0 |
| Self-hostable | No | Yes, free |
| Also does | Appeals | Applications, tickets, verification, anti-raid, giveaways, polls, role menus, welcomer |
| Export your data | No export | /export — every form, panel, submission and answer as JSON |
Switching costs you nothing to carry across
There is no import command for Appeal.gg, and there cannot be one: Appeal.gg has no data export. Appealy does not scrape competitors — its Appy importer works only because Appy ships an export command and you hand Appealy the file.
In practice this matters far less than it sounds. Appeal.gg holds appeals, and a decided appeal has almost no forward value — last year's resolved case is not something you consult. That is unlike staff applications, which are history you genuinely want to keep, and which is why the Appy migration has a real importer behind it.
So switching is: invite Appealy, build an appeal form, turn appeals on. Your old appeals stay readable wherever they are for as long as that account exists.
Why you might switch
- One bot instead of two. If you already want applications, tickets or verification, appeals come with them and share one review queue.
- You can leave.
/exportwrites everything as JSON and/import-appealyreads it back. Leaving is a supported operation, not a conversation with support. - You can hold the token. Self-host it and a wrong decision by us cannot take your appeals offline, because there is no us in the path.
Why you might not
- Mutes and warns, as above. This is the big one.
- A portal is a different thing from a bot. Appeal.gg's whole
mechanic — swap
discord.ggforappeal.ggin an invite and a banned user lands on your appeal page — is genuinely good, and it works for someone who cannot see your server at all. - It is built for exactly this. If a standard appeal portal is all you want, a product that does one thing will usually do it better than one feature of a bot that does nine.
Appeal.gg is a separate project by different people and we are not affiliated with it. If it fits you better, use it.
Questions
Can I import my Appeal.gg appeals into Appealy?
No. Appeal.gg has no data export, so there is no file for an importer to read, and Appealy does not scrape other services. In practice it matters little: decided appeals have almost no forward value, unlike staff applications, which is why the Appy migration does have a real importer.
Does Appealy handle mute and warn appeals like Appeal.gg?
No, bans only. Discord has no API for appealing a timeout or a warning, so a product offering it is tracking those punishments in its own database. If much of your appeal volume is not bans, Appealy will not replace what you have.
Is Appealy the same project as Appeal.gg?
No. They are separate projects by different people and are not affiliated. Appeal.gg is a hosted appeal portal covering bans, mutes and warns. Appealy is an open-source Discord bot for staff applications and tickets that also runs ban appeals, and can be self-hosted under the AGPL-3.0.
Can I get my data out of Appealy later?
Yes. The /export command writes every form, panel, submission and answer for your server as one JSON file, and /import-appealy reads it back into another server.
Is Appealy free?
Yes for every feature — paid plans raise throughput caps only. Self-hosting is free under the AGPL-3.0.