FluxBilling
Alternative to ClientExec

The ClientExec alternative built like an app.

ClientExec is a long-standing PHP billing platform, sold since December 2025 only as a monthly lease. FluxBilling is a ClientExec alternative built as a multi-tenant SaaS: a React 18 SPA with automated recurring billing, integrated DCIM, a visual plugin builder, and continuous updates. Trade-offs honestly compared, migration steps spelled out.

Plans from €4.95/mo·Migration support included·last reviewed 2026-05-11
Platform deltas

Where the platforms diverge.

The four facts that summarise the difference between ClientExec and FluxBilling. Everything else is consequence.

K3s
Per-tenant isolation
pod + database
DCIM
Same schema as billing
rack, IPAM, IPMI
0
Per-gateway add-on cost
all included
Visual
Plugin builder
JSON manifest
In short

ClientExec is a long-standing PHP billing platform whose defining feature is a flat leased price with unlimited clients — $16.95/mo branded, $19.95/mo unbranded (clientexec.com/pricing, checked 2026-10-14; the one-time lifetime licence it was long known for is no longer sold). The trade-off is an older codebase, a slower release cadence, and no DCIM. FluxBilling is a ClientExec alternative built as a multi-tenant SaaS: a React 18 single-page app on PostgreSQL 16 with automated recurring billing, integrated DCIM and IPAM, a visual plugin builder, and continuous updates. It is a subscription on every tier, not a perpetual license, though the Business tier adds a one-time self-host fee to run it on your own infrastructure. There is no automated ClientExec importer today — migration is a scoped services engagement with a sandboxed test import before cut-over. If you already own a ClientExec licence and need nothing beyond billing, staying put is hard to beat on cost.

Feature-by-feature

Side-by-side, no asterisks.

Based on publicly available ClientExec documentation as of May 2026. Verify current capabilities with the vendor before purchase.

FeatureFluxBillingClientExec
License model
DistributionSaaS subscriptionMonthly lease, self-hosted
Owned (lifetime) license—No longer sold; existing ones stay valid
Updates includedContinuous, no extra tierIncluded with the lease
HostingManaged, included; Business self-hostsSelf-host or hosted add-on
Stack & UI
FrontendReact 18 SPAServer-rendered PHP
Page-reload-free adminYesNo[1]
Visual plugin builderYesNo[1]
Operator surface
Integrated DCIM (rack + IPAM)YesNo[1]
Bare metal IPMI/RedfishYesNo[1]
JSON plugin manifestYesNo[1]
Multi-tenant SaaS optionYesNo[1]
Provisioning
Proxmox VE / VirtFusion / Virtualizor / SolusVM 2Free pluginsLimited[1]
Auto-suspend on overdueYesYes
Stock check + allocationBuilt-inManual[1]
Security & audit
Public roadmapYesNo[1]
Two-factor authAuthenticator app (TOTP) or email codeEmail-code 2FA[2]
CSP + rate limitingOn by defaultPartial[2]
Per-tenant activity logYesLimited[2]
  1. [1] Source: clientexec.com product and feature documentation; not advertised as a built-in capability (captured 2026-05-11).
  2. [2] Source: clientexec.com security and account-settings documentation (captured 2026-05-11).

source: clientexec.com docs · reviewed 2026-05-11

Migration path

From ClientExec to FluxBilling.

Five steps. The data moves with AI Migration in the admin panel, which maps the ClientExec database for you and imports only what you approve. The migration team is there for plugin parity and cut-over if you want a hand.

  1. 01.
    Connect the database

    In the admin panel, add your ClientExec MySQL database as an AI Migration source, directly or through an SSH tunnel. The connection is read-only, and its password never reaches the AI.

    self-serve
  2. 02.
    Mapping and preview

    Admin AI reads the tables and proposes how clients, product categories, products, services, invoices and payments map onto FluxBilling. You approve the mapping, then a read-only preview shows the counts, warnings and anything that would block the import. Tickets and custom fields stay behind.

    you approve
  3. 03.
    Plugin parity

    For each ClientExec module you depend on (gateway, provisioner, custom hook), we either point to an equivalent FluxBilling visual plugin or build a one-off using the visual builder.

    ~ 1 week
  4. 04.
    Cut-over

    Approve the import, check the result, DNS swap, gateway re-tokenisation. A re-run only adds what is new. Customers set a new password with a password reset on first sign-in — there is no automated cross-platform hash rehash.

    ~ 2h window
  5. 05.
    Post-cutover

    Two weeks of priority support while ticket history, dunning rules, and any custom email templates settle in. ClientExec read-only is kept up for archival.

    14 days
Why different

Four mechanisms, not adjectives.

The differences that show up in day-to-day operator work. Concrete, measurable, and the reason migrations get planned in the first place.

Modern stack, on purpose
React 18 SPA, queued workers, optimistic UI. The platform feels like an app — because it is one. ClientExec's core remains classic server-rendered PHP, with the constraints that come with it.
DCIM is core, not bolted on
Rack U-positions, IPAM hierarchy, IPMI/Redfish bare-metal control are first-class objects in the same database as your invoices, feeding straight into automated provisioning. No separate DCIM product to license and sync.
Plugins via visual flows
New gateway, new provisioner, new notification channel — built on a node-based flow editor with a JSON manifest format. Stored in the tenant database, not files dropped over FTP.
Active development
Public roadmap, continuous patches across the SaaS fleet, no separate maintenance tier required to receive security updates.
Honest no-list

When ClientExec is the right call.

A SaaS subscription is not always the answer. Three situations where ClientExec genuinely wins, and we will say so up front.

Already on an owned licence

Clientexec stopped selling owned licences in December 2025, but every existing owned or lifetime licence stays valid. For a small operator with a fixed feature set, a licence that is already paid for is hard to beat on cost.

On-prem only, no exceptions

The Business tier self-hosts on your own infrastructure for a one-time fee (the subscription continues), which covers most on-prem requirements. Lite, Starter and Professional are SaaS only. If you need an on-prem install below Business, ClientExec's self-hosted lease fits there and FluxBilling does not.

Existing module investment

A library of ClientExec custom modules you do not want to rewrite right now is real switching cost. Stay until the FluxBilling plugin equivalents land or until you're replatforming anyway.

FAQ

Common questions before switching.

Isn't an owned ClientExec licence cheaper long-term?
If you already hold one, often yes — Clientexec discontinued owned licence sales in December 2025 but honours existing ones, and a licence you have paid for is hard to beat for a small operator with a static feature set. New customers can only lease: $16.95/mo branded or $19.95/mo unbranded, per Clientexec's December 2025 pricing update. The cost shows up elsewhere: ongoing patches typically require an active support tier and the codebase is older PHP. If you don't need active feature shipping or a modern stack, an owned ClientExec licence wins on raw cost; for a new lease, FluxBilling Starter costs less up to 150 clients, and ClientExec's unlimited-client lease costs less above that.
Why pay a SaaS subscription instead of buying once?
You're paying for ongoing development and managed hosting, not the binary. FluxBilling ships continuously, includes hosting, and bundles DCIM and all gateways. A self-hosted licence is the software only; the server, backups and upgrades to run it are yours to provide.
Does FluxBilling have a one-time license tier?
Not a perpetual license — every tier is a subscription. But the Business tier offers self-host: keep the monthly subscription and pay a one-time fee to run it on your own infrastructure, with the same billing, DCIM, and provisioning. Lite, Starter and Professional stay managed. Updates ship continuously either way; the difference is where it runs.
Can I migrate from ClientExec?
Yes, with AI Migration in the admin panel. A super admin connects the ClientExec MySQL database (read-only, directly or over SSH); Admin AI proposes how clients, products, services, invoices and payments map across, shows a read-only preview, and imports only after you approve. Tickets and custom fields are not imported, and customers set a new password after cut-over. If you would rather not run it yourself, open a ticket and the migration team will.
Will my customers be forced to reset passwords?
Yes. There is no automated cross-platform password-hash rehash; at cut-over a password reset email is sent so customers can set a fresh password on FluxBilling. We help schedule the email and the comms around it.
How do you compare on security posture?
CSP headers, rate limiting, IP allowlisting, and a per-tenant activity log are on by default, and 2FA by authenticator app (TOTP) or emailed code can be made mandatory separately for staff and for clients. Patches roll out across the SaaS fleet without a separate paid maintenance tier.

ClientExec is a trademark of its operator. This page is not affiliated with, endorsed by, or sponsored by ClientExec. All product names, logos, and trademarks are the property of their respective owners. Comparison data is based on publicly available documentation and pricing as of May 2026, is provided for informational purposes only, and may not reflect the most current features or pricing. Verify all details directly with the respective vendors before making purchasing decisions.

Get started

Try it on your own data. Refund inside 14 days if it’s not the fit.

Pick a tier and provision a tenant in under two minutes — isolated K3s namespace, your own database, the full product. If FluxBilling isn’t the right fit inside 14 days, open a ticket and we’ll refund the subscription. No sales call, no qualification gate. Want to look around first? The live demo opens the admin and client panels with sample data, no signup.

14-day refund
Standard policy
  1. 01.
    Pick a tier
    Lite from €4.95/mo. Upgrade later, no migration.
    < 1 min
  2. 02.
    Provision the tenant
    Isolated K3s namespace + your own PostgreSQL database. Full product, your data.
    < 2 min
  3. 03.
    Refund inside 14 days
    Not the fit? Open a ticket within 14 days and we refund the subscription. No questions, no qualification gate.
    d0 — d14
14-day refund · cancel any time
Start →