hTech IDrive e2 Object Storage

Sell S3-compatible object storage under your own brand, as a standalone WHMCS product. Your customer orders a storage plan, and the module creates their storage account, their access keys and their first bucket, then renders the whole product inside your client area — on your domain, without your customer ever seeing the storage vendor's name.

Because the storage vendor has no single sign-on, there is nowhere to hand a customer off to. If your billing system cannot show them their buckets, their objects, their keys and their usage, then nothing can, and every request becomes a ticket. That is the gap this module fills.

What your customer gets when their order provisions

• A storage sub-account of their own, in a region they chose on the order form.
• An S3 endpoint on your white-label domain, in the form s3.<region>.<your-domain>.
• Their own access keys — created, listed and revoked from your client area, with the secret shown once.
• Buckets and objects: create, browse, upload, download and delete, with an object browser that paginates and a per-bucket protection setting.
• Usage, written back into WHMCS so it appears on the service the way any other metered product does.

What you get

• Provisioning on order, with the regions you allow and the tiers you name.
• Suspend, unsuspend and terminate wired to the real storage account, so a service that stops being paid for stops being usable.
• A retention window you set — terminated data is removed after it elapses, not the moment an invoice lapses.
• A nightly reconciler that re-checks what the module believes against what the vendor reports and shows you every difference. It reads; it never writes.
• An overage sweep that can warn a customer who is over their allowance, or ask the vendor to enforce the account's quota. It ships switched off and does nothing at all until you choose.
• An admin resync for a single service, for when you want one answer now rather than at 3am.
• Multi-brand from one install: storage settings are install-wide, but credentials and the white-label domain are per server entry, so one WHMCS install can sell storage under several brands at once.

Your reseller credential is held encrypted by WHMCS in the server entry's password field and is never written anywhere in plaintext. The module refuses to read a credential-shaped value out of the plaintext access-hash field, and says so by name.

Requirements

• WHMCS 8.13.0 or newer.
• PHP 8.1, 8.2, 8.3 or 8.4. PHP 7.4 and 8.0 cannot run this module at all — the source does not parse on either, so this is a syntax fact rather than a support policy.
• ionCube Loader 14.0 or newer. The module is ionCube-encoded, as one bundle carrying three encoder slots, measured running on 8.1, 8.2, 8.3 and 8.4 under loader 14.4. If your host runs the loader WHMCS itself requires, it runs this.
• Your own reseller account with the storage vendor. This module is the front end; the storage is yours to resell.
• Outbound HTTPS from your WHMCS server to the vendor's reseller API and to your own white-label endpoints.
• DNS you control for the white-label endpoint hostnames.

What this module does not do

Every line here is a measurement, and each one is here because you would otherwise find it out after paying.

• It does not sell storage as an extra attached to a service the customer already has. Storage is a standalone product in this version, and the module refuses an order of the attached shape by name, before a single request leaves your server. The reason is the billing platform's: an addon record has no configurable-option columns to hold a region or a quota, and a missing quota resolves to zero — which means unlimited at this vendor. A silent, expensive, uncorrectable failure is worse than a refusal, so it refuses.
• It does not upgrade a customer's plan when they go over. The overage policy offers exactly two responses and they are the two that work: warn and soft-block. A third, auto-upgrade, exists in the code and is not offered, because it cannot act: it has no source of a target size, since a tier list carries names and labels and no quota figure. You will not find it in the dropdown. It is fenced rather than deleted — one entry re-enables it the day there is a number for it to read — because a control you can pick that silently does nothing is worse than one that is absent.
• It does not claim to know what soft-block does at the vendor. The vendor documents that a quota enforcement can take up to 24 hours to take effect. That is their statement and not a behaviour we have observed on a live account. Test it on your own account before you sell against it.
• It does nothing about overages until you say so. The policy ships blank, and blank is a named refusal: the nightly pass examines every active account, declines by name for each one, records that it ran, and changes nothing anywhere.
• It never updates itself. There is no scheduled task, no queue, no background job and no setting — not one defaulted off — that can install anything. An update happens when a signed-in administrator opens the update page, presses Update and confirms it. You may decline updates indefinitely and the module goes on working.
• It adds no crontab line and asks you to add none. The three scheduled passes hang off WHMCS's own cron hook.
• It sends no email, to you or to your customer. What it wants to tell you goes to the WHMCS activity log and to the service record.
• It does not gate your customers on our licence server. Suspend, unsuspend, terminate, usage collection, the client area and all three scheduled passes keep working on any verdict, with our licence server up or down. If we have an outage, your suspensions still work, your paying customers still reach their data, and your terminations still stop the vendor's bills.
• It does not set your prices, your tiers or your allowances. No tier name and no number ships with the module. What you call your tiers and what you charge is yours, and the module refuses to sync a product until you have stated them.

Pricing

This module is licensed on a recurring subscription, per installation, in US dollars: 9.45 per month, 26.95 per quarter, 50.95 per six months or 89.95 per year, with no setup fee on any of those terms. One licence covers one WHMCS installation, keyed to the domain that installation runs on — the apex and its www. form count as one domain, not two.

Your licence includes updates for as long as it is in force, and an installation that is never updated keeps working — the software does not expire, does not phone home to stay running and does not disable itself because a licence has lapsed. What lapses is your right to new versions and to support, not your installation.

Frequently asked

Does it work on WHMCS 8? Yes — WHMCS 8.13.0 and newer, on PHP 8.1 or 8.2 as well as 8.3 and 8.4. The same artifact runs on all four; there is no separate build to choose.

Do my customers need their own account with the storage vendor? No. They order from you, they pay you, and they never see the vendor. You need one reseller account with the vendor; every customer account is created underneath it by this module.

What happens if your licence server is down? Nothing stops. Suspend, unsuspend, terminate, usage collection, the client area and all three scheduled passes are permanently ungated on any verdict. A licence problem is our problem and never your customers'.

Are there automatic updates? No, and there is no setting that turns one on. A signed-in administrator presses Update and confirms; nothing else can start one. An update replaces this module's own files and never touches your customers' data.

Can I sell under more than one brand? Yes. Credentials and the white-label domain live on the server entry, so a second brand is a second server entry on the same install.

Do I need to run a separate cron? No. The scheduled passes attach to WHMCS's own cron.