Skip to content

Compare

The same recovery. Less handed over.

Every member-recovery bot does the same thing under the hood: a member authorises a bot, and the bot adds them back later. What differs is what members give up to verify, who can read it, and whether they can take it back.

Features

Side by side.

FeatureAnchorRestoreCord
Member pullAdding members who verified back into a new server.Yes, at Discord's paceYesSource: Member recovery, restorecord.com
Works with a protection botA bot that stops raids and nukes while they happen.Yes: the CARTIQO Bot links in one click, and its settings follow the server after a rebuildChecks at verification (captcha, firewall rules, anti-VPN, alt detection); their pages describe no anti-raid or anti-nuke botSource: restorecord.com, Pricing
Structure backupsA copy of the server's roles, channels and permissions to rebuild from.Yes: roles, channels, permissionsYes: roles, channels, permissions and messages (50 to 2,000 messages per backup, by plan)Source: restorecord.com, Pricing
What a verifying member hands overWhat the service keeps about each member who verifies.Username encrypted; no IP stored, only a one-way hash kept 30 daysDiscord ID, OAuth token, account age and device; IP address with ISP, city and VPN status (on by default, the server owner can turn it off); email if the server owner turns it onSource: Privacy Policy, Docs: Security settings
Discord permissions asked of membersWhat Discord asks members to allow when they verify.identify, guilds.joinguilds.join (on by default); email and the server list if the server owner turns them on, on Business and upSource: Docs: Security settings
Members can see and delete their dataWhether members can check and remove their own record.Yes, at anchor.cartiqolabs.com/meYes: a Manage My Data page to view and manage it, and requests by emailSource: Manage My Data, Privacy Policy
Bot modelWhose Discord bot members authorise, and so who can pull them.Your own bot, from day oneYour own custom bot: 1 on Free, 5, 25 or unlimited on the paid plansSource: Pricing, restorecord.com
Run fromWho runs it, and where the data is kept.CARTIQO, Denmark; hosted in Frankfurt (EU)Axvant UG, Germany; database in Germany, application servers also in the USA and SingaporeSource: Privacy Policy

The RestoreCord column says only what their own public pages say, checked on 19 Nov 2026: restorecord.com, Pricing, Privacy Policy, Docs: Security settings, Manage My Data, Member recovery. Features change; check their site for the current details.

Price

A little less than RestoreCord per month at every level, on 8 Nov 2026.

Prices for the closest RestoreCord plan at each level, per month and per year, as their pricing page showed them on 8 Nov 2026. Per year, RestoreCord is cheaper on the first two levels. Compare what each plan includes as well: the price alone is not the whole story.

LevelAnchorPer monthPer yearRestoreCordPer monthPer year
Entry paid planPlus5 servers, 25,000 members€4.99€49.90Premium5 servers, unlimited members€5€30
Mid planPro25 servers, unlimited members€9.99€99.90Business25 servers, unlimited members€10€50
Top planBusiness100 servers, unlimited members€19.99€199.90Enterprise100+ servers, unlimited members€20€200

The lower price in each pair is in bold. Paid yearly, RestoreCord costs less on the first two levels (€30 and €50 a year against Anchor's €49.90 and €99.90), and about the same at the top (€199.90 against €200). Anchor's prices include VAT. What Anchor adds is how it treats members: no IP address stored, every record encrypted and hosted in Frankfurt. Members: Anchor has no limit on Pro and Business, like RestoreCord, and 25,000 on Plus. Servers: the same on every level (5, 25 and 100; RestoreCord says 100+ at the top). Checked on 8 Nov 2026 on RestoreCord's pricing page. Prices and features change; check their site for the current details.

Their Free plan is €0, like Anchor's.

Where RestoreCord is ahead

Message backups. Anchor backs up the structure (roles, channels, permissions) but not messages: that would need a privileged intent and would store real conversations, which Anchor chooses not to keep.

Switching over

A member's permission belongs to the bot they authorised, so a list can't move between services. Set Anchor up beside your current bot and members verify again as they come through; nobody is lost in the meantime.

Set it up before you need it.

Nobody plans for a nuke. The members who verified on a quiet Tuesday are the ones you get back.