One subscription is one server
Not per seat, not per agent. Add as many staff as you like.
Standard
Genuinely usable, not a demo.
- Unlimited panels and ticket types
- Ticket forms and the full embed builder
- All ~50 variables and 11 modifiers
- Support roles and the 9 permission editors
- Custom commands
- Manual transcripts
- Logging, and 7 days of statistics
- Config backup, restore and transfer
- The ticket queue
Premium
Everything, on our shared bot.
- Everything in Standard
- Automatic transcripts
- Direct messages on ticket events
- The whole automation engine
- Claiming, and thread-mode tickets
- Role changes on ticket state change
- Scheduled support hours
- Custom and animated emoji on buttons
- Per-server bot appearance
- Full statistics history
- Web ticketing and documentation answering
White label
Your own Discord application.
- Everything in Premium
- Your bot, your name, your icon
- Your verification badge and directory listing
- Your own OAuth invite link
- Your own rate-limit budget
- Dashboard on your own domain
- Your logo and colours throughout
- No reference to us anywhere
Prices are the intended tiers for this build. Billing is not wired up yet, and this page says so rather than taking a card it cannot charge.
Questions people actually ask
Why is white labelling three times the price?
Because it is a different product, not a better version of the same one. A bot that is genuinely yours has its own rate-limit budget, its own verification standing, and its own encrypted credentials that we are contractually bound to handle in a specific way. That is operations work per customer, which the shared tier does not have.
Can I move a subscription between servers?
Yes. A subscription belongs to whoever bought it, not to the server it is currently pointed at.
What happens to my settings if I stop paying?
Nothing is deleted. Premium screens become read-only, so you can still see exactly what you configured rather than finding it apparently gone. Turn the subscription back on and it all works again.
Do you read our tickets?
No, and you can make that structural: point transcripts at your own Google Drive and the messages never touch our storage at all.
Is this finished?
No, and the site does not pretend otherwise. Sign-in, install, the configuration surface and the ticket lifecycle work today. The queue, web ticketing, documentation answering and billing are being built in that order.