Sell managed MySQL databases on DigitalOcean under your own brand — provisioned, billed and managed in Blesta
Made and supported by Projektif Digital Ltd. Runs inside PD Modules, the panel every module installs into.
PD DigitalOcean MySQL lets a hosting company sell DigitalOcean managed MySQL as its own database package. Your customer orders on your Blesta order form, a dedicated MySQL cluster is built on your DigitalOcean account, and your customer manages it from the service page in your client area with your branding, never needing a DigitalOcean login. You set the price, DigitalOcean bills you its own price, and the difference is your margin.
MySQL is the database most web applications already expect, which makes it the easiest managed database to sell to existing hosting customers who have outgrown a database on a shared server. It is built for hosts who want a MySQL line with its own backups, failover and access control, without running database servers or answering a ticket for every allowed-IP change.
A dedicated MySQL cluster per customer. Each order gets its own cluster in the region, plan and version the customer chose. Nothing is shared with another customer, so one tenant's load never lands on another's database.
Standard or Advanced Edition, your choice. The edition is set per package as its Engine. Advanced Edition needs no partnership with DigitalOcean and offers dedicated plans from 8 GiB RAM, so you can sell a small starter database and a larger production tier from the same module.
Failover you can price. High availability is a checkout option you price yourself: one standby node on Standard Edition, two on Advanced Edition.
Backups the customer can see. DigitalOcean backs the cluster up every day, and a Standard Edition database's Backups page lists those backups with date and size. Restores are done by you.
Customers help themselves. A copy-ready mysql command, a CA certificate download, password regeneration and an allowed-address list sit on the customer's own page.
Nothing left billing. Cancelling deletes the cluster at DigitalOcean and confirms it is gone, even after a licence lapse.
On Blesta the customer's pages are tabs on the service: Information, Trusted Sources, Backups (where the engine lists them) and Activity.
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.
PD DigitalOcean MySQL is one paid module with everything included: both editions, high availability, backups listing, trusted sources and password reset. There are no add-on tiers to compare. It installs into PD Modules in one click, updates itself, and uninstalls cleanly: its own tables and settings are removed and no Blesta files are modified.
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.
Whichever versions DigitalOcean currently offers for MySQL. The module reads them from DigitalOcean's live catalogue when it generates the package's options, so retired versions drop out and new ones appear when you regenerate. If you hide the Version choice, every order gets the version set on the package.
In PD Modules → DigitalOcean MySQL → Products, choose Generate options. The module writes the package's Blesta configurable options — Region · Plan · Version · High availability — from DigitalOcean's live catalogue. You set the prices under Packages → Configurable Options, and you can choose which of the choices customers see.
It provisions standby nodes beside the primary, so the cluster keeps serving through a node failure: one standby on Standard Edition, three nodes (a primary and two standbys) on Advanced Edition. DigitalOcean bills the extra nodes, so price the option accordingly. New Standard Edition databases can no longer have standby nodes from 30 November 2026 (from 15 October 2026 on DigitalOcean accounts that have never created a PostgreSQL or MySQL cluster).
Yes, through MySQL Advanced Edition. DigitalOcean is limiting new Standard Edition MySQL databases to plans up to 4 GiB RAM with no standby nodes — from 15 October 2026 for DigitalOcean accounts that have never created a PostgreSQL or MySQL cluster, and from 30 November 2026 for every account. Databases created earlier are not affected. Larger plans and high availability continue in MySQL Advanced Edition, which you choose per package — it is part of DigitalOcean's public API for any account, with no partnership or special subscription needed. Plans there start at 8 GiB RAM and DigitalOcean prices them separately, so check its pricing before you set yours. From 30 November 2026 a Standard Edition package stops offering larger plans and high availability, and an order over the limit is stopped before anything is created, with a message naming Advanced Edition.
Yes. When the customer changes the plan option or moves to another package, the running cluster is resized at DigitalOcean and the data is kept. The region is fixed when the cluster is created.
From the Trusted Sources tab on their service. They add their application servers' addresses, and once any are added only those can connect. Every connection is encrypted with TLS.
Yes. DigitalOcean takes automated daily backups of every MySQL cluster at no extra charge, and for a Standard Edition database customers see the list on their service's Backups tab.
Suspending locks the cluster's trusted sources so nothing can connect, and leaves the data untouched; DigitalOcean still bills a suspended cluster. Unsuspending restores the customer's own list. Cancelling deletes the cluster at DigitalOcean, so ask customers to export anything they need first.
Yes. You resell from your own DigitalOcean account, at your own margin. You add it once in Blesta under Settings → Company → Modules → Manage, as a module row holding a Personal Access Token with full access. The token is stored encrypted on your Blesta server, is only ever sent to DigitalOcean, and is never shown to a customer.
No. A licence lapse withdraws the management layer in stages but never stops, deletes or alters a running customer cluster. Your customers keep serving throughout.
Blesta 6.0 or later, on the PHP version Blesta 6 itself requires (8.2 or later), with PD Modules 0.2.322 or later and Blesta's cron running. It adds its own tables and pages rather than modifying Blesta's files, so it does not collide with other vendors' modules or a customised template, and uninstalling removes its own tables and settings.
Open a ticket from your client area, or use Get help inside the PD Modules panel, which attaches a diagnostic report — you see a preview of exactly what it contains, and can exclude any part of it, before anything is sent. Support is included with an active subscription; bug reports are welcome whatever your licence state.
Sell managed PostgreSQL, MySQL, MongoDB, Valkey, Kafka and OpenSearch under your own brand — provisioned, billed and managed in Blesta
Sell DigitalOcean Spaces object storage under your own brand — provisioned, metered and billed in Blesta
Sell cloud servers on DigitalOcean under your own brand — provisioned, billed and managed in Blesta
Sell managed Kubernetes on DigitalOcean under your own brand — provisioned, billed and managed in Blesta
Terms and Conditions · Privacy Policy
PD Hosting is the trading name of Projektif Digital Ltd, registered in England and Wales, company number 12482555.
