PD DigitalOcean MongoDB for WHMCS

PD DigitalOcean MongoDB lets a hosting company sell DigitalOcean managed MongoDB as its own document-database product. Your customer orders in your WHMCS cart, a dedicated MongoDB cluster is built on your DigitalOcean account, and your customer manages it from your client area under your brand, with no DigitalOcean login. You set the price and keep the margin over what DigitalOcean bills you.

MongoDB is the document store behind a great many Node.js applications, content platforms and mobile back ends. It is for hosts whose customers are developers choosing a database by data model, who want MongoDB managed rather than installed and patched on a server of their own.

Why hosts choose PD DigitalOcean MongoDB

A replica set when the customer wants one. High availability provisions a three-node replica set, offered as a checkout option you price yourself. The customer's page says how many standby nodes they have, so the redundancy they pay for is visible.

A connection string that is ready to paste. The customer's page shows the mongosh command with a full connection string, so developers can connect in a minute.

A dedicated cluster per customer. Each order builds its own MongoDB cluster in the region, plan and version the customer chose. Nothing is shared with another tenant.

Access control without tickets. Customers add and remove the IPv4 addresses and ranges allowed to connect, and changes apply within a minute. Until they add one, the page tells them the database accepts connections from any address.

Versions that follow DigitalOcean. The versions offered are read live from DigitalOcean, chosen at checkout or fixed per product.

Nothing left billing. Cancelling deletes the cluster at DigitalOcean and confirms it is gone.

How it works

1. Connect your DigitalOcean account. Add your DigitalOcean API token once on a WHMCS server record, using a token with Full Access, then press Test Connection.
2. Create your product. Create a product with the module and pick MongoDB as the Engine, then set a default region, plan and name prefix. Switch on automatic setup so a paid order provisions by itself.
3. Generate the checkout options. Open the module's Products page and press Generate. It builds the product's Region, Plan, High availability and Engine version options from DigitalOcean's live catalogue, all priced at zero for you to set.
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. WHMCS keeps billing as usual, and the customer copies the connect command and sets their own trusted sources.

What you get in WHMCS

Selling and pricing

• Checkout options for MongoDB generated from DigitalOcean's live catalogue: Region, Plan, High availability and Engine version
• Plans quoted as vCPU and RAM with storage included
• Versions read live from DigitalOcean; a blank version means DigitalOcean's default
• High availability as a priced checkout option, giving a three-node replica set
• Generated choices start at zero in every currency and you price each one under System Settings → Products/Services → Configurable Options; a sync never changes a price you have set
• Choose which choices customers see at checkout; anything hidden uses your product's default and keeps its price
• Clusters are named with your own prefix and the service number

Provisioning you can trust

• A paid order creates a dedicated MongoDB cluster on your own DigitalOcean account, with no step by you
• High availability provisions a three-node replica set
• 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 WHMCS's own upgrade 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

MongoDB, specifically

• The connection details show host, port, database, username and password, with a mongosh command built on a mongodb+srv connection string and TLS switched on
• Every cluster enforces TLS in transit, and the connect command already uses it
• There is no Backups page for MongoDB: the module lists backups only for engines where DigitalOcean provides a list
• The activity history records password regenerations and trusted-source changes alongside provisioning

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

The client area has Overview, Trusted Sources, Backups (where the engine lists them) and Activity under a Manage Database menu.

• Connection details in one window: host, port, username and password (masked until Show, with Copy beside each), plus a ready-to-use mongosh command with a TLS connection string
• 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
• Cluster layout in plain words: how many standby nodes a highly available database has

The firewall, connection details and backups pages are each a switch on the product: turn one off and it is hidden and refused. The client area renders natively on WHMCS's Six, Twenty-One and Nexus themes, 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 MongoDB is one paid module with everything included: provisioning, replica-set high availability, 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 WHMCS 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.

Requirements

• WHMCS 9 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
• WHMCS's automation cron running, which finalises new clusters and confirms cancellations
• PD Modules 0.2.322 or later, the free control panel every PD module installs into