Docs
Find what you need
Setup takes about two minutes and needs no configuration. Everything after that is optional: every command and every template token is written down, and the self-hosting guide runs the exact same code we host.
Start hereGetting started
Add the bot, run /setup, and watch your first room name itself.
Reference
Look something up
How it works
Creator channels, rooms, and who owns one. The model underneath every command in the reference below.
See the modelCommands
Every slash command, grouped by who can run it: room owners, any member, and admins with Manage Channels.
Browse commandsName templates
The full token language, with a playground at the top to try it in before you read the tables.
Learn the tokensTemplate assistant
Describe the names you want in plain language and it writes the template. Including which language it answers in.
Skip the syntaxBilling
How pricing, trials, and subscriptions work, including adding unlimited servers to one plan billed by their combined size.
Read about billingWhen it misbehaves
Something stopped working
Nearly every problem is one permission in one place, and Discord reports all of them the same way, which is why the obvious checks come back clean.
Troubleshooting
Rooms not appearing, names not updating, game names missing, or AVC paused. What each message means and the permission that actually fixes it.
Find the symptomYour hardware
Or run it yourself
Self-hosting is not a stripped-down community edition. It is the same container we deploy, with billing dormant, and it needs a bot token and Docker.
Self-hosting
Migrations apply themselves and slash commands register themselves, so past dropping your bot token into a .env it is one command:
docker compose up
When the docs run out