Control Panel Integration
Devpilot detects hosting control panels on your server and integrates with them for app installs, credentials, and status.
Control Panel Integration
If your server already runs a hosting control panel — aaPanel, cPanel, Plesk, CyberPanel, or CloudPanel — Devpilot can detect it, store credentials for it, and use its API for features like the App Store. You don't have to abandon your panel to manage the server in Devpilot.
Control panel integration is optional. On a bare Ubuntu server with no panel, Devpilot manages everything directly over SSH. When a panel is present, Devpilot simply adds a safer path that goes through the panel's own API where appropriate.
Supported Panels
aaPanel (including BT-Panel)
Devpilot's deepest panel integration. When aaPanel is detected, the App Store uses its API to install web servers, databases, and runtimes that aaPanel already knows how to manage.
- Default admin port:
8888 - Integration style: API key (bt key)
cPanel / WHM
Devpilot detects cPanel and marks the server as panel-managed so system-level changes stay in your control.
- Default WHM port:
2087 - Integration style: API token
Plesk
Detected by Devpilot. The server is flagged as Plesk-managed to keep Devpilot's automation from fighting with Plesk's own configuration.
- Default port:
8443 - Integration style: username and password
CyberPanel
Detected by Devpilot. Installed software owned by CyberPanel is tagged as panel-managed in the App Store.
- Default port:
8090 - Integration style: username and password
CloudPanel
Detected by Devpilot. System packages managed by CloudPanel are flagged so Devpilot won't overwrite them.
- Default port:
8443 - Integration style: username and password
Today, deep App Store integration (installing apps via panel API) is available for aaPanel. The other supported panels are detected and flagged, and you can still store credentials for them, but the App Store installs on those panels are treated as coming soon.
How Devpilot Detects Your Panel
Detection runs over SSH using a small set of safe, read-only checks:
| Panel | What Devpilot checks |
|---|---|
| aaPanel | Presence of /www/server/panel/ files |
| cPanel/WHM | Presence of /usr/local/cpanel/cpanel |
| CyberPanel | Presence of /usr/local/CyberCP/ |
| Plesk | Presence of /usr/local/psa/version |
| CloudPanel | Presence of /home/clp |
Devpilot also captures the version string where possible.
Running detection
Open the Control Panel section
From a server's detail page, open Settings and look for the Control Panel card.
Click "Detect Panel"
Devpilot opens an SSH session, runs the detection commands, and stores the result on the server. If a panel is found, Devpilot also attempts to auto-detect its API credentials in the background.
Review the result
You'll see the detected panel type, its version, and whether credentials were auto-detected or need to be entered manually.
Storing Panel Credentials
Some features (notably the App Store's panel-API install path) need to talk to the panel itself. Credentials are stored encrypted per server and never leave your workspace.
You can provide any of the following, depending on the panel:
- API URL — The panel's admin URL (for example,
https://server.example.com:8888). - API key — Used by panels that authenticate with a key (for example, aaPanel's bt key).
- Username and password — For panels that still use basic credentials.
- Port — Overrides the panel's default port if you've changed it.
Credentials are optional. Without them, Devpilot still knows a panel is present and flags software it owns — the App Store just uses direct install methods instead of panel API calls.
Verify credentials
After saving credentials, click Verify. Devpilot makes a test call to the panel and updates the Verified timestamp on success. If verification fails, double-check the URL, port, and token.
Remove credentials
Click Remove Credentials to delete the stored credentials for that server. The panel itself is untouched — only the saved secrets are removed from Devpilot.
What Integrates with Panels
Once a panel is detected, the following Devpilot features become panel-aware:
- App Store — Software already managed by the panel is tagged (for example,
Managed by aaPanel) so you don't accidentally reinstall it through a different method. For aaPanel, installs flow through the panel API. - Server info — The server detail view shows the panel type, version, and detection time.
- Automation safeguards — System-level scripts avoid overwriting files owned by the panel when the panel is flagged as present.
What's Not Included
- Provisioning a new server with a panel pre-installed — Provisioning currently delivers a plain Ubuntu host. Install your panel afterward, then run detection.
- Single sign-on into the panel UI — Devpilot doesn't open the panel's own admin interface for you. Log in to your panel directly when you need its full UI.
- Panel installation from Devpilot — The App Store installs individual apps. Installing the panel itself is a one-time manual step.
Next Steps
Server App Store
Browse, install, and manage server software from the Devpilot app catalog. Web servers, databases, caches, runtimes, security, and utility tools installed through your control panel or package manager.
File Transfer
Transfer files between two servers in your Devpilot workspace. Track progress, review history, and retry failed transfers.