Comparison
Xenon is the best tool for backing up a Discord server and rebuilding it, and we will make that case narrowly rather than claim to be best at everything. The alternatives do more than we do, and they charge your members and your Discord account for it. Here is the whole trade, including where the answer is not us.
Competitor figures checked 29 August 2026.
It is the headline feature of every bot that has one, and it is not a property of the backup. It is a gate you install on your server months in advance.
RestoreCord and VaultCord both describe the same mechanism. Every member passes an OAuth2 screen when they join, granting an application permission to add them to servers. RestoreCord’s documentation describes storing that token for future restoration; VaultCord calls it OAuth2 member verification with authorizations stored.
If the server is lost, the operator replays the stored authorizations and the members are added to a new one. Nothing about this reads a backup. It reads a list of people who authorized an app, possibly a year earlier.
It only covers members who joined after you installed the gate and who completed it. The permission sits with a third party until each member revokes it, and most will never think about it again. Discord also refuses to add a user who is banned in the target server, so it does not recover anyone who was banned.
Xenon is a bot in your server. It reads what an administrator can already see and writes what an administrator could already write, and no member of your server is ever shown a permission screen or asked to authorize anything.
The trade is real and worth being blunt about: Xenon cannot bring your members back. Discord provides no way to move an account between servers, so a tool restricted to bot APIs cannot do it, and any tool that can is holding a permission your members granted it. If member recovery is what you are shopping for, Xenon is not the tool.
Xenon is an app on Discord. You add it and you are done. The alternatives are services that run on an application you create, register, credential and stay responsible for, and that is before you have taken a single backup.
Open Discord’s Developer Portal. Create an application. Add a bot to it. Generate a token. Copy an OAuth2 client secret. Set a redirect URI. Build an invite URL with the right scopes and permissions, then use it. VaultCord’s API documentation confirms where that ends up: the endpoint that creates a custom bot takes a clientSecret and a token. RestoreCord’s custom bots are separate applications on every plan, including Free.
That token is now yours to look after, permanently. It is a credential that grants administrator access to your server, it exists in two places at once, and rotating it if it ever leaks is your job rather than the provider’s.
And there is a step neither of them documents. Reading message content or member data needs Discord’s privileged intents switched on for your application, in the Developer Portal, by you. RestoreCord’s custom-bot guide covers the application, the bot, the token and the redirect URL, and never mentions intents. VaultCord’s lists the redirect URL, the token and two Discord permissions, which are a different system entirely.
Above 10,000 reachable users you cannot switch them on at all. Since June 2026 you apply, and Discord decides. So a community large enough to really need backups is the one whose owner has to make a case to Discord for the platform’s two most sensitive permissions, on an application nobody has verified, and can be told no. We applied for both on ours and were approved, which is the point: that review happened once, here, instead of once per customer.
Miss it and nothing tells you. The bot connects, the backup runs, the dashboard reports success, and the message content comes back empty, because the gate applies to the REST API the backup reads through and not only to the live gateway. You find out when you restore, which is the one moment you cannot afford to find out.
You add Xenon the way you add any bot on Discord: click, pick the server, done. There is no Developer Portal, no application to create, no token to generate, nothing to store and nothing to maintain.
None of this applies to Xenon, which runs on our own application. It applies wherever you created the bot and handed over its token, because that application is registered to your Discord account rather than to the provider’s, and everything below follows from that one fact.
Xenon is a verified Discord application, and its two privileged intents were applied for and approved. Discord has examined what this software does, what it reads and why. An application you spin up for one server never crosses the threshold that requires any of that, so nobody reviews it. The bot holding administrator permission in your community is one no one has vetted.
And this is the half that matters most. The application is registered to your Discord account, which makes you its developer of record: Discord’s developer terms bind you rather than the provider, and since June 2026 an app that can see more than 10,000 users must apply for privileged intents, so on a community that size it is you writing to Discord about what the software does and why it needs the platform’s two most sensitive permissions.
It shares a failure domain with you. If your Discord account is ever suspended or lost, the application registered to it goes with it, so the tool you installed to survive a disaster stops working in exactly the disaster it was bought for. The standard advice to move the bot into a Discord team is the fix for that, and a team exists precisely because applications otherwise die with the account that made them.
Xenon has run as a single Discord application since 2018. Discord knows exactly what it is, what it asks for and who operates it, and there is one party to hold responsible if it ever stops meeting the platform’s rules.
That concentration is the feature. Every risk of running software against Discord’s platform sits with us, which is where a customer should want it, and it is only possible because there is nothing in how Xenon works that needs to be spread thin to survive.
The catastrophe these products are sold against, the server gone and the community scattered, is real and rare. Most losses are smaller and duller than that, and none of them are helped by getting your member list back.
Every one of those is a rebuild, and a rebuild is decided by how many good states you can go back to and how completely each one restores. That is the job Xenon is built for, and it is the claim we will defend.
The narrow claim, made on the things that decide it.
Xenon captures the whole structure, channels, categories, roles, the role order, permission overwrites and server settings, free and with no cap on how much of the server it covers. Messages, threads, forum posts, bans, nicknames and role assignments come with Premium.
Xenon keeps 15 backups on the free plan and up to 250 on Premium. RestoreCord keeps one snapshot on its free plan and up to 50 on its most expensive. The backup you need is rarely the most recent one. It is the one from before a restructure nobody noticed going wrong.
A single stored snapshot means the first capture you take after noticing damage overwrites the last good state you had. Depth inside a backup only matters once you have more than one to choose from, which is why we would rather give you fifteen for free than one deep one.
Competitors publish larger per-channel numbers than ours: RestoreCord runs 50 to 2,000 by plan and saves messages on its free tier where Xenon saves none. Xenon runs 0 to 250. On depth alone they win, and we would rather say so than bury it.
Messages in a backup are context, so a restored channel is not empty. None of these figures is an archive at any provider. If you want one channel kept deeply, a Xenon chatlog holds up to 1,000 messages from a single channel; if you want a real archive, you want an export rather than a backup.
Fifteen backups of the complete structure, every template in the gallery, and no verification gate on your members in exchange. It is the whole rebuild-a-server job, free, rather than a trial of one.
Adding Xenon is one click. Getting a competitor’s custom bot running means creating an application in Discord’s Developer Portal, generating a token and a client secret, setting a redirect URI and building an invite URL, all before your first backup, and yours to maintain afterwards.
Message content and member data need Discord’s privileged intents enabled on your own application. Neither competitor’s setup guide mentions them. Skip it and the backup still reports success, with the message content empty, which you discover on the day you restore. Xenon’s intents are set once, on our application, where a customer cannot get them wrong.
One subscription covers the servers you administrate. RestoreCord sells server capacity by tier, one on Free, five at €5, twenty-five at €10, so running a handful of communities moves you up their ladder and does not move you up ours.
Xenon has published server templates since 2018 and every submission is checked before it appears, which is why the catalog is smaller than galleries that publish whatever is submitted. Neither competitor runs one.
Backups contain your members’ data, which makes us your processor and puts you in scope of the GDPR. Every workspace accepts a Data Processing Addendum before we process anything, and the version accepted is recorded against it.
Three cases where we are honestly not the answer, so you do not have to find out later.
Xenon restores the server, not the people in it. If recovering the member list is the requirement, a tool built on member authorization is the only thing that does it, and you should go in knowing what it asks of them.
Xenon is recovery, not prevention. It has no firewall, no raid detection and no permission watchdog. Those are a different product and several exist.
A chatlog reaches 1,000 messages in a single channel, which is further than a backup goes but is still not an archive. For real retention, ask us about Vault, or chain chatlogs backwards through the channel with before: and keep the set.
The two products people weigh Xenon against most often, each taken on its own terms.
Xenon vs VaultCord
Restores members through stored OAuth2 authorizations, and runs on a Discord application you create and own. What their API asks you to hand over, and what it means that the app is yours.
Xenon vs RestoreCord
A verification gate first and a backup tool second. Why that ordering decides what it can recover, and what a permission screen on every join costs you before anything goes wrong.
Shopping for a server layout rather than a backup bot? Template galleries, template generators and AI server builders are three different products sold under one name, and where to get a server template is its own comparison.
Anything else, our Discord server is the fastest way to get an answer.
Join our DiscordNo. Discord has no mechanism for moving an account between servers, so no bot can. Tools that advertise it are replaying an authorization each member granted when they joined, which is a thing you have to set up long before you need it.
Because messages in a backup exist to give a restored channel context rather than to archive it, and none of the numbers advertised in this category are an archive. A chatlog goes to 1,000 in one channel if you need depth there.
How chatlogs workThe whole structure of your server, channels, roles, permissions and settings, backs up and restores free, and every template in the gallery is free to load. Premium adds messages, member data and sync.
What Premium addsNothing. They are never shown a permission screen and never grant anything. An administrator adds the bot and runs the commands.
Yes. Xenon does not conflict with a verification or anti-raid bot, and running one for prevention and Xenon for recovery is a reasonable setup.
No, and you should not have to. Xenon is an application on Discord and you add it in one click, the way you add any bot. Both alternatives here need you to open Discord’s Developer Portal, register an application, generate a bot token and client secret and hand them over, which makes that application yours to run, credential and maintain for as long as you use the product.
Yes, and its two privileged intents are approved rather than merely switched on. Discord has reviewed what Xenon does, what it reads and why. A bot you create yourself for one server never reaches the threshold that requires any of that, so nothing about it is reviewed by anyone, which is worth knowing about something you are giving administrator permission to.
With Xenon, we are. It is our application, registered to us, and nothing about it is in your name. With a tool that had you create the bot yourself and hand over its token, that application is registered to your own Discord account instead, so Discord’s developer terms bind you, an enforcement action is against your account, and configuring it correctly is yours too. That last part is the one that bites first: neither competitor’s setup guide mentions privileged intents, and an application without them backs up messages that come back empty.
