Every input and output is a plugin.
Payments, hypervisors, game panels, notifications. Stripe and SolusVM 2 are seeded into every tenant. The rest install on demand or you build them in the visual editor.
Four integrations that exercise the full surface area.
Seeded payment plugin. GatewayRegistry resolves it at runtime, no restart required.
Seeded infrastructure plugin. Adapter bridges to the provisioning interface.
Core importer. Idempotent, resumable, dry-run before commit.
Notification plugin. Subscribes to PlatformEventBus, formats with Handlebars.
Browse the directory.
Every plugin runs through the same registry, with the same lifecycle hooks. Statuses are honest: Shipped is seeded into every tenant, Available installs on demand, 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. Seeded into every tenant.
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. Build with the visual editor.
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.
POS-friendly card processing.
Provision and lifecycle servers, containers, and game pods. Resolved through VisualPluginAdapter.
Project-scoped VM provisioning, snapshots, ISO library. Seeded into every tenant.
KVM, OpenVZ, LXC. Stock check, OS install, console.
Game-server panel — Minecraft, Rust, ARK, more.
Shared hosting accounts and reseller packages.
VE clusters with HA-aware node selection.
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.
One-shot data importers from legacy hosting platforms. Idempotent, resumable, dry-runnable.
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
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.
- 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.