Panelbotdocs
SearchStart free

Supported platforms and integrations

Which control panels, billing portals, server software, and hosting tools Panelbot works with, what it does with each, and what is not supported today.

Control panels

cPanel and WHM. The deepest support, and where most of our customers run. Accounts, email, databases, DNS, SSL, disk and inode usage, firewall state, and the WordPress paths that sit on top of all of it.

DirectAdmin. Covers the common hosting flows: accounts, email, databases, DNS, SSL, and the usual diagnostic paths. It is genuinely supported rather than experimental, but if a rare corner exists it is more likely to be a cPanel corner we have already met.

Nothing else is supported today. If you run Plesk, HestiaCP, or your own panel, Panelbot is not a fit yet, and we would rather tell you now than after you have signed up. Say so anyway if you are interested, because what people ask for is how we decide what to build.

Billing portals

WHMCS and Blesta. The widget loads inside your client area, so a conversation starts already knowing who the customer is, which services they have, and which server those services live on. That identity is the reason the assistant can act on an account without asking the customer to prove who they are all over again.

Other portals are not supported today. The same invitation applies: tell us.

Hosting tools we work with

These are detected on your servers rather than configured by you. If they are there, the assistant uses them; if not, it works without them.

CloudLinux. Resource limits are part of the picture when a site is slow, so the assistant reads LVE limits and faults rather than guessing at “the server is busy”.

Imunify360. Malware findings and blocked IPs feed the security and access diagnostics, so a customer locked out by a security rule gets a real reason instead of a shrug.

JetBackup. Restores are one of the highest-value things a customer can ask for at 2am, and one of the easiest to get wrong. The assistant can list what is available and, with confirmation, restore.

Softaculous. Application installs and the state of what is already installed.

What you need to connect a server

Panelbot connects over the panel API, so the requirements are the panel’s own:

  • A Linux server running cPanel/WHM or DirectAdmin, reachable on its normal API port.
  • A panel credential for Panelbot to use: a WHM API token for a root or reseller user on cPanel, or a login key for an admin or reseller user on DirectAdmin. A reseller credential is enough; you do not need root, and you do not need to ask an upstream host to whitelist anything.

Nothing is installed on the server. See Connect your first server.

If you install the optional agent

The server agent is optional and only for jobs a panel credential cannot reach on your setup. If you choose it, the server also needs:

  • Python 3.9 or newer, which is already present on essentially every panel box.
  • Outbound HTTPS on port 443, plus outbound access to the TLS message bus port (6379 by default). No inbound ports are opened. On a CSF server the installer adds the bus rule to /etc/csf/csf.allow itself; see What the installer puts on your server.
  • Root access to run the installer once. The agent that gets installed does not keep it.

We deliberately do not publish a table of blessed OS versions. Panel servers vary more than any list would honestly capture, and the installer checks the machine in front of it and tells you if something is missing. That is a more reliable answer than a version matrix that goes stale.

What is not supported

Windows servers. Panels other than cPanel and DirectAdmin. Billing portals other than WHMCS and Blesta. Bare servers with no panel at all, since the panel is how the assistant understands who owns what.