A Discord bot is priced by what it talks to, not by its number of commands. A welcome bot needs one event and a server to run on, while one that grants a rank on payment, removes it a month later and logs both steps needs a database, a store connection and error handling on both ends. On a feature list, each is one line.
Levels of a Discord bot
| Level | What it adds to the work |
|---|---|
| Webhook notifications | a script on the store or panel side, no permanent connection |
| A few commands | a Developer Portal app, permissions and an always-on server |
| Modules | a database, tickets with transcripts, verification and roles that survive a restart |
| Linked to your systems | ranks after purchase, game accounts tied to Discord, tests on system copies |
| A system with a panel | settings in the browser and sign-in with Discord |
The limits Discord enforces
Discord's documentation allows a bot 50 requests per second and 3 seconds for the first reply to a command. After 10,000 invalid requests in 10 minutes, Discord temporarily locks the whole IP address out of its API. Blind retries during a bulk role update can lock out every bot on the server. That is why we plan rate-limit handling together with the rest of the bot, before it goes live, not after the first lockout.
What the price covers
The quote comes back within an hour. The price covers a test version on a server with your roles, documentation and a standard 90-day warranty, and once the bot is accepted and paid for, the code is yours. Hosting is quoted separately.
Modules and integrations with stores, games and panels are listed on our custom Discord bots page.
Was this post helpful?
