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
Made and supported by Projektif Digital Ltd. Runs inside PD Modules, the panel every module installs into.
PD DigitalOcean Kubernetes lets a hosting company sell managed Kubernetes clusters as its own Blesta package. Your customer orders in Blesta, a dedicated cluster is built in your DigitalOcean account, and your customer downloads a kubeconfig from your client area and runs kubectl within seconds, without ever having a DigitalOcean login. You set the price, DigitalOcean bills you its list price, and the difference is your margin.
It is built for hosts who want to offer container hosting to developers and agencies without operating control planes themselves, and without handing out access to their provider account.
Sell managed Kubernetes under your own brand. Customers see your company, your prices and your client area. Clusters run on your own DigitalOcean account, so customers need no account of their own, and your account and API token are never exposed to them.
Every paid order sets itself up. When Blesta activates the service, through its Provision Paid Pending Services task or a staff member pressing Activate, a dedicated managed cluster with one worker node pool is created exactly once, in the region, node plan and node count the customer chose. Once it is running, its API endpoint and node pool are recorded and shown to the customer.
Connect in one click. The customer downloads their kubeconfig from the service page, with the endpoint and numbered kubectl steps beside it. It gives access to their cluster only, never to your DigitalOcean account, and only the owner of the service can download it.
Customers can grow. A change of node count is applied to the existing pool in place, and a change of node plan replaces the pool with new nodes at the new size. Customers do it themselves through Blesta's Upgrade/Downgrade, once you allow it on the package.
Pricing with the cost in view. The Products page shows what DigitalOcean charges each month for every node plan, read live and shown in dollars and in your default currency. Set a margin and each choice shows a suggested price and your margin per sale. The margin is optional and changes nothing until you use it.
Nothing left billing. Cancelling a service destroys the cluster together with the load balancers and block-storage volumes its workloads created, and a background sweep confirms the deletion finished. No create, retry or double request can leave a second cluster billing unseen.



Kubeconfig download is a switch on the package. Turn it off and the customer cannot download it. Pages follow the Blesta client template and every string can be translated or reworded. The customer's panel does not name the provider in its own words; the cluster's endpoint is DigitalOcean's hostname, as kubectl needs it.
PD DigitalOcean Kubernetes is one paid module with everything included. There are no add-on tiers and no per-cluster fees or cut from us: DigitalOcean bills you directly and you set your own price. It installs into PD Modules in one click and updates itself.
If your subscription ever lapses, your customers are not cut off. Running clusters are never stopped, deleted or changed. Once a licence has expired, new clusters are no longer provisioned while existing ones keep being managed, and customers can still download their kubeconfig. Only if it is later suspended does customer management pause, behind a neutral message. Teardown keeps running throughout.
They download their kubeconfig from the client area in one click and use it with kubectl. No access to your DigitalOcean account is needed.
Yes — through Blesta Upgrade/Downgrade, which resizes or grows the worker node pool.
No — a managed control plane can't be paused, so suspension is a management lock and the cluster keeps running. Terminate to stop billing.
The cluster is destroyed together with the load balancers and volumes DigitalOcean provisioned for it — zero orphans left billing on your account.
Yes. You resell on your own DigitalOcean account, at your own margin. Your API token is stored encrypted on your Blesta server 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 resource. Your customers keep serving throughout.
Your customers' data stays in your Blesta. To confirm your licence, the platform sends us four things and nothing else: your licence key, the domain, your server's own IP address and the directory it is installed in — the four values recorded against your licence in your client area. Alongside that we see which module and version you run and whether its licence is healthy, so we can ship compatible updates. We never receive your clients' personal data, your credentials, or the contents of your Blesta. Crash reports are off unless you turn them on, and a diagnostic report is only ever sent when you send one, after showing you a preview you can edit.
Blesta 6.0 or later, on PHP 8.1 or later. It installs alongside whatever else you run — it adds its own tables and templates rather than modifying Blesta files, so it does not collide with other vendors' modules or with a customised template. Uninstalling removes its own tables and settings and leaves no orphans behind.
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.