Connect DigitalOcean, Akamai, or Vultr.
ServerChirp can create servers through connected DigitalOcean, Akamai Cloud (Linode), and Vultr accounts. You can also connect a compatible server from another provider using managed SSH or the bootstrap command.
Open Settings → Integrations, choose a provider, and add an API credential with permission to create and inspect compute instances. ServerChirp encrypts the credential and never returns its secret value through the API.
After connecting, ServerChirp synchronizes the provider's regions, sizes, images, and available price metadata. Refresh the provider when a recently added region or size is missing.
From New server, choose the provider connection and then select:
The cloud bill remains with the provider. Deleting or disconnecting a ServerChirp resource does not imply that every provider-side resource should be destroyed; the confirmation flow tells you exactly what will happen.
For providers without a native integration, create the instance yourself and use server provisioning. Register its IPv4 address and SSH port, run a supported Ubuntu LTS release, and make sure it has the required outbound connectivity. Managed SSH also requires ServerChirp to reach that SSH address during provisioning.
Prefer a provider credential dedicated to ServerChirp. Rotate it if it is copied outside your password manager or if an administrator leaves the team. Removing the credential stops new provider operations but does not disconnect agents already running on existing servers.
