Paymenter

Open-source hosting billing, honestly reviewed. What you actually get when you ditch WHMCS and self-host it.

TL;DR

• What it is: Open-source (MIT) billing and webshop platform built specifically for hosting providers — subscriptions, invoicing, client management, and automated provisioning in a single panel [2].
• Who it’s for: Small-to-mid hosting companies tired of paying recurring WHMCS licensing fees, and technical teams who want billing they can actually modify, extend, and own [2].
• Cost savings: WHMCS starts around $16–25/month for entry tiers and climbs fast as your client count grows. Paymenter’s self-hosted edition is free software on a $5–10/month VPS, or $5/month on their managed cloud [website].
• Key strength: Built from the ground up for hosting workflows — not adapted from generic billing. Native integrations with Pterodactyl, cPanel, Plesk, DirectAdmin, and five other control panels out of the box [README][website].
• Key weakness: Younger project (1,547 GitHub stars) with a smaller community and module ecosystem compared to WHMCS. If you need something that works without any engineering, WHMCS is still more battle-tested [2].

---

What is Paymenter

Paymenter is an open-source billing platform built for one specific vertical: hosting companies. Where generic billing tools treat subscriptions as an edge case, Paymenter treats them as the core. The README description — “Free and open-source webshop solution for hostings” — is precise and honest in a way the homepage marketing copy (“Automate subscriptions, eliminate billing chaos”) is not [README][website].

The practical scope is: a customer-facing storefront where clients browse services and check out, a backend admin panel for managing those clients and services, an invoicing and payment collection engine, and automated provisioning hooks that fire when a client pays. That last part is what separates it from a generic invoicing tool — when someone orders a VPS, Paymenter can tell Pterodactyl to create the server automatically [website].

It runs on a standard PHP/MariaDB stack (PHP 8.3+, Composer, Apache or Nginx, MariaDB), which is the same environment most sysadmins in the hosting industry already operate. There is no Docker-first architecture, no Node.js runtime to babysit — it installs the way PHP apps have always installed [README][website docs].

As of this review, the project has 1,547 GitHub stars, 27,000+ total software downloads, and a Discord community of 2,570+ members. The primary sponsors are Kuroit and McSets, both hosting companies — which tells you exactly who the target user is [website][README].

---

Why people choose it

The systemadministration.net analysis [2] frames the decision well: the argument for Paymenter isn’t primarily about price, it’s about governability.

When a hosting provider runs WHMCS, they accept a set of dependencies: the vendor’s licensing terms, the vendor’s module marketplace, and whatever the vendor decides to change in the next version. This is fine until it isn’t — until pricing changes, until a module you depend on loses support, until you want to integrate billing with an internal tool and discover the API doesn’t expose what you need. The MIT license on Paymenter eliminates those risks structurally. You can fork it, modify it, run it on your own infrastructure, and integrate it with whatever you want [2][README].

The second argument is automation-first design. Billing software for generic businesses handles invoicing. Billing software for hosting businesses needs to handle the full service lifecycle: client orders, payment clears, server provisions, client gets credentials, renewal fires, payment fails, service suspends, client reactivates, service unsuspends [2]. Paymenter’s extension system is built around these workflows rather than retrofitting them.

The third argument, especially for smaller providers, is the WHMCS migration path. Paymenter ships a first-party importer for WHMCS data — clients, services, invoices — that runs as a single artisan command. The website shows a demo output importing 2,540 clients [website]. Importers for Blesta are listed as coming soon. That’s a real differentiator: migration friction is often what keeps small providers stuck on expensive legacy tools long after they’ve decided to leave.

---

Features

Client storefront and checkout:

• Configurable product catalog with pricing tiers [website]
• Customer self-service portal (order history, service management, invoice downloads) [website]
• Affiliate tracking and reward system [website]
• Multi-language support with built-in translation [website]
• Multi-currency support with automatic conversion [website]

Billing engine:

• Automated subscription renewal and invoice generation [README][website]
• Payment processing via Stripe, PayPal, and Mollie (bundled extensions) [website]
• Invoice management and audit trail [2]
• Support ticketing system built in — not a third-party integration [website]
• Announcement/blog system for customer communications [website]

Provisioning integrations (the critical differentiator): These are the extensions that make Paymenter a hosting platform rather than a generic billing tool:

• Pterodactyl — game server and VPS panel [website]
• cPanel — the industry standard shared hosting panel [website]
• Plesk — Windows/Linux hosting panel [website]
• DirectAdmin — lightweight hosting panel [website]
• Virtualizor — VPS management panel [website]
• VirtFusion — KVM VPS platform [website]
• Enhance — modern hosting platform [website]
• Convoy — Docker-based panel [website]

Developer and extensibility layer:

• Extension marketplace for community-built add-ons [website]
• REST API with OpenAPI spec published publicly [website]
• Theme engine for custom storefronts [website docs]
• Event system for hooking into billing lifecycle events [website docs]
• OAuth support for external integrations [website docs]

Migration:

• WHMCS importer (artisan command, handles clients + invoices + services) [website]
• Blesta importer: listed as “soon” [website]

---

Pricing: SaaS vs self-hosted math

Paymenter Cloud (their managed PaaS):

• Starts at $5/month [website]
• Marketed as “hassle-free,” includes automatic updates and backups [website]
• No detailed pricing tiers publicly visible beyond the entry price

Paymenter self-hosted:

• Software license: $0 (MIT) [README]
• VPS to run it: $5–15/month on Hetzner, Contabo, or DigitalOcean
• Your time to set up and maintain it

WHMCS for comparison (industry standard):

• Starter (~250 clients): ~$16–22/mo
• Plus (~unlimited clients, basic features): ~$35–45/mo
• Professional (full feature set): ~$70–90/mo
• Pricing has historically increased with new ownership changes, which is part of why the hosting community keeps looking for alternatives

Concrete math for a small provider:

Say you’re running 150 clients on shared hosting with automated renewals. On WHMCS Starter, you’re paying ~$22/mo — $264/year — for software licensing alone, before you pay for any third-party modules. On Paymenter self-hosted running on a $6 Hetzner VPS, your total is $72/year including infrastructure. That’s $192/year saved, or roughly enough to cover your VPS costs for three years [2][website].

For a mid-sized provider with 500+ clients needing the full WHMCS Professional tier at ~$80/mo, the math gets more dramatic: $960/year in licensing vs. $72 in VPS costs. The difference isn’t “nice to have,” it’s a meaningful chunk of operating cost for a bootstrapped hosting business [2].

Caveat: this math assumes you’re comfortable with PHP deployments and can do your own setup. If you need hand-holding, factor that cost in.

---

Deployment reality check

The installation documentation lists Ubuntu 20.04/22.04/24.04, Debian 10/11, and CentOS 7/8 as supported. Windows is explicitly unsupported [website docs].

Required stack:

• PHP 8.3 or higher
• Composer
• Apache or Nginx
• MariaDB (not MySQL — MariaDB specifically, which the docs make clear)

The installation path is a standard PHP app setup: install dependencies, clone repo, composer install, configure .env, run migrations, set up cron jobs and a systemd service. There is no Docker Compose shortcut out of the box — this is a more traditional server setup than projects like Activepieces or n8n [website docs].

What can go sideways:

• The PHP/MariaDB stack means more moving parts than container-based tools. PHP version mismatches, Composer version issues, and MariaDB vs MySQL compatibility quirks are all real failure modes [2].
• The extension integrations (cPanel, Pterodactyl, etc.) require additional configuration per panel. You’re not getting zero-config provisioning — each extension needs credentials and endpoint configuration [website docs].
• The project is relatively young (1,547 stars). WHMCS has been in production at thousands of providers for 15+ years. Edge cases in Paymenter’s billing engine that WHMCS handled years ago may still surface [2].
• Windows is not supported. If your operations team runs Windows servers, stop here [website docs].

For a technical user comfortable with Linux server administration, estimate 1–3 hours for a working install from a fresh VPS. For someone who hasn’t configured PHP and nginx before, budget a full day or use the managed cloud option.

The live demo at demo.paymenter.org is a practical asset — you can evaluate the admin UI and client portal before committing to any setup [README].

---

Pros and Cons

Pros

• MIT license, genuinely. Fork it, modify it, embed it in a managed service you resell — no licensing conversation needed [README][2]. This is the primary reason technical teams choose it over WHMCS.
• Hosting-native provisioning. Eight control panel integrations ship bundled: Pterodactyl, cPanel, Plesk, DirectAdmin, Virtualizor, VirtFusion, Enhance, Convoy [website]. This isn’t an afterthought — it’s the product’s reason for existing.
• WHMCS migration built in. An artisan-command importer for clients, services, and invoices removes the biggest friction from switching [website].
• REST API with OpenAPI spec. Publicly documented API means you can build internal tooling, reporting dashboards, or custom provisioning workflows against a stable contract [website].
• Full service lifecycle automation. Order → payment → provision → renewal → suspension → reactivation is the designed workflow, not a collection of workarounds [2][README].
• Multi-language and multi-currency out of the box. Useful for providers serving international markets without buying additional modules [website].
• Standard PHP stack. Deploying on environments the hosting industry already runs. No Docker dependency, no unusual runtime [README].
• $5/mo managed cloud option. For providers who want to try it before operating it themselves [website].

Cons

• Smaller community than WHMCS. 1,547 GitHub stars and 2,570 Discord members vs. WHMCS’s 15+ years of commercial adoption, forum threads, and third-party module vendors [website][2]. When something breaks at 2am, WHMCS has more community answers indexed.
• No Docker Compose out of the box. Traditional PHP/Apache/MariaDB setup requires more server administration competence than containerized alternatives [website docs].
• Extension marketplace is still growing. The marketplace exists but is smaller than WHMCS’s third-party module ecosystem. Specialized billing scenarios (complex taxation rules, country-specific payment methods beyond Stripe/PayPal/Mollie) may require custom extension development [website].
• Younger codebase. Edge cases that commercial billing software has handled for a decade — specific tax scenarios, unusual payment failure states, complex subscription modifications — may surface as bugs in Paymenter [2].
• No Blesta importer yet. If you’re coming from Blesta specifically, migration is a manual process [website].
• Windows not supported. Explicit in the docs [website docs].
• Pricing transparency limited. The managed cloud offering lists “$5/month” but doesn’t publish detailed tier breakdowns publicly. You have to contact or sign up to find limits [website].

---

Who should use this / who shouldn’t

Use Paymenter if:

• You’re running a hosting business — VPS, shared hosting, game servers, managed services — and you’re paying WHMCS licensing fees that you’d rather not.
• Your team includes at least one person comfortable with Linux server administration and PHP deployments.
• You need automated provisioning hooks into Pterodactyl, cPanel, Plesk, or DirectAdmin, and you don’t want to pay per-module for each integration.
• You value owning your billing infrastructure over having a vendor-supported product with a phone number to call.
• You’re migrating from WHMCS and want a first-party import tool for your client data.

Skip it (stay on WHMCS) if:

• You need battle-tested billing software that thousands of providers have stress-tested over a decade. WHMCS has seen more weird billing edge cases than Paymenter has.
• Your billing requirements are complex — advanced tax rules, country-specific compliance, dozens of payment gateways — and you need a large third-party module ecosystem to fill gaps.
• Your team has zero Linux server administration capacity and the managed cloud option ($5/mo) still requires more setup than you want to do.
• Downtime in billing directly translates to revenue loss and you need a commercial SLA.

Skip it (try FOSSBilling instead) if:

• Your hosting setup is simpler and you want an alternative open-source option with different design choices.

Skip it entirely if:

• You’re not running a hosting business. Paymenter is built for hosting-specific workflows — control panel provisioning, bandwidth-based billing, server lifecycle management. Using it for a SaaS or e-commerce business would mean fighting the tool at every step.

---

Alternatives worth considering

WHMCS — the incumbent and industry standard. Most third-party integrations exist for WHMCS first. Proprietary, licensed per client count, has changed pricing multiple times under different ownership. The migration story from WHMCS to Paymenter exists specifically because this has frustrated enough providers to build it [website][2].

Blesta — commercial billing for hosting, similar positioning to WHMCS but different company. Also proprietary, also requires per-module purchases for integrations. Paymenter’s Blesta importer is listed as coming soon, which is a signal that some providers are making that specific switch [website].

FOSSBilling — the other open-source billing platform in this space. Also MIT-licensed, also self-hostable. Less hosting-native than Paymenter but more generalist. Worth evaluating if your provisioning needs don’t match Paymenter’s bundled integrations [2].

Pterodactyl — not a billing platform, but worth naming because many game server hosters are already running it. Paymenter integrates with Pterodactyl for provisioning — they’re complementary, not competing [website].

For a hosting provider specifically, the realistic shortlist is Paymenter vs WHMCS. The question is whether the cost savings and MIT license outweigh the ecosystem maturity gap. For small-to-mid providers with technical teams, the math increasingly favors Paymenter.

---

Bottom line

Paymenter is a technically sound, purpose-built billing platform for hosting providers who are willing to run their own infrastructure. The MIT license removes the vendor dependency risk that has repeatedly bitten WHMCS users when licensing terms changed. The provisioning integrations cover the major control panels that the hosting industry runs. The WHMCS migration tool is a real asset. What you give up is the maturity and ecosystem depth that 15 years of commercial development buys — the edge case handling, the deep third-party module catalog, the community answers that exist for every WHMCS problem. If you have a technical team and are paying meaningful WHMCS licensing fees, the switch math is clear. If you’re a solo operator with no Linux administration background and billing is mission-critical, the managed cloud option or staying on WHMCS is the safer path.

If the self-hosting setup is the blocker, that’s exactly what upready.dev deploys for clients. One-time fee, done, you own the billing infrastructure.

---

Sources

1. System Administration — “Paymenter: the Open-Source Billing Platform Aiming to Simplify Hosting’s Billing Chaos” (Jan 10, 2026). https://systemadministration.net/paymenter-the-open-source-billing-platform-aiming-to-simplify-hostings-billing-chaos/

Primary sources:

• GitHub repository and README: https://github.com/paymenter/paymenter (1,547 stars, MIT license)
• Official website: https://paymenter.org
• Installation documentation: https://paymenter.org/docs/installation/install
• Extension marketplace: https://paymenter.org/marketplace
• REST API / OpenAPI spec: https://paymenter.org/api/
• Live demo: https://demo.paymenter.org