PD DigitalOcean Databases lets you offer PostgreSQL, MySQL, MongoDB, Valkey, Kafka and OpenSearch through Blesta. Each package chooses one engine; customers can then select the choices you expose for that offering.

Before you start

Install PD DigitalOcean Databases through PD Modules and connect the account that will own the clusters. Connect the account holding your module licence inside PD Modules first; entering a licence key is the alternative activation method.

Create the package

Open Packages → Browse Packages → Create Package, choose PD DigitalOcean Databases as the Module and select its intended account. Open Module Options. After choosing Engine, save and reopen the package so the dependent plan and version lists follow that engine.

Choose Engine, including the edition for PostgreSQL or MySQL. Set Region, Plan, Engine version and High availability for that engine. Leaving Engine version blank asks for DigitalOcean’s default when a new cluster is created; it is not a policy that automatically upgrades existing clusters.

Use separate offerings for different engines and editions. Changing the offering later does not turn an existing MySQL database into PostgreSQL or convert its edition. Region and engine version are creation choices; do not sell a change to either as an in-place migration.

Choose customer controls

Review Client: Firewall, Client: Connection details and Client: Backups explicitly on Module Options. An unticked feature is off. Backups appear only for the supported Standard Edition PostgreSQL and MySQL list, even if the switch is enabled for another engine.

Use a resource name prefix suitable for new services. Keep any optional Client Area Section free of provider tokens and private administrative information.

Check the offer before accepting orders

Set the package prices and group. Manage generated choice prices under Packages → Configurable Options. Add the package group to the intended order form. Review paid-pending-services automation and any manual-activation hold.

The catalogue can use cached or fallback choices, and listing a region and plan does not prove their combination is currently available to the selected account. Review DigitalOcean’s engine, edition and regional restrictions before offering it. Creating a real cluster incurs provider charges; an order or active billing service alone is not proof that the database is ready.

After an intended activation, check the database service, connection details and normal cron progress. If the outcome is uncertain, reconcile the existing service and provider result before another create attempt.

See the PD DigitalOcean Databases Blesta guide for related setup, or explore PD DigitalOcean Databases.