It is not our bot with your logo.
It is your bot.
You create the Discord application. We operate it for you as your service provider. Your members never encounter our name, because it is genuinely not involved.
An avatar and a bio
- Still their application, their name in the member list
- Reverts to their branding the moment it sends a DM
- Shares one 50-request-per-second budget with every other customer
- Their verification badge, or none
- Dashboard on their domain, with their name on it
Your application, end to end
- Your bot in the member list, in DMs, everywhere
- Your own OAuth invite carrying your client id
- Your own rate limit, unaffected by anyone else's busy day
- Your verification badge and App Directory listing
- Your domain, your logo, your colours, no mention of us
Is handing over a bot token allowed?
Yes, and Discord names the exact structure. It is worth answering precisely, because the arrangement looks like credential sharing and the rule that appears to forbid it is real.
Discord's Developer Terms require you to use your credentials solely with your own application, and not to permit any other application to use them — and then add a carve-out for Service Providers, subject to section 12(a). Section 12(a) sets out what that arrangement has to look like.
So the shape is not something we invented to get around a rule. It is the shape the rule describes. Five obligations fall straight out of it, and each one is a thing the product does rather than a promise it makes:
A written agreement, first
You have to require us, in writing, to use your credentials only for you and for no other purpose. It is the gate the token field sits behind — not a checkbox next to the submit button — because the terms require the direction to exist before we hold the credentials.
Encrypted at rest
Stated in the terms, not merely good practice. Sealed with AES-256-GCM before they are written, never logged, and never displayed again — not even masked, because a mask still leaks a length.
Your token drives only your application
Every record we hold is scoped to your application id. There is no query in the system that reads tenant data without it. We verify on connection that the token really does belong to the application id you gave, so two customers cannot cross wires.
Offboarding deletes everything
One button. Your credentials are erased in the same statement that marks the account closed, so there is no window in which a disconnected tenant still has a usable token sitting in a table. Your Discord application itself is untouched and stays yours.
The liability is yours, and we say so plainly
Discord's terms make you solely responsible for a service provider's acts as if they were your own. That is a real risk and it belongs on this page rather than in a footnote. Discord may also prohibit your use of any service provider it believes has violated its terms — which is a kill switch on this tier, held by Discord.
What you actually do
About ten minutes, most of it in Discord's own portal. Four of these need a human signed in to the account that owns the application, so they cannot be done for you.
Create an application and add a bot
In Discord's developer portal, under your own account. It is yours from this moment and stays yours.
Paste the id, token and secret here
We ask Discord to confirm the token before we store anything, so a half-copied paste fails immediately with a sentence rather than later with a mysterious 401.
Add two URLs in the portal
An OAuth redirect, so your staff can sign in, and an interactions endpoint, so your bot receives commands over HTTPS instead of holding a socket open. The dashboard shows both, ready to copy.
Invite your bot and register its commands
Your invite link, carrying your client id. Then one click to register the slash commands on your application.
One trap worth knowing before you hit it
Do not set your bot's banner in the developer portal. That page never loads an existing banner back into its upload control, so every Save on it submits the field empty and deletes a banner you already had — including on an unrelated save. It reads as "the banner will not stick" and it is really "something else on this page is deleting it". Set it from the dashboard, which sends only the fields you actually named.
Ready when you are
Sign in, connect your application, and your members will never see anyone's name but yours.
Connect your application