Resell Amazon EC2 compute as your own cloud servers — provisioned, billed and managed in WHMCS
Resell Amazon Lightsail as your own VPS — provisioned, billed and managed in WHMCS
★★★★★5.0 · our rating, not customer reviewsMade and supported by Projektif Digital Ltd. Runs inside PD Modules, the panel every module installs into.
PD Lightsail lets a hosting company sell Amazon Lightsail cloud servers as its own VPS product. Your customer orders in your WHMCS cart, the server is built in your AWS account within minutes, and your customer manages it from your client area: a control panel that carries your brand and never mentions AWS. You set the price, AWS bills you the cost, and the difference is your margin.
It is built for hosts who want to offer cloud servers without building a control panel, without handing out AWS access, and without a support ticket every time a customer needs a reboot.
Sell cloud servers under your own brand. Your customers see your company, your prices and your client area. Amazon is never named on their pages, and they never need an AWS login.
Every order sets itself up. The server is created the moment WHMCS sets the order up, with the region, plan and operating system the customer picked at checkout. Suspend, unsuspend and terminate follow your normal WHMCS billing, so a missed payment stops the server and a payment starts it again.
Customers help themselves. Power controls, connection details, snapshots, a firewall, static IPs, SSH keys, usage graphs and an optional in-browser terminal are all on the customer's own service page. That is most of the tickets a VPS product normally generates.
Products that stay current. Plans and operating system images are read live from your AWS account. A daily check tells you when AWS retires something your cart still offers, and one click of Sync hides it from new orders without touching existing customers or your prices.
Pricing with the cost in view. Price Analysis shows the live AWS monthly cost of every Lightsail plan next to a suggested price at the margin you set, so you start from real numbers.
Nothing left billing. Terminating a service removes the server, its static IP, its extra disk, its snapshots and its key pair, then confirms at AWS that everything is really gone. No forgotten resources on your AWS bill.


ssh command; on Windows, the RDP details instead


Every one of these is a switch on the product. Turn one off and it disappears from the customer's page, and the server refuses it too. The pages render natively on WHMCS's Six, Twenty-One and Nexus themes and are fully translatable, with wording overrides that survive updates.
PD Lightsail is one paid module with everything included: provisioning, power, snapshots, firewall, static IPs, metrics, upgrades and the browser console. There are no add-on tiers to compare. It installs into PD Modules in one click, updates itself, and uninstalls cleanly without modifying any WHMCS files.
If your subscription ever lapses, your customers are not cut off. You get a 14-day grace period with everything working, then admin management locks while customers keep their servers, and only after that do customer features pause, behind a neutral "contact support" message that never mentions licensing. The servers themselves keep running in your AWS account throughout.
Yes. You connect your AWS credentials once, and every client server is provisioned into your account — AWS bills you, you bill your client through WHMCS, and the difference is your margin.
Not silently. Plans and OS images are read live from AWS, and a daily check alerts you when one your generated options still offer has been retired; it stays orderable until you press Sync, which hides it without touching existing services.
Yes — an optional in-browser SSH console gives them a full terminal with no SSH client, keys or setup on their side. It stays off until you switch it on, and only you decide which servers offer it.
You stay in control: suspension and termination follow WHMCS's normal service lifecycle, and termination removes the server together with its snapshots, extra disk and static IP — so nothing is left billing. Copy off anything a client needs to keep before you terminate.
No. Upgrades are data-preserving, so a client keeps their instance and data when they move up to a larger bundle.
One paid product with every feature included — provisioning, power, snapshots, firewall, metrics and the console. No confusing add-ons.
Nothing of yours is touched, and nothing is deleted. The module steps down in stages instead: a 14-day grace period where everything still works and you get a renewal reminder, then admin management locks while your customers carry on being served, and only after that do the customer-facing features stop — behind a neutral "temporarily unavailable, please contact support" message that never mentions licensing to your customer. Anything the module provisioned keeps running in your own account throughout, and your data and settings stay exactly where they are. Renewing restores everything immediately.
Your customers' data stays in your WHMCS. 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 WHMCS. The exception is the optional browser console: when you switch it on, each session hands our console relay the server's address, login user and SSH key, sealed so only the relay can open it and usable once, and the terminal's traffic passes through the relay while the session is open; nothing is stored there. 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.
WHMCS 9 or later, on PHP 8.2 or later. It installs alongside whatever else you run — it adds its own tables and templates rather than modifying WHMCS files, so it does not collide with other vendors' modules or with a customised theme. Uninstalling removes its own tables and settings. Terminate its services and let their cleanup finish first — uninstalling also removes the record of any cleanup still in progress.