Xenon vs RestoreCord: an alternative that asks less

RestoreCord and Xenon are both Discord backup bots, but they work differently. RestoreCord saves more messages per channel and can re-add members after a server is lost. Xenon keeps more restore points, has a template gallery and cross-server sync, and needs nothing from your members or your Discord account.

The short version

	RestoreCord	Xenon
Re-adds members after a server is lost	Yes, if they verified beforehand, capped once Discord limits the owner	No
Restore points, free then paid	1, then 5, 30, 50	15, then 50, 100, 250
Messages saved per channel	50, 200, 500, 2,000	0, 50, 100, 250
Price per month	€0, €5, €10, €20	$0, $5.99, $10.99, $15.99
Asks your members to authorize anything	Yes	No
Discord application registered to you	Yes, on every plan	No
Templates and cross-server sync	No	Yes
IP, VPN, and alt-account filtering	Yes	No

Choose RestoreCord if getting members back after losing a server is the main requirement, and set it up before you need it. Choose Xenon if you want to undo damage to the server itself, such as a raid, a compromised admin, or a bad permission change. The two don’t conflict, and some servers run both.

How member recovery works

RestoreCord can re-add members. Xenon can’t, and no bot can do it through Discord’s bot API, because there’s no endpoint that moves an account from one server to another. If your server is deleted, Xenon rebuilds the channels, roles, permissions, and settings on a new server, and members have to be invited back.

RestoreCord uses guilds.join, a documented OAuth2 scope. When members join your server, a verification page asks them to let an application add them to servers, and RestoreCord stores that permission. If the server is lost, it uses the stored permissions to add those members to a replacement. Discord allows this. The only stated condition is that the bot is already in the server it adds people to.

There are four limits, and they apply to every service built this way:

• It only covers members who verified before the incident. Setting it up after a raid recovers nobody.
• The permission stays with a third party until each member revokes it, which few people do.
• Discord won’t add a user who is banned from the target server, so members a hostile admin banned on the way out don’t come back.
• Since June 2026 there’s a daily cap. RestoreCord’s support staff say that once Discord restricts the account that owns the bot or the server, pulls drop to somewhere between 50 and 500 members a day, and that this affects every bot. Their advice to restricted owners was to create a new Discord account. Discord hasn’t documented the limit, so these numbers come from RestoreCord.

The messages from RestoreCord's support group

On 12 June 2026 a customer asked in RestoreCord’s public Telegram group whether Discord had added a limit, because pulls stopped working after 500 members. Eight days later RestoreCord’s xenos answered:

20 June 2026. Message, archived copy.

On 26 June xenos said what triggers it: “if your discord bot owner or server owner is limited, discord limits the amount of people you can pull”. On 6 July they put the range at 10 to 500. Customers were still reporting it in late July.

Advice for an owner whose account is restricted:

27 June 2026. Message, archived copy.

The cap is most likely to apply when recovery matters most. Discord removing a server is a common way to lose one, and that’s also when the owner’s account is most likely to be restricted. That’s our inference. Neither RestoreCord nor Discord has said it.

The bot is a Discord application you own

Xenon is one Discord application. You add it like any other bot.

On RestoreCord, every plan, including the free one, uses a custom bot: a Discord application you create and register under your own account. That has consequences:

• Discord’s developer terms apply to you, not to RestoreCord.
• If Discord acts against how the bot behaves, it acts on your application.
• If your Discord account is banned, the bot goes with it, and that’s one of the situations a recovery tool is supposed to cover.

RestoreCord’s setup guide also doesn’t mention privileged intents. Without them, backups run and report success but save no message content.

What the setup involves, and why the intents matter

You create an application in Discord’s Developer Portal, add a bot to it, generate a token, copy a client secret, set a redirect URI, and build an invite URL with the right scopes and permissions, all before your first backup.

A bot token and a client secret are the bot itself, not a dashboard login. Whoever holds them can act as it with every permission you granted, and if they leak, rotating them is your job. RestoreCord also holds the stored member permissions, so a single breach exposes both the bot and the list of people it can add to servers.

Reading message content or member data requires privileged intents, which you turn on for your application in the Developer Portal. RestoreCord’s custom-bot guide covers the application, the bot, the token, and the redirect URL. It never mentions them. Nothing warns you if they’re off, because the restriction applies to the REST API a backup reads from and not only to the live gateway. You find out when you restore.

Once a bot can reach 10,000 users, you can no longer turn these intents on yourself. Since June 2026 you have to apply, and Discord can refuse. So the servers big enough to need backups most are the ones whose owners have to get approval for Discord’s two most sensitive permissions. Xenon’s intents were approved once, on our application.

The comparison page covers this with both alternatives side by side.

RestoreCord’s security guide tells you how to avoid detection

RestoreCord’s setup guide warns that if your bot is disabled, all members are lost, and links to a six-point security guide. Two points are basic account hygiene. One forbids selling members and cites Discord’s Terms of Service as the reason, which is to RestoreCord’s credit. Two tell you to use your own domain and a neutral bot name so that, in RestoreCord’s words, it is “harder for Discord to detect that you are using RestoreCord.”

You carry out those steps yourself. You register the application, buy the domain, and pick the name, all on your own account. If Discord treats that as deception, your account is the one at risk.

The guide's wording, and the rule it touches

The setup guide’s opening warning: “It’s strongly advised to familiarize yourself with our bot security guide before taking any further steps. Keep in mind, if your bot gets disabled, all members will be lost!”

The two hygiene points: create the application on an account that isn’t in any servers, so losing your main account doesn’t take the bot with it, and add the bot to a Developer Portal team so you can’t be locked out.

The rule against selling: “Do not sell members on RestoreCord, this is against Discord’s Terms Of Service and will result in your bot getting disabled.”

On custom domains: “Using a custom domain completely hides the RestoreCord brand on Discord’s side. This makes it harder for Discord and your members to detect that you are using RestoreCord.” On naming: “Use a name that is appropriate for your bot. This will make it harder for Discord to detect that you are using RestoreCord.” Their custom-domain page explains why: Discord can link RestoreCord bots together because they all used one redirect domain, and your own domain breaks that link.

Discord’s Developer Policy, in force since July 2024, prohibits impersonating other applications and “deception via your and your Application’s account and identity”. That rule is mainly about posing as someone else, so it’s arguable whether a neutral name breaks it. The guide’s stated goal isn’t in doubt, though. It’s to make the bot harder for Discord to detect.

Is pulling members against Discord’s rules?

No. guilds.join is documented and allowed.

What matters is disclosure. Discord’s Developer Policy says an app that adds someone to a server must clearly tell them and get explicit permission, with an accurate description of what they’re agreeing to. A verification message that says members can be added to a replacement server later meets that. One that only says “click to verify” doesn’t. The server owner writes that message, and RestoreCord’s guide doesn’t ask you to change it. VaultCord’s guide tells you to remove the honest wording.

The Developer Policy text

Rule one: “Do not modify a Discord user’s account without explicit permission from the Discord user. Functionality that intends to make any changes to a Discord account (e.g., adding the account to a server) must clearly and properly inform the Discord account owner of the changes and receive explicit permission to enact the changes.”

Rule two adds that the permission prompt must “contain an accurate description of the purpose or feature being enabled.”

The 2025 breach reports

In February 2025, a file described as a RestoreCord database was posted on a hacker forum. Tom’s Guide and Yahoo Tech reported that it held Discord IDs, usernames, and IP addresses, with estimates between 840,000 and one million records. RestoreCord disputes this. It says the file traces back to a November 2023 incident in which a staff member shared a limited number of IP addresses, that most addresses in the file are randomly generated, and that fewer than 5,000 are real.

We can’t verify either account. The risk exists because member recovery requires a third party to store records about your members, including permissions that can add them to servers. Xenon stores no OAuth permissions and no member list of that kind, so there’s nothing equivalent to leak.

RestoreCord and VaultCord share a founder

The same person built RestoreCord in 2020, sold it in 2022, and then started VaultCord, which is why the two work the same way. RestoreCord is now owned by Axvant UG and publishes its own comparison against VaultCord.

Where that comes from

KeyAuth’s changelog from July 2023 says its founder built RestoreCord in 2020, sold it in 2022, and was starting a new Discord recovery bot. The entry a month later names vaultcord.com. VaultCord’s own documentation says its owner “formerly operated KeyAuth”.

Where Xenon is better

Most server damage is smaller than a deleted server. It’s usually a deleted category, a permission change that locks people out, or a bot that ran the wrong command. Member recovery doesn’t help with any of that. Having several backups to choose from does.

• More restore points. Xenon keeps 15 backups on the free plan and 50, 100, or 250 on paid plans. RestoreCord keeps 1 on its free plan, then 5, 30, or 50. With a single slot, a backup taken after something goes wrong overwrites the last good one.
• Nothing asked of your members. There’s no verification page and no permission for anyone to revoke later.
• No Discord application in your name. There’s no token or client secret to protect and no privileged intents to remember. Discord’s developer terms bind us, not you.
• No stored member permissions. There’s no list of people who can be added to servers, so there’s nothing of that kind to leak.
• Nothing to hide from Discord. The setup doesn’t involve custom domains or names chosen to avoid detection.
• Templates and sync. A template gallery published since 2018, with every submission reviewed, and cross-server sync for messages, bans, and role assignments. RestoreCord has neither.

Where RestoreCord is ahead

• Member recovery, with the limits described above.
• More messages per channel. 50, 200, 500, and 2,000 across its four plans, against Xenon’s 0, 50, 100, and 250.
• Messages on the free plan. RestoreCord’s free plan saves 50 per channel. Xenon’s free plan saves structure, roles, permissions, and settings only.
• Admission control. A firewall with IP, country, ASN, and user-agent rules, VPN and proxy detection, and alt-account signals. Xenon doesn’t do this.

Prices are close at the lower tiers, depending on the exchange rate, and RestoreCord’s top tier costs more. Its tiers also set how many servers you can use, with one on free, five at €5, and 25 at €10. Xenon Premium covers every server you administrate, so compare the tier you’d actually need.

Which to pick

If you need members back after losing a server, RestoreCord is the only one of the two that does it. Set it up early and expect the limits: only members who verified beforehand, no banned members, and possibly a few hundred a day.

For everything else that goes wrong with a server, Xenon gives you more restore points without asking anything of your members or putting a Discord application in your name.

See the full comparison, or add Xenon and take a backup in a few seconds.

Sources

Competitor plans, limits, and prices come from their own pages, read on 29 August 2026. These change, so check the live pages before deciding.

All sources, with the dates we read them

• RestoreCord’s pricing and comparison pages, for its plans, backup counts, and per-channel message limits
• RestoreCord’s public support group on Telegram for the pull limit: the customer report of 12 June, staff messages of 20 June, 26 June, 27 June and 6 July, and a customer report of 25 July, read and archived on 22 October 2026
• Discord’s Developer Policy (effective 8 July 2024), its Community Guidelines and its OAuth2 documentation for the guilds.join scope, read on 11 September 2026
• RestoreCord’s custom bot setup guide, bot security guide and custom redirect guide, read on 11 September 2026. docs.restorecord.com has served a Vercel 404 behind an expired certificate since then, so these link to the documentation’s own origin
• Tom’s Guide’s and Yahoo Tech’s February 2025 reports on the database, and RestoreCord’s response as quoted in them
• The KeyAuth changelog entries of 17 July and 26 August 2023, and VaultCord’s help center, for the founding, the 2022 sale, and the KeyAuth connection
• Xenon’s figures come from our plans page, which shows the live configuration