Flaem runs a service from purchase to renewal: the client pays in the store, a node provisions the server, and the panel keeps track of payments, limits and live metrics. The store is no bolt-on plugin: it shares the accounts, wallet, invoices and services, so the operator maintains no link between sales and servers. The panel, its database and client data live on the operator's machines.
What the Flaem panel sells, and how
| Part | How it works |
|---|---|
| Offers and plans | one offer, such as Minecraft servers, with resource plans; the client picks the engine, game version and add-ons in the cart and sees the total before paying |
| Hardware tiers | a Premium plan starts only on nodes carrying the same tag, with no second offer to maintain |
| Coupons and promotions | before publishing, a preview shows the price of every plan in every billing period |
| Software licences | the client gets the key once the order is paid, and renewals come out of the wallet with a reminder and an invoice |
| Payments | a payment issues the invoice and starts or renews the service in the same transaction, and Polish invoices reach KSeF from a background queue |
A licence that never stops your clients
The Flaem licence is not tied to your client count and takes no commission on sales. You activate it with a key or a signed offline token, with which the panel never contacts the licence server. A late payment first blocks new nodes and offers, then switches the admin panel to read-only. At every stage your hosting clients keep buying, renewing, restarting servers and opening the console, and they see nothing about your licence.
Payments, reseller white-label and migration from other panels are in the Flaem case study.
Was this post helpful?
