FOSSBilling

Open-source billing and client management for web hosts, honestly reviewed. Still in beta — that matters.

TL;DR

• What it is: Free, open-source (Apache-2.0) billing and client management platform designed for web hosting businesses — think WHMCS, but self-hosted and $0/month [1][5].
• Who it’s for: Small-to-mid web hosting resellers, VPS providers, and digital service businesses that need automated invoicing, hosting provisioning, and domain management without a recurring SaaS bill [3][5].
• Cost savings: WHMCS runs on a paid monthly subscription that scales with client count. FOSSBilling’s software costs nothing; you pay only for a VPS to run it on [5].
• Key strength: Full hosting automation stack in one tool — billing, provisioning (cPanel, Plesk, DirectAdmin, HestiaCP), domain management, and a built-in support desk [website].
• Key weakness: Explicitly labeled beta in the README. The codebase is a modernized fork of the abandoned BoxBilling project, and rough edges remain — including limited third-party reviews and unresolved open issues [README][1].

---

What is FOSSBilling

FOSSBilling is a self-hosted billing and client management system written in PHP. It automates the operational grind of running a web hosting business: generating invoices, processing recurring payments, provisioning accounts on control panels, managing domain registrations, and handling support tickets — all from one admin panel [README][website].

The project is a direct successor to BoxBilling, a popular open-source billing tool that was abandoned by its original maintainer. The FOSSBilling team forked it, relicensed it under Apache 2.0, and has been modernizing the codebase since [1]. As of this review, the GitHub repository sits at 1,506 stars with active releases shipping through 2025 — the most recent being 0.7.2 in September 2025 [1][2].

The honest pitch is narrower than the website’s “free and open source hosting automation” headline suggests. This is not a general-purpose business billing tool. It is purpose-built for hosting providers who need to provision cPanel accounts, automate domain renewals through Namecheap and similar registrars, and handle recurring subscriptions for hosting plans. If your business model doesn’t involve selling hosting services, you’re using the wrong tool [README][3].

The project is community-run, funded through Open Collective and GitHub Sponsors, and coordinated through a Discord server and public forum. There is no company behind it in the WHMCS or Blesta sense — no paid support tier, no enterprise contract [README][website].

---

Why people choose it over WHMCS, Blesta, and Paymenter

The comparison space for hosting billing software is small and dominated by a single incumbent: WHMCS. Every other tool in this category defines itself against it.

Versus WHMCS. WHMCS is the industry standard. It has the deepest integration catalog, the largest community of themes and modules, and the name recognition that makes clients trust your client portal. It is also a closed-source SaaS with a monthly fee that grows as your client base grows. For a hosting reseller with 50 clients, WHMCS costs real money every month for software you don’t own and can’t audit [3][5]. FOSSBilling is $0 for the software license, Apache-2.0, and you can inspect every line of code. That’s the entire pitch in one sentence.

The SatisfyHost comparison [3] positions FOSSBilling as the budget-conscious open-source option in a market where even the cheaper paid tools like Blesta start at $12.95/month (monthly plan) or $250 one-time. For a solo developer or tiny hosting operation, “free and auditable” beats “cheap but proprietary” most of the time.

Versus Blesta. Blesta is the developer-friendly paid alternative — clean codebase, modular architecture, one-time license option at $250–$300 (or $1,295 lifetime) [5]. Reviewers cite it as the closest paid competitor to WHMCS in terms of code quality. If you’re willing to pay once, Blesta is more mature and has a longer track record. FOSSBilling wins only if “zero software cost, Apache license, full source access” is a hard requirement for your business [5].

Versus Paymenter. Paymenter is a newer open-source entrant also positioned as a free WHMCS alternative. It appears on AlternativeTo’s list as a top alternative to FOSSBilling [1]. Neither project has extensive third-party review coverage, which makes direct comparison difficult. FOSSBilling has more GitHub history, more stars (1,506 vs. Paymenter’s smaller footprint), and a longer community track record as a BoxBilling successor.

On the beta status. The README note — “FOSSBilling is under active development and currently considered beta. Expect rough edges and limited support” — is the most important sentence in the entire codebase for a prospective user. This isn’t false modesty. The changelog shows frequent bug fix releases, including a 0.7.2 patch that fixed invoice authentication failures affecting cronjob tasks, renewals, and PayPal payments [2]. For a hosting business where broken invoicing means missed revenue, running beta billing software is a calculated risk, not just a philosophical stance.

---

Features

Based on the README and website documentation:

Billing and invoicing:

• Automated invoice generation and payment reminders [README]
• Multi-currency support with automatic exchange rate syncing [website]
• Support for multiple payment gateways: PayPal, Stripe, Mollie, and others [website]
• Recurring subscriptions and service renewals [README]
• Basic reporting [README]

Hosting provisioning:

• Automated account provisioning on cPanel/WHM, Plesk, DirectAdmin, HestiaCP, ISPConfig, Control-WebPanel (CWP) [website]
• 1-click WHM logins added in 0.7.0 [2]
• Server manager module architecture allows custom control panel integrations [README]

Domain management:

• Domain registration, transfer, and renewal [website]
• Multiple registrar integrations including Namecheap [website]
• Experimental EPP-based registry support [website]

Client management:

• Centralized client portal [README]
• Support ticket system with email notifications and automatic closure [website]
• Guest ticket submission supported [website]
• WYSIWYG editor for markdown content in client area (added 0.7.0) [2]

Security:

• IP blocking, reCAPTCHA, spam protection, CSRF prevention [website]
• Activity logging [website]
• Session fingerprinting [2]
• Email enumeration prevention via login attempt timing delays (added 0.7.0) [2]
• New security module and dashboard with configuration checks (added 0.7.0) [2]
• Debug logs now auto-mask sensitive parameters (added 0.7.0) [2]

Extensibility:

• Extension directory for themes, modules, payment gateways, server managers, and domain registrars [website]
• REST API with JavaScript API wrapper [README]
• Event hooks for custom logic [README]
• Twig templating system [README]

Other:

• Community-powered multi-language translations via Crowdin [README]
• Responsive UI [README]
• Simple CLI interface (added 0.7.0) [2]
• GeoIP with ASN information (added 0.7.0) [2]

---

Pricing: software cost vs. the competition

FOSSBilling (self-hosted):

• Software license: $0 (Apache-2.0) [README]
• VPS to run it: $5–15/month on Hetzner, Contabo, or Vultr
• Hosting requirements: PHP 8.2+, MySQL database (standard LAMP stack) [website]

WHMCS (the incumbent):

• Paid monthly subscription — pricing varies by client count. Specific current tier pricing not available in reviewed sources, but it is a per-client-count model where costs escalate as your business grows [3][5].

Blesta (closest paid open-codebase alternative):

• Monthly Branded: $12.95/month
• Monthly Unbranded: $14.95/month
• Owned Branded: $250 one-time (1 year support)
• Owned Unbranded: $300 one-time
• Owned Lifetime: $1,295 one-time [5]

HostBill (enterprise tier):

• Startup: $599 one-time
• Enterprise: $999 one-time
• Data Center: $1,599 one-time [5]

The math for a small hosting reseller:

If you’re running a small VPS reselling operation with 30–50 clients, your WHMCS bill is a fixed recurring cost every month, indefinitely. With FOSSBilling, you pay once for a VPS (~$6–10/month) and the billing software is free. Over 12 months: WHMCS (even at a conservative estimate) vs. $72–120 in VPS costs for FOSSBilling. Over 3 years, the gap widens. The open-source case isn’t just ideological — the math is straightforward for anyone not running a mature, WHMCS-dependent operation with custom module dependencies.

The one asterisk: Blesta’s owned lifetime license at $1,295 is arguably a better choice than FOSSBilling if you want software stability over software cost. You pay once and get mature, non-beta billing software with professional support. For a business where billing reliability is non-negotiable, “mature and paid once” might beat “free and beta.”

---

Deployment reality check

FOSSBilling runs on a standard LAMP or LEMP stack. The official documentation lists requirements including PHP 8.2+ (PHP 8.4 added in 0.7.0, PHP 8.1 support dropped in 0.7.0) [2], MySQL or MariaDB, and standard PHP extensions. There is an official Docker installation path in addition to traditional server installation [website].

What you need:

• A VPS or server with PHP 8.2+ and MySQL
• A web server (Apache or Nginx)
• A domain pointed at the server for your client portal
• An SMTP provider for email notifications and payment reminders
• Basic comfort with server administration

What can go sideways:

The 0.7.2 changelog [2] reveals a meaningful bug that slipped through to release: an invoice authentication issue that broke cronjob tasks, renewals, and PayPal payments. For a billing system, this is the category of bug that causes actual revenue loss. It was caught and patched, but the fact that it shipped to a release version is the kind of signal the README’s beta warning is referring to.

The codebase is actively being modernized — version 0.7.0 replaced the internal FOSSBilling\Request class entirely with Symfony’s HttpFoundation component and significantly refactored routing [2]. These are the right architectural moves, but they also mean the internal APIs are not stable between minor versions. If you’ve written any custom modules for FOSSBilling, expect breakage during upgrades.

AlternativeTo lists 218 open issues at the time of their last update [1], which is a relevant signal for a project of this size. That’s not disqualifying, but it’s worth checking the issue tracker before committing to a production deployment.

Realistic setup time for someone comfortable with Linux server administration: 1–3 hours including domain and SMTP configuration. For a non-technical user following documentation: half a day, assuming they’ve deployed a PHP application before. If this is their first time managing a VPS, budget a full day and expect to ask questions on the Discord.

---

Pros and Cons

Pros

• Apache 2.0 license. Genuinely open source — fork it, audit it, embed it, no legal complications [README][1]. This is the strongest differentiator from WHMCS.
• Zero software cost. For a bootstrapped hosting reseller, eliminating a monthly billing platform fee is immediately visible on the P&L [3][5].
• Full hosting automation stack. Billing, provisioning, domains, and support in one tool — no stitching together separate systems [website].
• Solid control panel coverage. cPanel, Plesk, DirectAdmin, HestiaCP, ISPConfig out of the box [website]. This covers the panels that actual customers use.
• Active development. Multiple releases shipped in 2025, including meaningful security improvements and PHP 8.4 support [2]. This is not an abandoned project.
• Standard stack. PHP + MySQL is deployable anywhere a LAMP host exists — no Docker requirement, no exotic dependencies [README].
• Extension directory. Community themes, payment gateways, and server managers available for installation [website].
• REST API included. Automation and external integrations are possible [README].

Cons

• Beta. The README says it plainly. Version 0.7.2 fixed a billing authentication bug that broke PayPal and renewals [2]. That’s not a theoretical risk — it’s a documented incident in recent release history.
• Limited third-party reviews. The review sources available are primarily roundup articles listing FOSSBilling alongside many other tools. There are no deep, first-hand “I ran this in production for a year” accounts to synthesize. This is a genuine information gap.
• No commercial support. Community Discord and forum only. If something breaks at 2am and your clients can’t pay, there’s no support contract to call [README][website].
• BoxBilling legacy. The codebase started as a fork of an abandoned project. The team is modernizing it (the Symfony HttpFoundation migration in 0.7.0 is evidence of this), but legacy architectural debt exists [2][website].
• Primarily for hosting businesses. The feature set maps to hosting-specific workflows. If you’re selling digital downloads, software licenses, or subscriptions unrelated to hosting, the tool works but feels like a square peg [README][1].
• Open issues count. 218 open issues on GitHub at last count [1]. For a project without a full-time engineering team, backlog growth is a real concern.
• PHP 8.2+ requirement. Not a problem for a fresh server, but a migration concern for anyone running legacy PHP infrastructure [2].

---

Who should use this / who shouldn’t

Use FOSSBilling if:

• You’re starting or running a small web hosting reseller or VPS provider business and the cost of WHMCS or Blesta is a real constraint.
• You want Apache-licensed billing software you can fork, audit, or customize without legal risk.
• Your provisioning needs are covered by cPanel, Plesk, DirectAdmin, HestiaCP, or ISPConfig.
• You have basic server administration skills and can manage a PHP application on a VPS.
• You can tolerate beta software and are willing to track releases and upgrade promptly when security patches ship.

Skip it (pay for Blesta instead) if:

• Billing reliability is non-negotiable and a production bug causing broken renewals would cost you clients.
• You want professional support with a real SLA when something breaks.
• You can budget a one-time $250–$300 for software that’s been through more production hardening.

Skip it (stay on WHMCS) if:

• Your operations already depend on WHMCS-specific modules, themes, or integrations from the WHMCS marketplace.
• Your clients expect the WHMCS client portal experience they already know.
• You have a team and need a billing platform that your staff can use without hand-holding.

Skip it (wrong tool entirely) if:

• Your business model has nothing to do with web hosting — you’re selling SaaS subscriptions, digital downloads, or consulting services. Look at Invoice Ninja, Akaunting, or a general-purpose billing tool instead [4].

---

Alternatives worth considering

• WHMCS — the incumbent. Closed source, paid subscription, largest integration and module catalog, deepest community. The tool everything else is measured against [3][5].
• Blesta — the best-regarded paid open-codebase alternative. Clean architecture, professional support, one-time license option, not free [5].
• Paymenter — newer open-source WHMCS alternative, listed as a top alternative to FOSSBilling on AlternativeTo [1]. Less history, smaller community, similar free-and-open premise.
• HostBill — enterprise-grade, one-time license, deep integration catalog (500+ modules), $599+ entry price. For large hosting providers, not resellers [5].
• Autumn — appears in the AlternativeTo alternatives list [1]. Limited publicly available information on features and maturity.
• Akaunting — if your actual need is general small-business invoicing and accounting rather than hosting-specific billing. Free, open-source, more mature for non-hosting use cases [4].
• InvoicePlane — open-source invoicing for freelancers and small businesses with no hosting-specific features. A better fit if you just need quotes and invoices [4].

---

Bottom line

FOSSBilling is the most viable free path out of WHMCS for a small web hosting operation that wants Apache-licensed billing software and doesn’t want to pay a monthly software fee indefinitely. It handles the core hosting billing stack — invoicing, provisioning, domains, support tickets — across the major control panels. The price is right and the license is genuinely open.

The honest caveat is the beta status. This isn’t marketing language; the changelog demonstrates it with a 0.7.2 patch that fixed a billing authentication bug affecting PayPal and renewals. If you run a hosting business where billing reliability is tied directly to revenue, you should either wait for a stable 1.0 release, run a staging instance for several months before going live, or pay for Blesta and get software with more production hardening behind it. If you’re starting out, can stay current with releases, and want to keep your infrastructure costs as low as possible — FOSSBilling is a legitimate choice.

---

Sources

1. AlternativeTo — FOSSBilling (community profile, 1,527 stars, alternatives, features). https://alternativeto.net/software/fossbilling/about/
2. FOSSBilling Changelog — official release notes for 0.7.0, 0.7.1, 0.7.2. https://fossbilling.org/docs/changelog
3. SatisfyHost — “Top 10 Best Web Hosting Billing & Automation Software in 2026” (Aug 24, 2025). https://satisfyhost.com/blog/web-hosting-billing-automation-software/
4. GeckoAndFly — “8 Best Free Accounting Software & CRM Invoicing For Small Businesses”. https://www.geckoandfly.com/35929/crm-invoicing-software/
5. RCTheme — “WHMCS Alternatives 2025-26: Top 7 Options, Price, Features”. https://www.rctheme.com/blog/whmcs-alternatives/

Primary sources:

• GitHub repository: https://github.com/fossbilling/fossbilling (1,506 stars, Apache-2.0 license)
• Official website: https://fossbilling.org/
• Documentation: https://fossbilling.org/docs
• Forum: https://forum.fossbilling.org
• Discord: https://fossbilling.org/discord