Use PD DigitalOcean MongoDB to offer a managed MongoDB cluster under your own hosting brand. Define its region, size, version and availability before accepting orders.

Connect the intended account

Install PD DigitalOcean MongoDB 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 test is separate from proving database-write permissions or regional capacity.

Set the MongoDB defaults

Open System Settings → Products/Services → Products/Services, create an Other product and choose PD DigitalOcean MongoDB 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. The engine is fixed to MongoDB. A blank Engine version requests DigitalOcean’s default for a new cluster; it does not set an automatic version-upgrade policy for existing databases.

Choose the availability layout

With High availability enabled, the module requests a three-node replica set rather than the base single-node layout. Extra nodes affect provider costs. Choose a supported plan for that layout and region; the module’s catalogue may be cached or use fallback choices, so the list is not proof of current provider capacity.

A replica set supports availability, but it is not a backup or an application recovery test. Do not promise that enabling it removes every connection interruption or data-loss scenario.

Choose client controls and activation

Review Client: Firewall and Client: Connection details explicitly. The customer’s Trusted Sources and credential controls depend on those switches. The module does not expose a MongoDB client Backups tab, even when the generic Client: Backups field is on. That interface limitation does not mean DigitalOcean has no managed MongoDB recovery facilities.

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

After an intended activation, check the service’s database state, normal cron progress and saved connection details. Creating a real cluster incurs provider charges. If the create outcome is uncertain, reconcile the existing service and cluster before repeating it.

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