FluxBilling

WHMCS Hourly Billing: What WHMCS and Blesta Offer for Hourly VPS

WHMCS and Blesta have no hourly cycle in core. What their modules add, the problems hourly billing creates for VPS hosts, and how a prepaid hourly cycle works natively.

Mario MarinMario Marin9 min read

WHMCS hourly billing is not part of the core product. WHMCS 9.1 bills services one time or monthly, quarterly, semi-annually, annually, biennially or triennially, and its usage billing adds metered charges to the next renewal invoice. Hosts who sell VPS by the hour add a commercial module, and Blesta hosts face the same choice. A few platforms, FluxBilling among them, ship a prepaid hourly cycle built in.

How this was sourced. FluxBilling publishes this page and sells billing software with hourly billing built in, so it competes with both products. WHMCS facts come from docs.whmcs.com and the WHMCS Marketplace, Blesta facts from blesta.com and the Blesta Marketplace, and module details from each vendor's own page, all read on 16 November 2026. FluxBilling behaviour is taken from our hourly billing documentation and code.

How does WHMCS hourly billing work today?

It does not, in the sense a VPS host means. The WHMCS billing logic documentation lists seven billing cycles for services and addons: One Time, Monthly, Quarterly, Semi-Annually, Annually, Biennially and Triennially. There is no hourly cycle and no prepaid meter that draws a balance down by the hour.

What WHMCS does have is close, but aimed at shared hosting:

  • Usage billing. Products on the cPanel, DirectAdmin and Plesk modules can capture metrics such as bandwidth or addon domains, priced per unit, by volume or graduated. The charge is added to the next renewal invoice, and WHMCS recommends a monthly cycle so usage is billed often.
  • Overage billing. Disk and bandwidth above a package's soft limits, calculated on the last day of each month.
  • Time billing. Staff hours on client projects, added as billable items. It is for consulting work, not server uptime.

Module developers can report their own metrics, so a provisioning module can feed usage into WHMCS. Hourly VPS billing with a prepaid balance still needs an add-on.

Which WHMCS modules add hourly billing?

A WHMCS Marketplace search for "hourly" returned 32 listings, most of them commercial. Some resell one provider's cloud by the hour, such as Hetzner hourly VPS modules. The general-purpose option is ModulesGarden's Advanced Billing For WHMCS, which its listing describes as hourly billing for any WHMCS module, with credit billing, prepaid top-ups, a minimum credit threshold for creating and using services, low-credit emails and automatic suspension when a client runs out of credit.

At the time of writing (November 2026), ModulesGarden lists it at $35.95 a month, $299.95 a year, or $1,999.95 once for an owned, unencrypted copy with optional updates at $149.95 a year. Its page showed version 4.6.0 for WHMCS 9.0. That is on top of the WHMCS licence and whatever provisioning module creates the servers, such as a Proxmox module from the Marketplace.

What about Blesta hourly billing?

Blesta's billing features page lists recurring invoices by day, week, month or year, and account credits with low-balance alerts for prepaid clients. It lists no hourly cycle and no usage metering.

The Blesta Marketplace has a commercial Hourly Billing plugin by SystemFreaks, version 1.5.0 from 4 November 2026. Its listing describes a postpaid model: nothing is due at checkout, active hours are metered, and usage is billed in arrears on the monthly renewal invoice, capped at the package's monthly price. The default divisor is 672 hours. That is a sensible design for trusted customers, but the server runs for a month before anyone pays for it.

What problems do hosts hit with hourly billing?

  • Postpaid hours are credit risk. A customer who runs a server for 600 hours and never pays the renewal invoice has cost you a month of capacity. Prepaid credit removes that risk.
  • Throwaway sign-ups. Without a minimum balance, an hourly VPS costs an abuser cents. A minimum credit before ordering raises the price of a test account.
  • Long months. A rate derived from 720 hours (30 days) bills 744 hours in a 31-day month, about 3% over the monthly price. Either cap the month or say clearly that hourly can cost more.
  • Zero credit. Suspension needs a grace period, and termination deletes data. Both clocks belong in your terms.
  • Stopped is not deleted. A powered-off VM still holds disk, RAM reservation and IP addresses. Most hosts keep billing it, and customers need to be told.
  • Invoices for hours. One invoice per hour is unreadable and one per top-up says nothing about usage. A monthly statement with hours and rate per service is what accountants ask for.
  • Add-ons. Extra IPs, backups or a protection tier must meter at the same hourly logic as the server, or the monthly and hourly totals drift apart.

How does FluxBilling bill by the hour?

Hourly billing is native and runs from one switch under Settings, Billing, Automation. You tick the Hourly cycle on a product category, and every product in it gets an hourly price box. Leave the box blank and the rate is the monthly price divided by 720, kept to four decimal places. Hourly add-ons and location surcharges are worked out from their monthly amounts the same way, and an add-on can be offered on whole product categories.

  • Prepaid credit. The customer holds a credit balance. On an order of hourly services the first hour is taken at once, then a pass on every hour, on the hour (UTC) deducts each service's rate including tax. The balance never goes negative.
  • Minimum balance. Hourly Min Balance refuses an hourly order until the customer holds that much credit. No setup fee is charged on hourly orders.
  • Grace in hours. Suspension Grace and Termination Grace are both counted in hours. With 1 and 24, a VPS and its data are gone about 25 hours after the credit runs out, so set them deliberately.
  • Warnings and top-ups. Low-credit emails go out when the balance covers fewer hours than your threshold, at most once a day per service. Automatic top-up can charge a saved card, and a suspended service comes back when credit arrives.
  • Monthly cap. When switched on, a service never costs more in a calendar month than 720 hours of its own rate. The rest of the month is free.
  • Monthly summary. On the 1st, each customer gets one already-paid document listing every service with its hours and rate, for example "720 hours @ €0.0685/hr".

The limits, plainly. A powered-off VM keeps billing because its resources stay reserved, and only a game server can be set to stop billing while stopped. Hourly upgrades get no proration: the new rate starts with the next hour. Products in the Other category, which your team delivers by hand, cannot be sold hourly.

What does an hourly price look like in practice?

An example with round prices, before tax, on the 720-hour rule:

Example itemMonthly priceHourly rate31-day month, no cap (744 h)31-day month, capped (720 h)
Small VPS€4.00€0.0056€4.17€4.03
Extra IPv4 add-on€2.00€0.0028€2.08€2.02
Larger VPS€20.00€0.0278€20.68€20.02

The capped column lands a few cents above the monthly price because the cap is 720 hours of the rounded hourly rate, not the monthly figure itself. A ten-day test of the larger VPS costs 240 hours at €0.0278, or €6.67. As a live example, hosting providers on FluxBilling sell KVM VPS from €0.0056 an hour.

Which hourly billing option fits your business?

Side by side, at the time of writing (November 2026), from each vendor's own documentation or listing:

WHMCS coreWHMCS with Advanced BillingBlesta with Hourly BillingFluxBilling
Hourly cycleNoYes, for any moduleYes, per packageYes, per product category
When the customer paysNot applicablePrepaid credit or invoices every X daysIn arrears, on the monthly renewal invoicePrepaid credit, deducted every hour
Minimum balance to orderNot applicableConfigurable thresholdNothing due at checkoutHourly Min Balance setting
Monthly capNot applicableNot listedPackage monthly priceOptional, 720 hours of the service's own rate
Out of creditNot applicableAutomatic suspensionBlesta's usual handling of an unpaid invoiceSuspension after a grace in hours, termination after a second grace
Extra costNot applicableFrom $35.95 a monthCommercial, priced at orderIncluded on every plan
  • Stay on WHMCS with a module if your catalogue, registrars and team are built around WHMCS and hourly is a small part of sales. Budget for the module, its renewals and its compatibility after each WHMCS upgrade.
  • Use Blesta with a plugin if your hourly customers are known businesses and billing in arrears suits them.
  • Use a platform with hourly built in if hourly VPS or game servers are a main product and you want prepaid credit, caps and grace clocks in the core. FluxBilling plans run from €4.95 a month for 10 clients to €25 for unlimited clients, see pricing.

Questions people ask

Can WHMCS bill a VPS by the hour?

Not in the core product, which has no hourly billing cycle. Hosts add a commercial module, such as ModulesGarden's Advanced Billing For WHMCS, or a provider-specific hourly module from the Marketplace.

Does Blesta support hourly billing?

Not natively. Its shortest recurring term is a day. A commercial Marketplace plugin meters active hours and bills them in arrears on the monthly invoice.

Should the hourly rate use 720 or 730 hours?

720 hours (30 days) gives a clean rate and a predictable cap. 730 is the average month and undercharges short months. Whatever you choose, publish it and cap the month if you advertise hourly as never costing more than monthly.

Prepaid or postpaid hourly billing?

Prepaid suits anonymous and new customers because nothing runs unpaid. Postpaid suits trusted accounts that prefer one invoice. Many hosts offer prepaid to everyone and postpaid by agreement.

Where to go next

If hourly billing is why you are leaving, see how FluxBilling compares as a WHMCS alternative or a Blesta alternative. Blesta hosts can follow our Blesta migration guide, and if you are still weighing free software, read FOSSBilling vs WHMCS.

WHMCS, Blesta, ModulesGarden, SystemFreaks, Hetzner, cPanel, DirectAdmin, Plesk and Proxmox are trademarks of their respective owners. FluxBilling is not affiliated with or endorsed by any of them. Third-party prices and versions are as published on 16 November 2026 and may change.

Tagged
whmcs hourly billingblesta hourly billinghourly billing for vpswhmcs usage billingprepaid hourly billinghourly vps billing softwareadvanced billing for whmcs
Written by
Mario Marin
Mario Marin
View all posts →