adminbolt Licenses For WHMCS: A Walkthrough of the ModulesGarden Module

ModulesGarden released the adminbolt Licenses For WHMCS provisioning module on May 13, 2026. It is a free WHMCS module that handles the full lifecycle of an adminbolt license from inside WHMCS itself: order, create, activate, suspend, change, terminate, and the routine sync work in between. For anyone running adminbolt as part of a reseller offering on WHMCS, this is the bridge that turns license sales from a manual ticket into an order-driven workflow.

This article walks through what the module does, what it looks like in the WHMCS admin area and the client area, what the technical requirements are, and where it fits in a reseller's stack. The product page is at modulesgarden.com/products/whmcs/adminbolt-licenses and it is distributed as a free module with lifetime access and free updates.

What the module covers

adminbolt Licenses For WHMCS is a WHMCS provisioning module that connects WHMCS to the adminbolt Reseller API. The moment a client places an order in WHMCS, the module reaches the reseller API, creates the license, activates it, attaches the relevant metadata (domain, IP, installation directory), and returns the license key to both the admin panel and the client area. No manual provisioning step, no copy-paste between two control panels.

The module is built and maintained by ModulesGarden, the WHMCS module vendor behind Password Manager For WHMCS, Hosting Renewals For WHMCS, DNS Manager For WHMCS, and dozens of other widely deployed WHMCS extensions. The free pricing is unusual for ModulesGarden, the rest of their catalog runs at $119 to $400 per year per license. Free here means the module itself costs $0; the licenses you sell through it still cost whatever you list them at.

In the WHMCS admin area

The admin side gives a hosting operator full lifecycle control without leaving WHMCS. Each adminbolt license appears as a WHMCS service with the standard service controls plus a panel of module-specific actions:

• Create License. Triggered automatically by a paid WHMCS order; also available manually when an admin needs to provision a license outside the normal order flow.
• Renew License. Aligns with the WHMCS billing cycle, the module supports flexible mapping between WHMCS cycles and adminbolt renewal terms.
• Suspend and Unsuspend License. Used when a payment fails or when an admin needs to pause a license temporarily.
• Terminate License. Final stop. Removes the license from the adminbolt reseller account.
• Change Package. Move a license to a different adminbolt product (for example, VPS to Bare Metal) without recreating it.
• Synchronize License Data With adminbolt. Forces a refresh between the WHMCS service record and the adminbolt reseller API. Useful after manual changes on either side.

Below the action panel, the module surfaces the license metadata that operators need most often:

• License Key
• License Status
• Valid Domains
• Valid IP Addresses
• Installation Directory

All of this in the same service detail view a WHMCS admin already opens for any other hosted service.

In the client area

The client side is smaller by design. A customer who bought an adminbolt license through your WHMCS portal sees their license details from inside the standard WHMCS client area. From there they can:

• View license details and status.
• See assigned domains, IP addresses, and installation directory.
• Reissue the license (useful after migrating servers).
• Request service cancellation through the normal WHMCS cancellation flow.

There is no separate login, no separate portal. From the customer's perspective the adminbolt license is just another service in their WHMCS account, alongside the hosting plan, the domain, and the SSL.

Why the design choices matter

A few details in this module are worth pulling out because they affect operations more than feature lists usually suggest.

Flexible billing cycle mapping. WHMCS supports a wide range of billing cycles (monthly, quarterly, semi-annual, annual, biennial, triennial). adminbolt's reseller API has its own renewal semantics. The module maps between the two rather than forcing the operator to align them, which means existing WHMCS pricing tables for adminbolt resold licenses do not have to be rebuilt to match the upstream model.

Reissue from the client area. Allowing a customer to reissue a license themselves (typically when changing the server the license is bound to) removes the most common license-related support ticket. Without this control, every server migration becomes a support thread.

Synchronize action on demand. Reseller APIs and billing systems drift apart over time, an admin changes something through the panel, a license expires in the upstream system without WHMCS noticing, a refund is processed manually. The explicit sync action lets the operator force WHMCS back into alignment with the adminbolt reseller account when needed, rather than waiting for a cron-driven sync.

Free distribution. ModulesGarden sells the rest of their WHMCS catalog as annual licenses. Distributing this module for free lowers the barrier for adminbolt resellers, which directly correlates with how many providers adopt adminbolt as a resold product through WHMCS.

Technical requirements

The module's general info section spells out the supported environment:

• adminbolt Reseller API access required. You will need to be onboarded as an adminbolt reseller and have API credentials issued.
• WHMCS V8.13 through V9.x supported.
• PHP 8.2 to 8.3 supported.
• ionCube Loader V14 or later required. The module ships as ionCube-encoded PHP.
• Multi-language support built in.
• WHMCS themes: Twenty-One, Nexus, and Lagom WHMCS Client Theme are all supported out of the box.

If you are running WHMCS at the current version with a modern PHP and any of the three mainstream themes, you are in scope. The only setup work is getting reseller API credentials and connecting them in the module configuration.

Where this sits in a reseller stack

For a hosting provider who already resells adminbolt licenses to other operators, agencies, or self-hosted customers, the module replaces the manual loop that usually accompanies license sales:

• Without the module: customer orders in WHMCS, payment clears, admin gets a notification, admin logs into the adminbolt reseller portal, creates a license manually, copies the key back to WHMCS, emails the customer.
• With the module: customer orders in WHMCS, payment clears, license is created automatically, key is attached to the WHMCS service, customer sees it in the client area, customer goes live without admin involvement.

The same logic applies to renewals, suspensions on failed payment, and terminations on cancellation. Each of these moves from "admin task with delay" to "automatic, with audit trail in WHMCS."

For providers not yet reselling adminbolt, the module lowers the activation effort. The infrastructure to bill, suspend, and account for adminbolt licenses already exists on the WHMCS side, and the module fills in the missing automation.

Pricing and access

The free distribution covers the module itself only. The adminbolt licenses you provision and resell through the module are billed at whatever you list them at in your WHMCS product catalog, with margin between your retail price and your reseller cost.

Getting started

The high-level setup is the standard WHMCS provisioning module flow:

1. Order the module on the ModulesGarden product page (free).
2. Upload the module to your WHMCS modules/servers/ directory.
3. Add a new server in WHMCS pointing to the adminbolt reseller API endpoint, with your reseller API credentials.
4. Create a WHMCS product, set the module to adminbolt Licenses, map the package to the adminbolt product type you intend to sell (VPS, Bare Metal, Standalone).
5. Configure the product price and billing cycles.
6. Publish the product to your storefront.

ModulesGarden ships full documentation under the Documentation link on the product page; that is the canonical install reference.

Where to learn more

• Module product page on ModulesGarden
• adminbolt for resellers and partners
• adminbolt control panel features
• For pre-sales questions on the module itself: ModulesGarden support center linked from the product page.

If you are running WHMCS and considering reselling adminbolt licenses, this module is the missing automation layer between the billing system you already have and the control panel you want to sell. The fact that it costs nothing and is maintained by a long-running WHMCS vendor makes the trial cost effectively zero.

FAQ

Is the module really free? Yes. The module itself is distributed at $0.00 with lifetime access and free updates. You only pay for the adminbolt licenses you provision through it, and you set your own resale price for those.

Do I need to be an adminbolt reseller to use the module? Yes. The module connects to the adminbolt Reseller API and requires reseller credentials. Contact adminbolt through [email protected] if you are not yet on the reseller program.

Which WHMCS versions does it support? WHMCS V8.13 through V9.x, with PHP 8.2 or 8.3 and ionCube Loader V14 or later.

Which WHMCS themes work with the client area? Twenty-One, Nexus, and Lagom WHMCS Client Theme are all supported. Custom themes may work if they follow standard WHMCS template conventions, but the three named themes are the tested set.

Can I change a customer from one adminbolt plan to another without losing their license? Yes. The Change Package action in the admin panel handles plan changes (for example, VPS to Bare Metal) without recreating the license.

What happens to the license if a customer cancels in WHMCS? The module's Terminate License action runs through the normal WHMCS cancellation flow. The license is removed from the adminbolt reseller account and the WHMCS service is closed.

Can clients reissue licenses themselves? Yes. The client area exposes a Reissue License action, which is the standard flow when a customer migrates to a new server and needs to rebind the license.

Is there a multi-language version? Yes. The module ships with multi-language support, so you can localize the customer-facing strings to match your storefront.