What the bot can actually do
Most hosting bots report status. This one runs the server.
You can start, reboot, shut down, force stop and hard reset, and read live CPU, memory, disk and network usage while you do it. You can create, restore, lock and delete backups. You can review your firewall rules, add and delete them, and change the default policies. You can set the reverse DNS for each of your addresses, rename a server, reinstall it with a different operating system, mount an installer image, open a one-time console link and reset the administrator password.
That is the same surface the customer portal gives you, minus billing. Anything that would charge you links out to the portal instead, which means handing someone the bot is not handing them your payment method.
Why chat instead of a dashboard
A dashboard is somewhere you go. Discord is somewhere you already are.
When a game server stops responding mid-session, the distance between noticing and fixing it is the whole problem. Opening a browser, finding the tab, logging in, navigating to the right server and pressing reboot is four or five steps during which everyone is still waiting. Typing /menu on your phone is one.
This matters most for the people who run something with other people in it — community servers, game servers, small teams. The person who needs to restart the machine is often not the person who owns the hosting account, and getting them portal credentials is a bad answer to that problem.
Privacy in a shared channel
The obvious objection to running infrastructure from a public chat is that a public chat is public.
Every reply the bot sends is ephemeral: it renders only for the person who pressed the button, and it is gone when they dismiss it. Server names, IP addresses, usage graphs and console links are never visible to anyone else in the channel, and they are never written into the channel history.
Destructive actions ask first. Restoring a backup, reinstalling an operating system and force-stopping a machine all require a confirmation step, so a mis-tapped button on a phone does not take a production server down. Console links are single-use and expire after ten seconds — long enough to click, short enough that a screenshot is worthless.
Roles for your community
If you run a Discord community, the bot can grant roles from your Virtbase data without anybody checking manually: how many servers a member currently rents, whether their email address is verified, and how long they have been a customer.
What it shares is exactly those three values, and only for the roles the server is configured to grant. Email addresses, server names and IP addresses are never passed to the Discord server.
Getting started
Link your Discord account once on your authentication settings page, then run /menu. If you run it before linking, the bot walks you through the setup rather than showing an error.
You do not need to add the bot to a server of your own — if it is already in a server you are a member of, it works there, and it works in direct messages. The full walkthrough is in how do I manage my servers from Discord.