PD DigitalOcean Databases for Blesta

PD DigitalOcean Databases lets a hosting company sell every DigitalOcean managed database as its own package line: PostgreSQL, MySQL, MongoDB, Valkey, Kafka and OpenSearch. Your customer orders on your Blesta order form, a dedicated cluster is built on your DigitalOcean account, and your customer manages it from the service page in your client area: connection details, trusted sources, password reset and activity, under your brand with no DigitalOcean login.

It is the module for hosts who want a full managed-database catalogue from one install. Each package you create is set to one engine, so "Managed PostgreSQL" and "Managed Valkey Cache" are separate things on sale, each with its own price and choices, served by the same module and the same DigitalOcean token. Selling just one engine? The focused edition for it does the same job.

Why hosts choose PD DigitalOcean Databases

Six engines from one install. One module, one licence, one DigitalOcean token and one set of admin screens run all six. Adding an engine later is a new package, not a new module to install and keep updated.

Each engine behaves like itself. Kafka always runs three brokers and shows the SASL_SSL guidance and CA download its clients need. Valkey customers choose their own memory policy. OpenSearch customers get their Dashboards address beside the credentials. Each engine gets its own connect command: psql, mysql, mongosh, redis-cli, kcat or curl.

Every order sets itself up. A paid order creates a dedicated cluster in the region, plan and version the customer chose, with no step by you. Nothing is shared between customers.

Nothing left billing. Cancelling deletes the cluster at DigitalOcean and confirms it is gone, and a retry can never leave a second cluster running unseen.

Customers help themselves. Connection details, a firewall they manage, password regeneration and an activity history sit on the customer's own page, which removes most of the tickets a database product brings.

You keep the margin. You pay DigitalOcean at its own price and set your own sell price, with no per-cluster fee to us. Two engines or more cost less here than as separate single-engine editions.

How it works

1. Connect your DigitalOcean account. Add your DigitalOcean API token once under Settings → Company → Modules, using a token with Full Access, then press Test Connection.
2. Create your package. Make one package per engine you want to sell, for example "Managed PostgreSQL" and "Managed Valkey". In each package's Module Options, pick the engine, then a default region, plan and name prefix. Blesta's cron activates the service after payment.
3. Generate the checkout options. Open the module's Products page and press Generate options. It builds the package's Region, Plan, High availability and Engine version options from DigitalOcean's live catalogue, all priced at zero for you to set. Kafka, which always runs three brokers, gets three options instead of four.
4. Your customer orders. They choose their options and pay. The cluster is built on your DigitalOcean account in the background, and the connection details appear on their own once it is online, usually within a few minutes.
5. You get paid, they manage it. Blesta keeps billing as usual, and the customer copies the connect command and sets their own trusted sources.

What you get in Blesta

Selling and pricing

• One product per engine: PostgreSQL and MySQL (each as Standard or Advanced Edition), MongoDB, Valkey, Kafka and OpenSearch
• Checkout options generated from DigitalOcean's live catalogue for each engine: Region, Plan, High availability and Engine version
• Regions and versions are read live from DigitalOcean
• Generated choices start at zero in every currency and you price each one under Packages → Configurable Options; a sync never changes a price you have set
• Choose which choices customers see at checkout; anything hidden uses your package's default and keeps its price
• Clusters are named with your own prefix and the service number

Provisioning you can trust

• High availability adds nodes for automatic failover: two on PostgreSQL, Valkey and MySQL Standard Edition, three on MySQL Advanced Edition, MongoDB and OpenSearch. Kafka always runs three
• Moving a service to a package for another engine is refused with a message, never applied by resizing the old cluster
• An order DigitalOcean would refuse is stopped with a clear message before anything is created; Atlanta, Richmond and Kansas City carry only Premium plans
• Every cluster is recorded before DigitalOcean is asked to create it, and pressing Create again never builds a second one
• A provisioning failure appears in the service's activity with its reason, never left at "Provisioning"
• A plan change through Blesta's own plan-change flow resizes the running cluster in place; host, port and data are kept
• Suspend replaces the trusted sources with a rule nothing matches: the cluster keeps running (DigitalOcean still bills it), the data is untouched, and the customer cannot lift the lockdown. Unsuspend restores exactly the sources saved
• Terminating deletes the cluster at DigitalOcean with its users, databases and backups, and confirms it is gone. There is no retention period, so tell customers to take their own backup first

Choosing PostgreSQL and MySQL editions

• PostgreSQL and MySQL each come as Standard Edition or Advanced Edition, chosen per package as its Engine
• Advanced Edition needs no partnership with DigitalOcean and offers dedicated plans from 8 GiB RAM; a database keeps its edition, and a move to the other edition is refused rather than resized
• Standard Edition PostgreSQL and MySQL get a Backups page listing DigitalOcean's daily backups; restores are done by you. Other engines show none

Running it day to day

• A Clients & Databases panel lists every cluster against the service paying for it, with engine, plan, region, endpoint and state
• An Activity panel records every provisioning and lifecycle action with its outcome
• A report shows your licence, whether a DigitalOcean account is connected and how many databases you run
• A cluster deleted outside your billing system is flagged to you

What your customers get

On Blesta the customer's pages are tabs on the service: Information, Trusted Sources, Backups (where the engine lists them) and Activity.

• Connection details in one window: host, port, username and password (masked until Show, with Copy beside each), plus a ready-to-use connect command in the engine's own client: psql, mysql, mongosh, redis-cli, kcat or curl
• The CA certificate as a download, for clients that ask for one; the connect command already uses TLS
• Regenerate password in one click behind an in-page confirmation; the new password appears in the connection details
• Trusted sources: add and remove the IPv4 addresses and ranges allowed to connect, with bad entries refused and changes applied within a minute
• Recent activity: their latest actions, up to 40, each marked done or not

The firewall, connection details and backups pages are each a switch on the package: turn one off and it is hidden and refused. The pages render in Blesta's client theme, and every line of customer text is translatable, with overrides that survive updates.

Security built in

• Your DigitalOcean API token is stored encrypted, only ever sent to DigitalOcean, and never shown on a customer page or in a customer message.
• Each database password is stored encrypted and shown only to the signed-in owner of that service.
• Every customer action needs a signed-in owner of the service and a valid security token.
• When something fails at DigitalOcean, the customer sees a neutral message and the reason goes to your activity log.

One product, every feature

PD DigitalOcean Databases is one paid module with all six engines included and no add-on tiers. It installs into PD Modules in one click, updates itself, and uninstalls cleanly, leaving no orphans and modifying no Blesta files.

If your subscription ever lapses, your customers are not cut off. A running database is never stopped, deleted or altered. New provisioning and admin configuration lock first, customers see a neutral "temporarily unavailable" message with their connection details still visible, and cancellations still complete. Renewing restores everything with nothing lost.

Requirements

• Blesta 6.0 or later on PHP 8.2 or later, with the ionCube Loader
• A DigitalOcean account with billing enabled and an API token with Full Access
• Blesta's cron running every minute, which finalises new clusters and confirms cancellations
• PD Modules 0.2.322 or later, the free control panel every PD module installs into