Vultr Integration
Connect your Vultr account to Devpilot to provision and manage cloud compute instances for your deployments.
Vultr Integration
The Vultr integration connects your Vultr account to a Devpilot workspace using a personal API key. Once connected, Devpilot can provision Vultr cloud compute instances on your behalf, install the Devpilot agent on them, and manage their lifecycle.
Prerequisites
- A Vultr account with billing enabled
- An active Devpilot workspace
Required Credentials
Devpilot stores the following fields for a Vultr integration:
| Field | Description |
|---|---|
| Access Key | A descriptive label for the key (used as the integration's display value). |
| Secret Key | Your Vultr personal API key. |
Vultr uses a single API key as a bearer token. Devpilot keeps a two-field form for consistency — the Secret Key field holds your API key, and Access Key acts as a label.
Generating a Vultr API Key
Open Account Settings
Sign in to the Vultr Customer Portal and open Account > API.
Enable API Access
If API access is disabled, enable it. Vultr may also ask you to whitelist the IP addresses that can use the key. If your Devpilot instance has a static egress IP, add it here; otherwise disable the IP allowlist while testing.
Copy Your API Key
Copy the Personal Access Token shown on the API page. Treat it like a password.
Connect Vultr in Devpilot
Go to Workspace Settings > Integrations and select Connect on the Vultr card. Enter a label in the Access Key field and paste the API key into the Secret Key field.
Validate and Save
Devpilot validates the key against the Vultr API before saving. If validation fails, double-check the key value and the IP allowlist.
What Devpilot Does on Vultr
When you provision a server, Devpilot:
- Creates a Vultr cloud compute instance in the selected region and plan
- Adds an SSH key to the instance
- Configures a firewall group with the ports the deployment needs
- Tags the instance with workspace metadata
- Installs the Devpilot agent
Testing and Rotating Credentials
Open the integration and select Test Credentials to re-run validation. To rotate, regenerate the API key in Vultr's API settings and update the Secret Key in Devpilot.
Regenerating a Vultr API key invalidates the previous one immediately. Update the Devpilot integration at the same time to avoid provisioning failures.
Troubleshooting
Credential Validation Fails
- Confirm API access is enabled in Account > API.
- If the IP allowlist is enabled, make sure Devpilot's egress IP is included (or disable the allowlist).
Instance Provisioning Fails
- Some plan and region combinations sell out temporarily — try another region or a different plan.
- Check your account's resource limit and billing status in the Vultr portal.
Disconnecting Vultr
Open the Vultr integration and select Remove. Stored credentials are deleted from Devpilot. Vultr instances already provisioned through Devpilot are not destroyed — manage them from the Vultr customer portal if you no longer need them.