Pre-launch test environment — payments use test credentials and data may be reset before launch.

TournabotDocsProductSign in with Discord
Documentation menu

Docs · Guides

Run the organisation

Branding, staff access, billing, and plan limits.

Website-first install

Sign up on the site, pick a plan, get an install link that already carries the permissions we need.

Install into a Discord server you own or administer. The site checks the bot is present before setup continues. Until that link is healthy, the staff dashboard shows only the setup wizard — not the product menu.

Plans and passes

Plans bill on a 28-day rhythm. Short passes are 2-day, 7-day, and 28-day.

Payment is on Indian rails. When a payment clears, the plan activates on the organisation — if it does not, troubleshooting starts at the payment receipt, not at Discord.

Your bot on paid plans

Free runs on the shared pooled bot (`TOURNABOT_POOLED_APP_ID`). From Scrim upward you get a dedicated Discord application — **platform-owned pool claim by default (D-71)**; create-your-own in the Developer Portal (D-53) remains the secondary path.

That dedicated identity is what opens message-based registration on your own token. Circuit adds managed branding and removes the platform mark from what we render.