Offer managed MySQL through PD DigitalOcean MySQL, with an edition and defaults that match the service you intend to sell.

Connect the intended account

Install PD DigitalOcean MySQL through PD Modules and connect the provider account that will own the clusters. Connect the account holding your module licence inside PD Modules first; a licence key is the alternative activation method. The provider account read test is separate from proving database-write permissions and capacity.

Save the MySQL defaults

Open System Settings → Products/Services → Products/Services, create an Other product and select PD DigitalOcean MySQL on Module Settings. Assign the intended server group, whose server stores your DigitalOcean token in Password.

Choose MySQL — Standard Edition or MySQL — Advanced Edition as Engine, then review Region, Plan, Engine version and High availability on Module Settings. Use a separate offering for each edition you sell. Blank Engine version asks for DigitalOcean’s default when creating a cluster; it is not an automatic upgrade policy for an existing database.

Match the edition and customer controls

Review the current Standard Edition new-cluster limits before offering large plans or standby nodes. The module’s Advanced Edition high-availability layout has three nodes; eligible Standard Edition clusters use a primary plus one standby. A listed choice does not establish availability for every region or account.

Set Client: Firewall, Client: Connection details and Client: Backups explicitly. This module lists client backups for Standard Edition MySQL only; the backup switch does not add an Advanced Edition backup page.

Check activation and the intended service

Set product prices and its automatic-setup policy, including whether creation should follow the first payment. An Active billing service alone does not establish that a database has been created.

Creating a real cluster incurs provider charges. After an intended activation, check the database service, normal cron progress and connection details. Catalogue data can be cached, stale or from fallback choices, so inspect the actual provider result before handing the service to its customer. If creation is uncertain, reconcile the existing service and cluster before repeating it.

Region, engine version and edition are not ordinary in-place migrations. Do not move an existing service to another edition expecting a routine resize.

See the PD DigitalOcean MySQL WHMCS guide for related setup, or explore PD DigitalOcean MySQL.