Every Flaem feature, from a game server to an e-invoice
Flaem is the service panel, store and billing system for hosting companies, installed on your own servers. Below is every module in turn: what you sell, how you run hosting day to day and how you move over from the panel you use today. Each one links to a page that covers it in detail.


Game servers your clients run on their own
The library has 36 games and 97 ready server definitions, from Minecraft and Counter-Strike to Rust, FiveM and SCP: Secret Laboratory. Your client buys a server in your store and manages it straight away, while you bill and invoice it in the same system. Games outside the list come in as Pterodactyl and Pelican eggs.


A Minecraft server panel and the invite card players send to their friends.
Console, files and backups without a ticket
The client sees a live console in the browser, edits files in an editor much like VS Code and uploads larger batches over SFTP. Backups are incremental, and files shared by servers of the same game sit on disk once. A scheduled restart counts down in the game chat first, so players have time to save.
Mods, versions and updates in one click
Mods from Steam Workshop and Thunderstore, modpacks from Modrinth and CurseForge and game updates from Steam are installed from the panel. The client picks the game or Java version from a list and sees the startup settings as a form with descriptions instead of raw variables.
When a server crashes, the owner knows why
Instead of a log they cannot read, they get a plain sentence in their own language, a help article and a fix button, such as changing the Java version or accepting the EULA. When they run short on resources, they see a bigger plan suggested, priced to the second.
Discord, player funding and a store on the server
The bot runs on your own Discord application, so your brand is the one talking on your clients' servers, with a server status card, crash alerts and commands for servers, backups and invoices. Players chip in for the renewal through player funding or buy items in the store on the server, and the money goes through your billing.

Minecraft: 24 server types, plugins and the Flaem plugin
A Minecraft offer in your store has resource plans, and the client picks the engine and version at checkout from a list you control. Every server type is in the library as a ready definition, so you switch on only the ones you want to sell.
- Java15
- Vanilla, Paper, Purpur, Spigot, Folia, Leaf, Pufferfish, Fabric, Forge, NeoForge, Quilt, Mohist, Arclight, SpongeForge, SpongeVanilla
- Proxy3
- BungeeCord, Velocity, Waterfall
- Modpacks2
- CurseForge, Modrinth
- Bedrock3
- Official server, PocketMine-MP, PowerNukkitX
- Geyser1
- Geyser as a standalone server
Plugins and mods from 4 catalogues
The client searches Modrinth, Hangar, SpigotMC or GeyserMC and installs a plugin in one click. Flaem pulls in the dependencies and checks the checksum of every file before it reaches the server. There are also 8 ready plugin sets and 4 templates for whole servers.
World rules without commands
Switches and number fields for 20 world rules replace commands in the game, and on a running server the change applies at once. The client sets the server icon and its coloured description with a preview that shows the line the way players will see it in the in-game server list.
Bedrock players and the Flaem plugin
One switch installs Geyser and, optionally, Floodgate, so players on phones and consoles join the Java server on the same port. The Flaem plugin on Paper, Purpur and Folia shows players, inventories, TPS and statistics in the panel, and hands out purchases from Tebex, CraftingStore, MineStoreCMS and ItemShop.pl in game.
VPS, VDS and LXC containers on your own Proxmox
Flaem drives Proxmox VE 8 and 9. The client picks the plan, system, SSH keys and hostname in one step, pays and shortly logs in to a running machine, without your team lifting a finger. The invoice and the renewal come from the same system.
KVM VPS
A full virtual machine from a system template, from an ISO in your catalogue or from the client's own image. The node keeps ready machines in reserve for the most popular plans, so an order starts in seconds rather than minutes.
VDS
Dedicated cores and memory on a virtual machine, sold as a separate product with its own price and limits. You set the virtual hardware profile for every plan.
LXC containers
A cheaper alternative to a VPS with the same set of actions in the panel. Nesting lets clients run Docker inside.
What the client does alone, without a ticket
- Browser console
- noVNC and a serial console keep working even when the client has cut off their own network.
- ISO images and rescue mode
- Booting from an ISO in your catalogue and fixing a broken configuration.
- Snapshots and backups
- A snapshot before a risky change and backups off the node, including a second location.
- Firewall and rDNS
- Traffic rules for the machine and reverse DNS set in the panel, no rules written in the system.
- IP addresses
- Extra addresses from your pool, or a cheaper VPS without its own IPv4.
- Plan changes
- Bigger or smaller on any day of the period, priced to the second.


A VPS for clients who have never opened a terminal
The Flaem agent runs inside the client's VPS and does what usually takes commands: it installs apps, connects a domain with HTTPS, updates the system and keeps access in check. The client clicks in a panel under your brand, and you sell VPS to people who are not administrators too.
App wizard
An app or a whole stack, port, domain and certificate in one pass, with a forecast of CPU, memory and disk use before the install.
Timed access
The client invites a helper, and the agent creates an account with a key and an expiry date. Once access is revoked, it removes the account together with the key.
Dedicated servers from the shelf to the client and back
Flaem takes every physical machine through its whole cycle, so a restart, a reinstall or the console is a button in the panel rather than a call to the data centre. The client buys a plan, not a particular box: Flaem picks a free machine with the plan's hardware in the location the client chose.
After a contract ends, the machine never goes back on sale by itself.
- 01InventoryLocation, rack, serial number and state of every machine.
- 02Burn-inSeveral hours under full load and a report before the machine goes on sale.
- 03Sold off the shelfA free machine is assigned automatically the moment the order is paid.
- 04Network installBoots from the network through the Flaem foothold in the rack, no USB stick.
- 05With the clientPower through Redfish or IPMI, SOL and KVM console in the browser.
- 06Safe returnPower is cut and the machine goes back to service with a "wipe disks" note.

GPU servers and AI models as a service
You sell a server with graphics cards like a dedicated server or a VPS: from inventory, with an invoice and a renewal. The panel shows the load, memory, temperature and power draw of every card separately, next to the CPU, disks and network of the whole machine.
- Dedicated server with GPUs
- The client gets the whole machine with its cards, with a network install, the controller and the console.
- VPS with a card
- A card assigned to a virtual machine on a Proxmox node, in the same panel as a regular VPS.
- AI model as a service
- The model runs on your cards, and the client sends requests without managing a server.
Websites and apps on the same nodes as your games
The client buys a web plan and puts several sites in it: WordPress, a PrestaShop store or an app from a git repository. Every site runs in its own container, with a domain, a certificate, a database and backups, and when resources run short, game servers come first.
- WordPress with a restore point
- The installer sets up WordPress without manual work, and right before every update Flaem saves a restore point of the site that the client can go back to if something stops working.
- Apps from git
- The client points at a repository, and Flaem builds the app within the resources of their plan, so the build does not slow down other services on the node.
- A copy of the site for testing
- The client tries a risky change on a copy with a temporary address, without connecting a domain. Every file change goes into a history it can be undone from.
- PHP, traffic and statistics
- PHP 8.2, 8.3 and 8.4 for each site separately, your own WAF and CDN or Cloudflare, traffic rules set visually and visitor statistics from the server logs, with no tracking script.
PHP
15WordPress, Joomla, Drupal, PrestaShop, Grav, Laravel, Nextcloud, MediaWiki, DokuWiki, phpBB, Matomo, FreshRSS, Kanboard, phpMyAdmin, PHP-FPM
Node.js
2Ghost, Node.js
Python
2Python ASGI, Python WSGI
Static site
1HTML, CSS and files with no server-side code
Domain, DNS and business email in the same cart as the server
The client searches for a domain in your store, registers it, sets its records and creates mailboxes in the panel where their server already is. They need no separate registrar account and no separate mail panel, and you set the prices and the margin.
- 1
Registration
Openprovider, AfterMarket.pl, ResellerClub, CentralNic, OVHcloud, Namecheap, Porkbun, domeny.tv and NASK directly. You set the account order for each TLD, so when the first one does not answer, the registration goes through the next.
- 2
DNS zone

A zone editor on your PowerDNS or in Cloudflare, with DNSSEC and glue records. You can also sell managed DNS as an add-on.
- 3
Mail records
MXSPFDKIMDMARCThe moment email is switched on, Flaem adds the records to the zone, and the mail status screen shows whether everything matches before the client notices that something is not arriving.
- 4
Mailboxes

Mailboxes, aliases and catch-all on mailcow servers from a pool. You sell email in the plan price or as an add-on charged per domain.
- Full support for .pl domains
- You register .pl domains through Polish registrars or directly with NASK, with the same actions in the client panel: transfer with a code, WHOIS and DNSSEC.
- Price from cost or fixed
- Your margin is added on top of the registrar's cost, so the price follows it, or you set a fixed amount for a TLD that no price list will change.
- Domains you already have, and your own registrar
- You take over the domains on your registrar account into Flaem and assign them to clients. A registrar outside the list is described in a form, connected through your own bridge or, as an accredited registrar, reached directly over EPP.
Backups, S3 object storage and databases as your own products
A backup on the same disk as the machine disappears together with it. So for every plan you decide where backups go, and you sell storage for client data as separate services, billed like any other.
S3 object storage
S3-compatible storage that applications write to over the internet. The client connects it to any tool that supports the standard.
Storage box
A plain disk reachable over the network that the client sends nightly backups to, with no system to update and secure.
Managed databases
MySQL, MariaDB and PostgreSQL with access, backups and limits in the panel. The client sees database size, slow queries and locks, and you see every database on every host.
Incremental game backups
Shared game files sit on disk once, and every later backup stores only the changes. The client restores the whole server or selected files, databases included.
IP transit, addresses, BGP and ASN sold like any other service
When you run your own network, companies buy more than servers from you: internet access, IP addresses and help getting their own network number. Flaem runs these services from the order in your store, through the BGP session and the RIPE database entry, to the invoice and the renewal.
- IP transit
- For a company with its own ASN
- GRE tunnel
- For a machine outside your network
- IPv4 and IPv6 leasing
- For a company without its own pool, with a RIPE entry
- ASN registration
- Application, documents and status in the client panel
BGP on BIRD 2 with RPKI
Sessions with clients, sub-operators and your upstream, each with an owner, a route filter and a history. Route objects and client subnet assignments go to the RIPE database straight from the panel.

Address pools without conflicts
Every address has a state in the panel: free, assigned to a service, assigned permanently to an account or leased out. The same address never ends up on two machines.
Network tools
Looking glass and a latency test for clients, and for you link quality measurement, sFlow and NetFlow traffic analysis, switches from the panel and detection of attacks leaving client machines.
DDoS protection at your provider
You set filters once, for the port ranges of a game, and every new server lands behind the right filter by itself. Clients see attacks on their addresses in the panel.
- Path.net
- OVH
- Cloudflare Magic Transit
- NeoProtect
Billing wired into the servers, no separate system needed
Flaem takes payments, issues invoices, renews services and stops unpaid ones in the same system that runs your clients' servers. You need no separate billing system and no module to connect it to the panel.
Client wallet
The client tops up the balance at any time, and each service takes its fee from it on its own renewal day. Refunds, compensation and referral rewards land in the wallet too, and every movement has its document.
BLIK in the panel and saved cards
The client enters a BLIK code without leaving the panel. You decide whether saved cards with automatic renewal are on, and every gateway starts in test mode so the first real payment never arrives by accident.
Unpaid services
A reminder before the due date, then suspension instead of deletion if nothing is paid. You set the suspension and deletion timings per product family, and after payment the service comes back on its own.
Contracts, SLA and hours
Minimum contract terms, your own SLA and compensation rules, admin work billed per started hour and temporary resource boosts paid by the hour.
Seven payment gateways, plus crypto through BTCPay
- Stripe
Przelewy24
Tpay
PayU- PayPal
paysafecard
SimPay
- 1-3,650days
- is how long a billing period can be, and every period has its own discount or surcharge
- 1-2,160hours
- of trial, free or paid, with a card required up front if you set it so
- 8reports
- for your accountant after the month closes, in one package with the JPK file
The invoice from a payment goes to KSeF on its own
Flaem issues the invoice the moment the client pays, builds the FA(3) file and sends it to KSeF, Poland's national e-invoicing system, in the background. A purchase never waits for KSeF, so an outage on the KSeF side blocks no sale and no renewal.
- 1
Payment
The client pays through a gateway or from the wallet.
- 2
FA(3) invoice
Created at the same moment as the payment.
- 3
Background queue
Retries the upload when KSeF does not answer.
- 4
KSeF
The document gets its KSeF number.
- 5
UPO
The official receipt is attached to the invoice.
Retries and offline deadlines
Each new attempt comes later than the last, and after the twelfth failure the queue stops and tells your staff. For every invoice in the queue Flaem works out the late-upload deadline from the mode and the Polish working-day calendar.
Corrections and advance invoices
An invoice accepted by KSeF cannot be changed, so every mistake and refund is documented with a correcting invoice. You issue it from the panel, and it goes through the same queue as FA(3) of the KOR type. Advance invoices work the same way.
KSeF for resellers
A reseller invoices in their own name, so their invoices reach KSeF in their own tax ID context and with their own token, not through your account.
EU tax and currencies
VAT number checks in VIES, the OSS scheme for clients from other EU countries and NBP exchange rates for invoices in a foreign currency.

A store where one offer replaces ten similar ones
The client sees one offer, for example Minecraft servers, picks a resource plan in it and chooses the engine, game version and add-ons in the cart. They see the amount before paying, and after paying they manage the service in the same panel straight away.
- OfferFor example Minecraft servers or VPS
- PlansResources, price and billing periods
- Hardware tierFor example Premium, running only on selected nodes
- Choice in the cartGame engine and version, variant and add-ons
- OrderThe amount is shown before payment
Bundles and resource pools
You sell a game server, a domain and email together, cheaper than separately. You set the discount and how long it lasts by hand, and Flaem never discounts anything on its own.
Custom offers with a payment link
Your staff put together an offer for one client and send them a link to pay. An order can have custom fields and a start on a chosen date.
Abandoned orders and campaigns
A client who picked a plan and did not pay gets one reminder a few hours later with a link to the same order, and the purchase shows up in the statistics of your ad campaigns.
Coupons and referrals
Discount codes and promotions have a fixed place in the price, so the cart total matches the invoice. A referrer gets a code, a link and a QR code, and rewards go only to the wallet balance.
A first offer from a template
Ready Minecraft and CS2 offer templates are created as drafts with prices for you to confirm. Guests see prices without creating an account.
Resellers sell your servers under their own brand
A reseller buys services from you at a wholesale price and sells them to their own clients under their own name. They get a panel with their own logo, domain, price list, invoices and ticket desk, while you see their sales and settle their margin in the same system, on the same nodes.

Full white-label
The logo, accent colour, font, panel domain and email sender all belong to the reseller. The panel also works as a phone app with their brand's name and icon.
Margin pricing and payouts
Every sale and renewal adds the margin to the reseller's ledger, and a refund to the client reverses it with the same entry, negative. The reseller pays out what they have earned.
Invoices under their tax ID
The client buys from the reseller, and the reseller buys from you. Each transaction has its own invoice, numbering and path to KSeF, and you invoice the reseller once a month.
Figures from the ledger
Metrics are calculated on the server from the ledger, not in the browser from lists on screen, so the same number comes out on every screen, and you see the sales of every reseller.
Within the reseller's reach
- The client list and their activity
- Suspending and restoring accounts
- A read-only view of a client account
- Power, renewal, plan change and cancellation of services
- Messages to all of their clients
- Their own coupons and promotions
Out of reach
- Nodes and infrastructure
- Instance settings
- Other resellers' clients and plans
- Staff and administrator accounts


A ticket with the client's services and invoices alongside, and the status page on a phone.
Tickets, chat and a status page without a separate help desk
The client writes from the panel, by email or in the chat, and your staff answer from the panel or straight from Discord. The client's services and invoices sit next to the conversation, so nobody switches between systems.
- Tickets and live chat
- Before the client sends a ticket, the panel suggests articles that match what they are typing. Chats wait in a queue, and when nobody answers, the chat turns into a ticket.
- Translation and an AI first line
- The client writes in Czech, and your staff read and answer in Polish. The translation runs on a model on your side, so ticket contents stay with you.
- A knowledge base in 5 languages
- You start with 15 articles on 5 shelves, each in Polish, English, German, Czech and Ukrainian, with full-text search.
- Viewing the account as the client
- Staff see the panel exactly as the client does, for 30 minutes at most, read-only and logged, and the client is told about it.
A public status page
It runs on your installation, under your domain. It shows 7 ready components, their live state, a 90-day uptime bar and planned maintenance, and visitors subscribe to updates by email.
After every ticket and chat the client leaves a rating from 1 to 5, and you see the statistics of every agent.
Notifications that land where someone will see them
Invoices, outages, approaching limits and ticket replies go out in the panel, by email, SMS, push, Telegram and Discord. The client picks channels in their preferences, and the delivery log shows you what reached whom.
- In the panelClients and staff
- EmailThrough your own SMTP server
- SMSTwilio, SMSAPI or SerwerSMS
- PushBrowser, APNs and FCM
- TelegramFor your clients and for you
- DiscordClient and team channels
On-call with escalation
An alarm goes first to whoever is on call according to the rota. If they do not acknowledge it in the set time, it moves to the next person on the ladder, rung by rung, until someone takes it.
- 1The person on call
- 2The next person on the rota
- 3The next rung, until someone takes the alarm

The operator on-call view in the phone app, with notifications from different channels.
Templates with your logo. Messages in 5 languages, in the colours of your brand or the reseller's, and every event can also fire a webhook to your own system.
Targeted announcements. To everyone or only to the owners of selected services. Before publishing, the panel shows how many people the announcement will reach.
Early warnings. Flaem warns you when a node is running out of disk or memory, the installation has no fresh backup, a node agent is out of date or a clock has drifted.
Per-second statistics with the real peaks kept
Flaem measures every service and every node each second and keeps the average, minimum, maximum and percentiles for every period, so a short spike does not vanish into an average. The client sees charts of their service, and you also see nodes, hardware, the network and who is taking resources from whom.
- p50 to p99
- for any window, with a p5 to p95 band under the average
- 5s
- peak network and disk speed kept for every period
- 30days
- of charts for every service, in one grid
- 3windows
- that hurt least for maintenance, from the node's weekly map

Who disturbs whom
In the minutes when steal, pressure or disk latency rise on a node, the panel shows the services that took the most at that time, with their share in percent.
A typical week and a black box
A chart is compared with what is normal for that service. Restarts, crashes, backups and attacks are markers on the chart, and when something happens Flaem freezes the detailed data from just before it.
Games, sites and hardware
TPS, MSPT, players and entities next to the game server's resources, PHP and JavaScript performance for sites, node hardware health and sFlow and NetFlow traffic analysis.
Accounts, your team and the money, protected
Flaem protects client accounts with two-step verification and passkeys, your team with permissions for every action and a two-person rule, the money with fraud screening and the network with abuse detection.
- Signing in
- A password with a second step, a passkey with no password, or a Google, GitHub, Discord, Steam or any OpenID Connect account. The account recovery code treats every use as a possible takeover.
- Permissions for every action
- You build roles from single actions, so support can read invoices without issuing refunds. Two-step verification is mandatory for your team.
- Two-person rule and audit
- Deleting a service, deleting a node and moving money wait for a second authorised person to approve. Every staff action goes into the audit log: who, what, when, from where and on whom.
- Abuse and nodes
- Flaem notices miners, spam, scanning and attacks leaving client machines and responds step by step. The channel between the control plane and the nodes is encrypted, and every release is signed.

Fraud screening before a service starts
- AcceptThe order goes ahead as usual.
- ReviewThe sale is recorded, only the delivery waits.
- RejectThe buyer gets a refusal code, only your team knows why.

- Two control planes behind a shared address and a backup of the whole installation on a schedule
- Services moved between nodes with downtime counted in seconds
- Every part of the installation checked every minute
- An overdue licence payment never switches off your clients' services
From an empty machine to the first sale, without SSH every day
The panel, the database and your clients' data sit on your own machines. You run the installation, nodes, updates and failures from the panel, and every risky change has a way back ready.
- 1
One-command install
The installer asks for the address, HTTPS, the licence key and the administrator, and does the rest on its own.
- 2
A 14-step wizard
From the licence and seller details to a published offer. Eight of the steps are enough for the first sale.
- 3
Nodes with a command from the panel
The panel prepares the command, and the installer checks the machine from inside and outside before it writes anything.
- 4
Updates that roll back
You start them in a window you choose. If the new version on a node does not come up, the node returns to the previous one without you.
- 5
A node failure
The panel waits as long as you set, notifies whoever is on call, then spreads the services over the remaining nodes with one command. Nothing moves by itself in the middle of the night.
Flaem driven from code, and your billing can stay
Clients and operators drive Flaem through a public API with keys and scopes. A key states exactly what it may do, and the same rules apply to Terraform, the command line tool and an AI assistant.
You drive it from
- REST API v1 described in OpenAPI 3.1
- The TypeScript client
- Terraform
- The command line
- An AI assistant over MCP
- WHMCS, Blesta, HostBill and Paymenter through the bridge
Scopes, rate limits and a log of every call
Flaem answers with
- 44 webhook event types
- A signature on every event
- Six attempts at growing intervals
- A delivery log
An AI assistant over MCP
You connect Claude or another MCP-compatible assistant to your own installation and ask it about nodes, services, clients, invoices and tickets. It has 23 tools and can do exactly as much as its key allows.
The billing bridge
If you stay with WHMCS, Blesta, HostBill or Paymenter, the billing system keeps owning the client and the money, while Flaem creates, suspends and resizes the servers.
The TypeScript client
The path, method and parameters are checked at compile time, so a call to an API endpoint that does not exist simply does not compile.

Moving from your current panel starts with a dry run
You move to Flaem from billing systems, game panels, VPS panels and web hosting panels. Servers and machines that can stay on their hardware are taken over in place, and nothing is created in the new system until you approve the report.
WHMCS- Pterodactyl
Pelican
Convoy
Virtualizor
SolusVM
VirtFusion
VMware ESXi
cPanel
DirectAdmin

- 1
Read
Flaem reads the data from the old system through its API, its database or an account backup.
- 2
Dry run report
You see what will be created, what will change and what cannot be moved.
You approve the report
Until then, nothing changes.
- 4
Import
Accounts, services and machines appear in Flaem.
- 5
Pricing
Moved plans wait inactive, at a price of 0, until you set prices.
No invoices by mistake
Client services work from the first moment, but Flaem does not bill or suspend them until you price them. Nobody gets an invoice or a block by accident during the move.
Nodes stay where they are
When a server already sits on hardware Flaem supports, only the panel changes. You take over Pterodactyl Wings nodes with no downtime for players, and a move is needed only when a machine has to go to Proxmox VE.
We will show you any of these modules on your own servers.
Tell us what you sell today and on which panel. In the demo we go through the modules you care about using your own offer, then work out the licence from the price list.