Why we built ClientFence, a free WHMCS alternative
Why the cPFence team turned FOSSBilling 0.8.8 into ClientFence: free, open-source billing for hosting businesses, with many features that work as in WHMCS.

A hosting business runs on its billing system: invoices, payments, orders, hosting accounts, domains and support tickets, all in one place. When billing goes wrong, it costs you money and clients.
For a long time the choice looked like this: pay for a licence for a closed system, or use a free one that is missing much of what a hosting business needs. We wanted a third option, so we built ClientFence.
The choice hosting businesses had
WHMCS has the features hosting businesses rely on, such as two-factor sign-in, quotes, configurable options and email-to-ticket. But it comes with a paid licence, monthly or yearly, priced by your number of active clients. Its code is encoded and needs ionCube to run, so you cannot read or change it. And it always sends data about your installation’s configuration back to its vendor, with a licence check every seven days.
FOSSBilling is free and open source under the Apache License 2.0. But version 0.8.8 had no two-factor sign-in, no quotes, no configurable options, no email-to-ticket, no prorated upgrades and no partial invoice payments. It had no import from another billing system and no Enhance integration in its core. For a hosting business moving from WHMCS, that was too much to give up.
What we set out to build
We started from FOSSBilling 0.8.8 and kept its open licence. Then we reworked it, through rounds of independent testing and code review, into a near-new platform rather than a simple fork. You can see how we tested it, and what we found, on the security page.
We had three goals.
Free and yours. ClientFence is released under the Apache License 2.0, with no licence fee. You run it on your own server, and the full source code is on GitHub. Our slogan says it best: 100% free. Self-hosted. Your infrastructure, your rules.
Works the way you expect. Many features work as they do in WHMCS: one renewal invoice for services due on the same day, add-ons for a service a client already has, WHMCS-style suspension and termination rules, and a choice of whether a client’s credit pays a staff order. Browse every feature to see the full list.
Easy to move to. Starting over is the hardest part of switching. ClientFence has a built-in import for WHMCS, Blesta, Upmind and ClientExec. It brings clients, services, domains, invoices, payments and tickets into a fresh install, with checks before it starts. It only reads the old system: nothing changes there, and nothing is emailed or charged. The WHMCS, Blesta and ClientExec imports keep ids, invoice numbers and client passwords. The WHMCS import guide walks you through it.
Built for Enhance hosts
We built ClientFence with Enhance hosts in mind. You connect your Enhance servers and sell their plans as products, and accounts are created, suspended, unsuspended and terminated automatically.
Each Enhance hosting account gets its own page in the client area. Clients look after their mailboxes, check their usage and DNS, and sign in to Enhance with one click, without leaving the portal. A daily status check shows staff any hosting service whose Enhance state differs from billing.
You do not need Enhance, though. ClientFence also has server managers for cPanel/WHM, Plesk, DirectAdmin, CWP and HestiaCP, and a Custom one.
Security from the team behind cPFence
The cPFence team builds hosting security, and we brought that work to the billing portal. ClientFence ships hardened: a strict script security policy, DKIM-verified senders and the security fixes found in independent testing, with passkeys, two-factor sign-in and fraud checks on new orders ready to turn on. Every optional security feature is off by default, so you turn on only what your business needs.
There is no telemetry. The only call home is a daily check of the release list on clientfence.com. It sends nothing about your site, and you can turn it off. Updates take one click: ClientFence saves a backup first, then installs the release, and puts things back if the release cannot be unpacked or its database update fails.
We already use ClientFence in production for our own business, Linkers Gate, and plan to use it for cPFence billing soon. Running it ourselves means we rely on the same software we offer you. Our testing has been limited to our own stack and servers, so please test it well on your own setup before you go live.
Try it on your own server
ClientFence is free, so there is no ticket support. Report bugs in GitHub Issues and ask questions on the ClientFence forum. We welcome developers and security researchers to review the source code, test their own installations and report potential vulnerabilities privately to our team.
Ready to see it for yourself? Download ClientFence, then follow the docs, from installing to moving from WHMCS.

