Hosting Suite connects cPanel, Plesk, DirectAdmin, Webuzo and Virtualmin accounts, but their available tools differ. Check the combination of provider support, product settings and server permissions before advertising a feature or investigating a missing customer button.
IN THIS ARTICLE
01 Build a practical compatibility checklist
- Identify the provider on the WHMCS server assigned to your test service. Check the saved Hosting Suite connection profile rather than relying on the server's display name.
- Enable that platform in the module, then enable the relevant product and customer tools. The package initially enables cPanel; configure additional providers deliberately.
- Open an active test service owned by the test client. Verify domains, email, databases, PHP information, SSL information, usage, FTP, aliases and account password management as appropriate.
- Test panel login independently. A working API connection does not establish that the server supports the required single sign-on method.
- Record the actions that actually appear for that product and account. Repeat after changing its server package or provider.
02 Understand the installer differences
| Provider | Installer implemented in the account manager |
|---|---|
| cPanel | Softaculous, including installation and supported management, backup, staging and cloning actions |
| Plesk | No account-manager installer capability in this release |
| DirectAdmin | Native WordPress listing and installation |
| Webuzo | Application installation and supported removal, backup, restore and upgrade actions |
| Virtualmin | Application listing, installation, removal and upgrade |
The separate App Hosting product builder currently uses cPanel. Do not interpret an account manager's installer support as support for selling application products through that provider.
03 Check advanced tools separately
cPanel has additional integrations for areas such as DNS, files, scheduled tasks, advanced database management, security, backups, Terminal and Git. Some require a server component, package feature or external provider. JetBackup, Imunify360 and other optional services need their own working configuration. A missing integration should not be resolved by displaying a button that the account cannot use.
What if the documentation and interface disagree?
Check the installed module release, its current capability list and the provider response. Older bundled guidance may describe broader installer support than this release implements. Capture the service, provider, exact action and error for your internal support record, excluding credentials. Use a disposable resource to verify a write operation, then remove that resource after testing. This produces a useful plan-level support matrix for your sales and support teams.