Every input and output is a plugin.
FluxBilling treats a hosting provider's payments, hypervisors, game panels, and notifications as plugins. Nothing is pre-installed and nothing costs extra — every plugin in the marketplace, Stripe and Proxmox VE included, is free and installs per tenant, or you build your own in the visual editor.
Four integrations that exercise the full surface area.
Marketplace payment plugin. GatewayRegistry resolves it at runtime, no restart required.
Marketplace infrastructure plugin. Adapter bridges to the provisioning interface.
Core importer. Reads the WHMCS database, never writes back; re-runs skip records already imported.
Notification plugin. Subscribes to PlatformEventBus, formats with Handlebars.
Browse the directory.
Nothing is pre-installed. Every plugin runs through the same registry, with the same lifecycle hooks. Statuses are honest: Available installs on demand from the marketplace, Shipped means it's built into core (migration importers only, not a plugin install), Build it means there's a starter template, Planned is on the roadmap.
Charge customers, refund disputes, settle webhooks. Resolved at runtime through GatewayRegistry.
Cards, wallets, recurring, refunds. Install from marketplace.
Standard checkout + webhook reconciliation. Install from marketplace.
iDEAL, SEPA, Bancontact, cards. Install from marketplace.
BTC, ETH, USDT and more. Install from marketplace.
Manual reconciliation flow. Install from marketplace.
SEPA Direct Debit and ACH.
Card vault and recurring profiles.
Global card processing across markets.
Merchant-of-record. Tax handled at the gateway.
Wallet checkout, supported in EU markets.
Multi-coin crypto checkout.
BTC and Lightning settlement.
Enterprise card acquiring.
India-region card and UPI processing.
Multi-coin crypto checkout, alternate settlement rails.
POS-friendly card processing.
Provision and lifecycle servers, containers, game pods, and domains. Resolved through VisualPluginAdapter.
VE 7/8 KVM guests cloned from cloud-init templates; console and snapshots.
KVM servers from VirtFusion packages; single sign-on into the panel.
KVM, OpenVZ, LXC plans. Emptiest-server placement, OS install, VNC console.
Plans, locations and OS images per product; VNC console and reinstall.
Game-server panel — Minecraft, Rust, ARK, more. SFTP, backups, eggs.
Shared hosting accounts from WHM packages; cPanel, Webmail and phpMyAdmin SSO.
Domain registration, renewal, nameservers, registrar lock, WHOIS privacy.
Subscription provisioning on Plesk Onyx and Obsidian.
Self-hosted IaaS with Nova, Neutron, Cinder.
Event-driven outbound to chat and ticketing. Subscribes to PlatformEventBus.
Bot delivery for ticket, billing, and provisioning events.
Webhook delivery to staff channels.
Incoming webhooks for billing and ops alerts.
Forward billing events to external analytics platforms. Subscribes to PlatformEventBus.
Purchases, refunds, sign-ups forwarded with multi-currency revenue tracking.
One-way data importers from legacy hosting platforms. Read-only against the source system.
Clients, services, invoices, transactions, tickets, tokenized cards.
Locations, racks, devices, IPAM, components.
Customers, packages, services with proration carry-over.
Multi-brand client and service migration.
Email transports are core, not plugins.
Transactional delivery for invoices, dunning, password resets, and ticket replies is wired into the platform. Configure from Settings, no install step.
Templates are stored per tenant in the email_templates table and rendered with Handlebars.
- SMTPcore
- Sendmailcore
- Mailguncore
- SendGridcore
- SparkPostcore
- Microsoft 365core
- Gmailcore
Building and shipping a plugin.
What a plugin is, and why it is a no-code flow rather than a PHP module.
The five-step New Plugin wizard, from scaffold into the builder.
Nodes, wiring, and how a flow executes at runtime.
The contract a plugin declares, and what the platform calls.
Credential storage, auth modes, and testing a connection.
The expression sandbox, and what it deliberately cannot do.
Building a notification channel rather than a gateway.
Moving a plugin between instances and versioning it.
The icon set a plugin can draw from in the builder and the admin UI.
Build your own without touching core.
The visual flow editor is the canonical way to extend FluxBilling. Drag nodes onto a canvas, wire them together, save the plugin, register it at runtime — no rebuild, no FTP.
Start, end, HTTP, condition, switch, transform, status map, set variable, loop, delay, log, format message.
Ready-made node patterns: HTTP+check, success/error branch, loop over array, transform+output, full action.
VPS, game server, web hosting, domain, license, blank — ship with sample connections and flows.
payment-gateway, infrastructure-provider, notification-integration, automation, custom.
PluginPackager exports a plugin as a .xzplugin tarball — flows, connections, config schema, and metadata in one file. Import it from the marketplace browser.
- The visual editor and the .xzplugin export use the same package format.
- Payment plugins register through GatewayRegistry at runtime.
- Infrastructure plugins bridge through VisualPluginAdapter.
Each tenant runs its own plugin set inside its own K3s pod with its own database. Plugin flows hold no privileged platform access — same internal interfaces, same auth, same rate limits as any other actor.
- Plugins live in the tenant's own visual_plugins table.
- Connections are encrypted with the per-tenant settings key.
- Lifecycle events route through PlatformEventBus.
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.
- 01.< 1 minPick a tierLite from €4.95/mo. Upgrade later, no migration.
- 02.< 2 minProvision the tenantIsolated K3s namespace + your own PostgreSQL database. Full product, your data.
- 03.d0 — d14Refund inside 14 daysNot the fit? Open a ticket within 14 days and we refund the subscription. No questions, no qualification gate.