Offer a managed Valkey service through PD DigitalOcean Valkey. Valkey is a Redis-compatible in-memory datastore; decide whether the offering is intended for disposable cache data or an application with stricter retention needs.

Connect the intended account

Install PD DigitalOcean Valkey through PD Modules and connect the provider account that will own the clusters. In PD Modules, connect the account holding your licence first; entering a licence key is the alternative activation method. A passing provider account test does not prove cluster-write permissions or capacity.

Set the resource defaults

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

Review Region, Plan, Engine version and High availability on Module Settings. Valkey is the fixed engine. Blank Engine version asks DigitalOcean to choose its default for a new cluster; it is not an automatic upgrade policy for an existing service.

Choose capacity and availability

With High availability enabled, the module requests a primary and one standby node. Review the selected plan, region and provider costs for that layout. Catalogue choices can be cached, stale or from fallback data, so a listed combination is not proof of current capacity.

High availability is separate from retention and recovery. It does not decide which keys the application may discard when memory is full, and it is not proof of a tested backup or recovery procedure.

Review client controls and activation

Set Client: Firewall and Client: Connection details explicitly. Customers can manage their allowed addresses and credentials when enabled. The generic Client: Backups field does not add a Valkey client backup list or restore control. Review the service’s Memory policy against the application’s intended use before handing it over.

Set product prices and the automatic-setup policy, including whether creation should follow the first payment. An Active billing service alone does not prove that the module created a Valkey cluster.

Creating a real cluster incurs provider charges. After an intended activation, check the service’s module state, normal cron progress and connection details. If creation is uncertain, reconcile the existing service and cluster before retrying. Region and version are creation choices, not ordinary in-place migrations.

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