Everything a server actually needs
Set up any feature from its own command — /welcome opens one message with every setting and a single on/off button — or from the dashboard, where each server is a sidebar of switches and every setting is a picker. The few that start on are marked on the docs page.
Moderation
Ban, kick, timeout and warn, every action numbered and searchable. Hierarchy is checked before anything happens, so nobody can act above themselves.
Verification
A CAPTCHA the bot draws itself — no third party sees your members for it, because the image is rendered in process. Of everything in verification, only the optional VPN check asks another service, and the privacy page names which.
Anti-raid & anti-nuke
Join-rate detection, mass-action limits and a lockdown that remembers what it changed so it can put it back. Switched on means acting: the limits and the response are yours to set.
Tickets
Private channels or threads opened from a panel, with questions, claiming and transcripts. Message content is never stored: a transcript is built from Discord’s own history when it is needed, and sent on rather than kept.
Logging
Deleted and edited messages, joins, leaves, roles, channels, voice. Every log says who did it, sourced from the audit log rather than guessed.
Applications & appeals
Staff openings people apply for, reviewed and voted on in private. Banned members can appeal by DM, and an approved appeal reverses the punishment itself.
Giveaways & events
Timed draws with entry by button, eligibility bars you set, and a fraud check for accounts made for the draw. Events take their own sign-ups, send reminders, and record who actually turned up.
Backups & migration
Snapshot your roles, channels, categories, permission overwrites, emoji and ban list — then rebuild a server from it, or carry it to a new one as a file. A rebuild survives a restart and resumes where it stopped.
Ranks & rosters
A ladder of ranks with requirements, a roster, and a contribution ledger where every number has a reason and an author. It will tell you who has earned a promotion, who has gone quiet, and who has been waiting longest.
Analytics
Who is active, which channels are busy, and how the server moves through the day — over a window you choose. The charts are drawn here, and a chart with one measurement draws one column rather than a confident flat line.
Every server, every setting, one place
Sign in with Discord and pick a server. Every feature is a card with its own switch, and every setting — channels, roles, limits — is a picker. There is no account to make and no password, and you can take the access back from Discord’s own settings at any time.
Sign in once
The standard Discord consent screen, asking for your name and your server list — no email, no messages. After that this browser remembers you, so coming back opens your servers directly. Logging out ends the login at Discord too, not just in this browser.
Pick a server
Every server where you hold Manage Server, the ones sick is already in listed first. The same permission the setup commands check inside Discord, so nothing is offered here that would be refused there.
Switch it on, tune it
Each feature is a card with a switch. Open one for its settings: channels and roles are pickers, and the bot checks every change against your server before it saves anything. Servers without sick get a button that adds it to that exact server.
Three steps
Add the bot
It asks for exactly the 29 permissions its code actually uses — no more, and you can untick any of them.
Move its role up
Discord will not let any bot act on a member whose highest role sits above its own. Drag sick above the roles you want it to manage.
Type a feature’s name
/welcome,/logs,/antinuke— each opens one message with every setting, a picker for each, and one button that turns the feature on or off. Changing a setting never switches anything on by itself.
The parts most bots do not tell you
The CAPTCHA is drawn here
Verification renders its own image in process. There is no captcha provider behind it, so nobody is handed your members’ addresses in exchange for a score.
Addresses are not kept
The bot never sees one — Discord does not expose them. The optional VPN check looks the connecting address up once, on the website, and keeps nothing. A wrong password or code at a sign-in is counted against a keyed fingerprint of the address — never the address itself — so that too many tries can be paused, and each count is deleted after a day.
Message content is not kept
Nothing said in your server is stored in our database. A ticket transcript is built from Discord’s own history and posted back into your server as a file. Snipe keeps the last few deleted or edited messages in memory only — a restart forgets them. The reason somebody gives for being AFK is kept too — until they return, thirty days at most — because it is shown to anyone who mentions them.