Offer a dedicated DigitalOcean managed Kafka cluster through PD DigitalOcean Kafka. The product defines the region, broker plan and version you sell; it does not configure the customer’s application topics or consumers.

Connect the intended account

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

Create the product

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

On Module Settings, set Region, Plan and Engine version. The engine is fixed to Kafka. Leave Engine version blank only when you intend DigitalOcean to choose its default for a new cluster. A stored version choice is not an automatic upgrade policy for existing brokers.

Understand the broker layout

This module creates a three-broker cluster. Its generic High availability field has no additional effect for Kafka, and the checkout generator does not add a separate high-availability choice. Do not equate the provider’s broader node-count limits with a broker-count selector in this module.

Choose a supported Kafka plan and region together. Catalogue data can be cached or come from a fallback list, and a listed plan does not prove that it is offered in every region. Review provider costs before enabling provisioning.

Choose client controls and activation

Review Client: Firewall and Client: Connection details explicitly. The customer can use Trusted Sources, connection details and password regeneration when enabled. Kafka has no client Backups tab in this module, regardless of the generic Client: Backups field.

Review the product’s automatic-setup setting, including whether creation should follow the first payment. An Active service is not proof that the module was invoked or the cluster is ready.

After an intended activation, check the service’s module state, normal cron progress and connection details. If a create outcome is uncertain, reconcile the existing cluster before retrying; do not order another billable cluster merely to inspect the interface.

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