How to sell DigitalOcean Droplets from WHMCS as your own VPS product

Bulent Kocaman — Sun, 15 Nov 2026 14:21:04 +0000

If you run a hosting business on WHMCS, selling cloud servers is an obvious next step. You don't need your own hardware for it: DigitalOcean already runs the servers, and your customers just want a VPS, a fair price and a control panel that works.

The hard part is everything in between. Someone has to create the server when an order is paid, give the customer a way to manage it, resize it on upgrade, power it off when an invoice goes unpaid, and remove every last piece when the service ends, so nothing keeps billing your DigitalOcean account. Doing that by hand doesn't scale past a handful of customers.

This post walks through how that flow works in WHMCS, and the decisions worth getting right whichever tool you use.

The flow you want

A customer orders a server in your WHMCS and picks a region, a plan and an operating system.
When the first payment arrives, WHMCS sets up the order and a Droplet is created on your DigitalOcean account.
The customer manages it from their client area, under your brand. They never need a DigitalOcean account.
Upgrades, suspensions and cancellations in WHMCS change the Droplet to match.

WHMCS bills your customers; DigitalOcean bills you. Your margin is the difference, and you set every price.

1. Connect DigitalOcean to WHMCS

Create a DigitalOcean API token with read and write access to Droplets (Full Access is simplest). A read-only token will pass a connection test and then fail on the first real order, which is a confusing way to find out.

In WHMCS the token belongs on a server record, stored encrypted. Your customers never see it.

2. Build checkout options from the live catalogue

The tempting shortcut is to hard-code a few plans in WHMCS configurable options. It works until DigitalOcean adds a region or retires a size, and then your order form quietly drifts out of date.

It's better to generate the options from DigitalOcean's live catalogue: region, server plan and operating system, plus the extras you want to sell, such as extra storage (Volumes), automated Backups and a dedicated reserved IP. Then price what you sell and hide the rest.

3. Give customers a real control panel

A VPS customer expects to manage their own server. At minimum that means power controls, connection details and a way to recover from mistakes:

power on, shut down, reboot and rename;
IP addresses, an SSH key generated for that server, and a ready-made SSH command;
a firewall they can edit themselves (DigitalOcean's Cloud Firewalls work well per server);
snapshots, restore and rebuild;
CPU and bandwidth graphs, and a history of what happened.

A browser console is worth offering too: a terminal in the client area means customers don't need an SSH client to fix a broken config at 2am.

4. Get the money details right

These are the parts that cost hosts money when they're overlooked:

A powered-off Droplet is still billed. Suspending an unpaid service by powering the server off protects your customer's data, but DigitalOcean keeps charging you. Terminate services that stay unpaid.
Snapshots are billed per GB while they exist. If customers can take snapshots, give them an allowance and sell extra slots, rather than letting storage grow unchecked.
Termination must clean up everything. Deleting the Droplet isn't enough. Its Volume, firewall, reserved IP and SSH keys should go too, and the clean-up should confirm with DigitalOcean that they're gone.

5. Mind the cron

Creating a server is quick, but the follow-up work (recording its IPs, attaching storage, creating its firewall, carrying out a customer's reboot) usually runs on a schedule. On the standard WHMCS cron that's typically every five minutes, so a customer's reboot can sit waiting. A dedicated one-minute cron makes the panel feel responsive.

The module we built for this

We make PD DigitalOcean Droplets, a WHMCS module that does all of the above: options generated from DigitalOcean's live catalogue, the customer control panel (including the browser console), resizing through WHMCS upgrades, and a clean-up that checks with DigitalOcean when a service ends. It runs inside the free PD Modules panel, which also offers that one-minute cron.

If you're setting this up, the module page has the details. Questions about selling DigitalOcean from WHMCS in general are welcome in the comments too.

PD Modules is made by Projektif Digital Ltd, the team behind PD Hosting.

DEV Community: Bulent Kocaman