WHMCS is billing, client management and automation software for web hosting companies and other businesses that sell recurring online services. It takes the order, sends the invoice, collects the payment through a payment gateway, creates the hosting account or registers the domain on a connected system, and gives customers a client area with support tickets. WHMCS does not host websites itself.
What is WHMCS in plain words?
WHMCS is the back office of a hosting business, delivered as one web application. The WHMCS website calls it a hosting automation platform for billing and client management. It has two sides:
- The admin area is for you and your staff. You see clients, orders, invoices, payments, support tickets and reports there.
- The client area is for your customers. They order, pay invoices, manage their services and domains, and ask for help there.
You can run it in two ways. Self-hosted means you install WHMCS on your own hosting account or server. WHMCS Cloud is the fully managed version, where WHMCS hosts and updates it for you. WHMCS and cPanel both carry the WebPros name today, but they are separate products with separate licenses.
What does WHMCS do?
WHMCS automates the repeating work between a customer clicking Order and the service being switched on, billed and supported. A scheduled task on the server, called the cron job, does the daily part without anyone logging in.
| Job | What WHMCS does | What it needs from you |
|---|---|---|
| Orders | Shows your products in an order form and takes the order. The documentation says products can be hosting accounts, domains, software licenses, design services, support plans "or even physical goods". | Products and prices set up. |
| Invoices and payments | Creates invoices before the due date, sends reminders and overdue notices, applies taxes and records the payment. | At least one payment gateway, such as PayPal or Stripe. That is the company that processes the card or bank payment. |
| Provisioning | Creates the hosting account automatically, suspends it when an invoice is overdue, restores it when the customer pays and terminates it when the service ends. | A server connected through a module. WHMCS includes modules for cPanel, Plesk and DirectAdmin, among others. |
| Domains | Sells registrations, transfers and renewals, and passes each one to a registrar. | An account with a supported domain registrar. |
| Support tickets | Runs a ticket desk with departments, email importing, a knowledgebase and downloads. | At least one support department. |
| Reports | Shows sales, income and billing activity. | Nothing extra. |
Provisioning is the word hosting people use for creating the account automatically. A module is the connector between WHMCS and another system, such as a server, a registrar or a gateway. Without the right module, that step stays manual.
WHMCS vs cPanel and WHM: what is the difference?
cPanel and WHM run the server, and WHMCS runs the business that sells space on it. They do different jobs, and WHMCS is built to connect to cPanel and WHM, not to replace them. WHM stands for WebHost Manager.
| Question | WHMCS | WHM | cPanel |
|---|---|---|---|
| What is it? | Billing, client management and automation | The server administration side of cPanel & WHM | The control panel for one hosting account |
| Who logs in? | You and your staff in the admin area, customers in the client area | The server's root user and resellers | The owner of that hosting account |
| What does it manage? | Clients, orders, invoices, payments, tickets and the rules for suspending | Hosting accounts, packages, DNS zones, backups and services on the server | Email accounts, files, databases and domains for one account |
| Does it invoice your customers? | Yes | No | No |
| Where does it run? | On a Linux hosting account or server with Apache, PHP and MySQL, or on WHMCS Cloud | On each hosting server | On each hosting server |
| How is it licensed? | Monthly, by number of active clients | Needs a valid cPanel & WHM license | Covered by that same license |
Here is how they work together. A customer orders a hosting plan in WHMCS and pays. WHMCS tells WHM to create the cPanel account, using a package you defined. If a later invoice goes unpaid, WHMCS tells WHM to suspend the account, and to restore it once the balance is paid. WHMCS's cPanel page also lists single sign-on from WHMCS into cPanel, disk and bandwidth usage reporting, and an importer for accounts that already exist on the server.
The descriptions of WHM and cPanel above come from the cPanel & WHM documentation. If you sell from Plesk or DirectAdmin servers instead, the split is the same: the panel runs the server, WHMCS runs the billing.
Who needs WHMCS, and who does not?
You need WHMCS when you sell recurring services to enough customers that invoicing, chasing payments and switching services on and off by hand has become a job of its own.
- Hosting companies and resellers. This is who it was built for. My WHMCS reseller hosting guide covers the smallest version: one reseller account connected to WHMCS.
- Agencies with maintenance plans. WHMCS's site names agencies that want client services, invoicing and subscriptions in one place.
- Domain resellers and software sellers. Domains are built in, and software licensing is a separate addon.
You probably do not need it in these cases:
- You host a few client sites and send a few invoices a year. Your accounting tool already does that.
- You sell one-off products, not renewals. An online shop fits better.
- You only want a help desk, or only a website builder. WHMCS is neither on its own.
- Nobody on your side will look after it. A billing system that nobody watches can send wrong invoices to real people.
If you are still deciding whether to sell hosting at all, my page on how to start a hosting business puts WHMCS next to the other launch decisions.
What does WHMCS not do?
WHMCS does not host anything, move money on its own or look after its own server. Six limits are worth knowing before you buy.
- It is not a hosting server. Websites and email live on a server run by a control panel. WHMCS only sends that panel instructions.
- It is not a payment processor. The documentation says you must set up at least one payment gateway before you can sell. The gateway holds your merchant account and charges its own fees.
- It is not a domain registrar. You need an account with a registrar that WHMCS supports.
- It is not your marketing website. It gives you a client area and order forms. Your main site is separate and links into them.
- Self-hosted WHMCS does not maintain itself. The system requirements list a Linux server with Apache, PHP, MySQL and the ionCube Loader. The cron job, updates and backups are yours. WHMCS Cloud takes that over, but its pricing page offers a curated module set there, while self-hosted can install any Marketplace or custom module.
- It is not open code you can edit freely. WHMCS needs the ionCube Loader to run, and its documentation recommends the hook system for most customizations. Changes go into hooks, modules and templates, or through the API.
The last point is where I earn my living, so weigh it accordingly: when the built-in modules do not cover a local payment gateway or an unusual product, someone has to write a module.
How does WHMCS licensing work?
WHMCS is licensed by the month, and the plan you need depends on your number of active clients. The WHMCS pricing page defines an active client as "any client with at least one active product, service, addon or domain".
- Self-hosted plans step up by active client limit. Every one lets you download WHMCS and install it in your own hosting environment.
- Fully managed plans include a number of active clients and charge for each client above it.
- When you pass your limit, WHMCS says it notifies you and upgrades the plan automatically unless you opt out.
- Before you commit, note that the page shows a 30-day money-back offer.
I have left the prices out here because they change. My WHMCS pricing guide lists every plan with the date I read it, and the costs beyond the license.
How do you get started with WHMCS?
Choose self-hosted or WHMCS Cloud first, then set up the pieces in the order WHMCS's own getting started guide uses: a server, products, a domain registrar, a payment gateway, a support department and the automation settings. A Getting Started Wizard walks you through the basics the first time you log in.
Place a test order before a real customer does. Pay it, check that the account appears on the server, and let one invoice go overdue on purpose to see the suspension happen. My post on how to set up WHMCS gives the full order of work. If you would rather hand it over, my WHMCS installation and setup page lists what I deliver, WHMCS development services covers the rest, and the scoping call is free and takes about 30 minutes.
Last reviewed 10 October 2026. Disclosure: I am a freelance WHMCS developer. I sell WHMCS installation, custom modules and maintenance, so I gain when a business chooses WHMCS. I am CTO at ElySpace, a developer at Marmaids LLC, and founder of WHMCSPilot and MagizAI. Feature and licensing statements were checked against whmcs.com and the WHMCS 9.0 documentation on the review date.