PD Object Storage for WHMCS and Blesta

PD Object Storage is available for WHMCS (8.13 or later) and Blesta (6.0 or later). Each has its own page with the screenshots, requirements and price for that system. A module is added to the PD Modules licence of the installation it runs on, so a WHMCS installation and a Blesta installation each hold their own licence.

Four, all built in: Amazon S3, Cloudflare R2, MinIO, and DigitalOcean Spaces. You choose the backend per product, and you can run several backends side by side in the same WHMCS or Blesta — each product on its own server.

No. PD Object Storage is the single flagship covering all four backends. If you only ever sell one, the focused editions (PD AWS S3, PD Cloudflare R2, PD MinIO S3, PD DigitalOcean Spaces) offer the same engine for that one provider.

Yours. You connect your own account for each backend, and every customer bucket is provisioned into it. You pay the provider at cost, set your sell price in WHMCS or Blesta, and keep the difference.

Every order gets its own bucket and a credential scoped to that bucket only — an S3 access key, an R2 token, an IAM user, or a Spaces key depending on the backend. One customer's credential cannot reach another customer's data. Your master credentials never leave your WHMCS or Blesta server.

A daily task measures each service's real storage use and writes it into WHMCS's or Blesta's disk-usage fields, so native overage billing, quota warnings and the client-area usage graph all work automatically — on every backend.

Yes, honestly. The module only offers what each backend actually supports — for example Cloudflare R2 has no object versioning, so that option and control simply aren't shown for an R2 product. Regions and data-location choices adapt too (including Cloudflare R2's EU-only residency).