Skip to content

How it works

From a quiet Tuesday to your worst night.

Anchor is three things done in order: your own bot, members verifying with it, and a pull when you need them back. Backups and alerts sit around them.

Step 1

Once, while it's calm

Connect your own bot.

Create an application in Discord's Developer Portal and paste its Client ID, secret and bot token. Anchor checks each with Discord before storing anything, and says exactly which setting is missing.

Setup checklistExample
  1. Bot token works: Done

    Signed in as Pixelhaven Guard.

  2. Client secret is correct: Done

    Discord accepted the Client ID and secret together.

  3. Verify redirect is added: Done

    Members can come back from Discord to the verify page.

  4. Interactions endpoint is set: Needs fixing

    Paste the URL Anchor shows under General Information. Discord tests it as you save.

  5. Public Bot is off: Recommended

    Anyone with the invite link can add your bot. Turn off Public Bot.

  • Discord only lets a bot add members who authorised that bot's application, so the bot has to be yours.
  • One bot per owner, serving all your servers. A ban on someone else's bot never touches it.
  • The invite link asks for six permissions and never Administrator.
  • Token and secret are encrypted under a key that never sits in the database, and never shown again, you included.
  • Revoke the token any time: Developer Portal → your application → Bot → Reset Token, then paste the new one in Anchor.
  • Disconnect the bot and its token is deleted at once. Delete your account and the token, servers, members and backups go 7 days later.
The bot setup guide

Step 2

Every new member

Members verify once.

/setup posts a Verify button in your server. It opens your branded page, which says what is kept and why before the Discord button, not behind a link.

Checks before the verified roleYou choose
Account age
Accounts younger than your minimum are turned away.
Captcha
A Cloudflare Turnstile check, no puzzles for most people.
Blacklist
By user ID, or by IP through its keyed hash.
VPN and hosting networks
Looked up locally, so the IP never goes to a third party.
Alt flag
The same device or IP as a member already in, or one you banned.
  • Members are asked for identify and guilds.join. Never email.
  • Passing every check gives the verified role; failing one tells you through a webhook.
  • The IP address is never stored: only a one-way hash for catching alts, deleted after 30 days. Country and network type stay for your charts.
  • Each member can see and delete their record at /me.
See the verify page

Step 3

The night it happens

Pull them back.

Make a new server, add your bot, press Pull. Anchor checks the bot can do it first, then adds everyone it can at the pace Discord allows. Members it can't add are listed in the report, with the reason.

An example member pull: 3,412 of 4,120 members added to a new server so far.

Member pull

Running

From list

Pixelhaven

Into server

Pixelhaven 2.0

3,412 of 4,120 members

83%
Added
3,286
Already in
94
Skipped
32

Respecting Discord's rate limits · about 6 minutes left

The pull reportExample
Added
Now in the new server, with the verified role.
Already in
Joined on their own before the pull reached them.
Skipped
At Discord’s 100-server cap (200 with Nitro), or blacklisted.
Failed
Revoked access in Discord since verifying; their record is deleted.
  • A preflight check first: the bot is in the server, can create invites, and sits above the verified role.
  • A queue that respects Discord’s rate limits, with live progress, pause and cancel.
  • Each login token becomes a short-lived access token in the worker’s memory only.
  • A 24-hour cooldown between full pulls of the same list, unless you confirm an emergency.

Around the three steps

Backups and alerts.

A snapshot of the structure, so the new server looks like the old one before anyone arrives, and a webhook for the moments worth a glance.

BackupsEvery plan

Roles and their order, permissions, categories, channels, overwrites and basic settings. Restore into an empty server with a preview of what will be created.

Manual on every plan, and automatic: monthly on Free, weekly on Plus, daily from Pro. No messages: that needs a privileged intent and stores real conversations.

AlertsWebhook
  • Member verified
  • Verification blocked
  • Alt flagged
  • Pull started
  • Pull finished
  • Backup created

Always

Built for recovery, not growth.

Member-pull bots get banned when they are used to inflate servers. Anchor makes that hard on purpose.

Your servers only
Pulls go into servers you control, where your own bot is.
No list trading
Selling, sharing or "boosting" member lists ends the account.
A cooldown
24 hours between full pulls unless you confirm an emergency.
No privileged intents
The bot runs on slash commands and REST, nothing it does not need.

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.