Flaem

A Proxmox VPS panel that sells and bills out of the box

Your client buys a virtual server in your store, pays and a moment later has a running machine with its console, backups and networking in the panel. Flaem drives Proxmox VE 8 and 9, so you sell KVM VPS, LXC containers and VDS from one place, with invoices and renewals included.

Flaem: store, billing and client panel
Proxmox VE 8 or 9 node
KVM VPS

A full virtual machine with its own kernel: Linux from the base image, Windows from your template or the client's own image.

LXC containers

Lighter than a virtual machine and handled like a VPS in the panel: power, resources, console and backups.

VDS

CPU cores reserved for one client. It only lands on nodes you mark for VDS.

Cores shared by VPS and containers
Cores reserved for VDS
One Proxmox VE node, three products in your store.
01Ordering

VPS ordering with a configurator: OS, SSH keys, password and hostname

The client sets up the machine in the same step in which they pick the plan. They pay, see the "Ready!" screen and log in to the server, and your team does nothing in between.

What the client picks at checkout

Operating system
A base image with Debian, Ubuntu, Rocky Linux or AlmaLinux. On top of that your own templates, Windows included, and the client's own system image.
SSH keys
Pasted at checkout and added later in the panel without reinstalling the system.
Root password
Set at purchase and changed in the panel at any time.
Hostname
Entered in the configurator and changed later from the panel.
Startup data
A custom cloud-init script for clients who want to automate the machine's first boot.
Ordering a VPS in the store: plan, system, SSH key, location and add-ons with a live price

Base images

  • Debian 13
  • Debian 12
  • Ubuntu 24.04
  • Ubuntu 22.04
  • Rocky Linux 9
  • AlmaLinux 9

Plus your own templates, Windows included, and the client's own system image.

Ready machines on standby

The node keeps prepared machines for your most popular plans, so a new order starts in seconds instead of minutes. You decide how many to keep, so they do not hold space for nothing.

Install from scratchminutes
Machine from standbyseconds
1Plan and configuration
2Payment
3The "Ready!" screen
4Logging in to the machine

Once paid, the VPS is created on the node by itself and the client goes straight to their machine in the panel.

02Console

Browser console for VPS, ISO images and rescue mode

When a client cuts off their own network or breaks the configuration, they still see their machine's screen in the browser and fix it themselves, without opening a ticket with you.

Client's browser
Flaem panel
Proxmox node
Machine screen and serial port
Machine networkdown

The console connects through the node, not through the machine's network, so it keeps working when that network is down.

Graphical console

The machine's screen, as if a monitor were plugged into the server. Handy for operating system installers and for Windows.

Serial terminal

The system's text console, convenient for Linux without a desktop environment.

Machine management in the panel

  • Power: start, restart and shutdown
  • System reinstall
  • New root password
  • SSH key added without a reinstall
  • Hostname change
  • Custom cloud-init startup data

ISO image

The client picks an image from your catalogue and sets the boot order, for example to run an operating system installer.

Boot order
  1. 1Machine disk
  2. 2Image from the catalogue

Rescue mode

The machine boots a rescue system with the client's disk attached. The client fixes the files and goes back to a normal boot.

Boot order
  1. 1Client disk
  2. 2Rescue system

LXC containers get power control, resource changes, console, reinstall, backups and password changes in the panel.

03Snapshots and backups

Snapshots, backups in a second location and moves in seconds

Before a risky change the client takes a snapshot and goes back to it if something breaks. Machine backups also live off the node, and when you need to free a node you move the VPS with downtime counted in seconds.

Main location
Node
Snapshots
Client VPS
Another node
Backup storage off the node
Machine backup
Second location
Standby VPS copy
Client VPS
04Networking

VPS networking: firewall, rDNS, extra IP addresses and IPv4-less VPS

Traffic to the machine passes several layers of protection, and the client sets their part in the panel, without writing rules inside the system.

Traffic from the internet
Before your network

DDoS protection at your provider

Path.net, OVH, Cloudflare Magic Transit or NeoProtect. The client sees reports of attacks on their addresses in the panel.

On the node

Kernel traffic filter

Drops junk traffic before it reaches the machines and rate-limits packets per address. You switch it on and off for each node.

On the machine

VPS firewall

Traffic rules the client sets for their machine in the panel, without logging in to the system.

Addresses

Extra IPs and rDNS

The client buys more addresses at your price and within your limit. The node configures them inside the machine itself, and when the system does not allow it the client gets ready commands. Addresses survive a reinstall and reverse DNS is set per address.

Client VPS

VPS without IPv4

You sell a VPS without its own IPv4 address as a cart option of the same plan. Everything else about the machine stays the same.

Static client addresses

You can pin IP addresses to the client account, not just to one of their machines.

05Monitoring

VPS monitoring: graphs, alerts, transfer allowance and insight without an agent

The client sees what their machine uses and gets an alert by their own rules before they run out of resources.

Client alerts

The client sets their own alert rules for the machine, and reports of DDoS attacks on their addresses land in the same panel.

VPS monitoring in the client panel: CPU, memory, disk and network every second, percentiles, events on the chart and an active alert

Graphs in the client panel

Alert threshold set by the client

Transfer allowance

The plan includes transfer, and the panel adds any overage at renewal.

Included in the planOverage added at renewal

VPS insight without an agent

For Windows, ISO installs and third-party images that have no Flaem agent inside, the VPS overview still shows:

  • Operating system
  • Kernel
  • Addresses
  • Disk usage
  • Logged-in users
06Apps

One-click apps on VPS, priced in every plan

The client picks an app from the list and Flaem installs it on their machine. You decide what the app costs in each plan.

The client clicks WordPress and has it on their VPS.

The signed catalogue holds 13 recipes, these eight among them.

Signed catalogue

The install runs from a signed catalogue of recipes, not from a script pasted from the internet.

Price per plan

You set the price of every app separately in every VPS plan.

After the install

The agent inside the VPS updates the app, backs it up and opens its admin panel without exposing a port.

07Billing

VPS billing: plan changes priced to the second

The client moves to a bigger or smaller plan on any day of the period and the panel prices the difference for the time that is left, to the second. The invoice and the renewal come from the same system.

Plan change
Period startRenewal
Current plan, already paidDifference for the time left

What you set in a VPS plan

SettingRangeHow it works
Billing period1 to 3650 daysAny period length in days, each with its own discount.
Trialup to 2160 hoursA trial counted in hours before the client pays for the first period.
Transferat renewalUsage above the plan's transfer is added to the next period.
Extra IP addressesyour price and limitThe client buys addresses in the panel within the limits you set.
Catalogue appsprice per planThe price of an install from the catalogue is set separately in every plan.
08Operator

On the operator side: offers, nodes and memory under control

You decide what you sell and on what hardware, and the node watches the things you would normally check by logging in to every machine.

Flaem operator dashboard: sales and MRR, live nodes and the issues waiting for a person

Nodes

A node in one command

The panel generates the install command. The installer checks the network first and then sets up the node in Proxmox mode, which runs VPS, LXC containers, game servers and websites.

Node networking with rollback

You change node networking in the panel and see the diff before saving. If the node does not confirm it can reach the control plane after the change, it rolls back to the previous configuration.

Node updates

Each node shows pending packages, the kernel and whether a reboot is needed. You plan a window, clients get an announcement, you move machines before the reboot and you get a report at the end.

Node rebuild

After a hardware failure you point to a new machine and Flaem installs everything on it and restores services from backups, with the same addresses and ports.

Offers and hardware

Offers from a template

A ready VPS template creates a draft offer with plans and prices to confirm. Variants such as VDS or a VPS without IPv4 are cart options of the same offer, not separate products.

Hardware and disks per product

On one node each product can use different hardware and different disks, and each plan has its own virtual hardware profile.

Templates with a trial boot

A refreshed OS template boots on trial first, and clients only get it once the machine comes up.

Local package mirror

Installs and updates on client VPS pull packages from a mirror in your location, faster and without outside transfer. You enable it per location.

Resources and abuse

Node memory

You enable identical memory page merging on the node and set ballooning per plan. You see how much you really save and how close the node is to running out. When the node stops a machine for lack of memory, the panel records the cause and you get a single alert.

Outgoing attacks

For every machine the node counts packets per second, the UDP share and the number of targets, and detects outgoing floods and SSH or RDP password guessing. The signal goes into abuse cases.

Addresses without conflicts

The node assigns guest addresses even without cloud-init and makes sure no two machines get the same address.

Terraform and a command line tool

Clients who prefer code to clicking create and change VPS through the Terraform provider or the command line tool, on the public API with scoped keys.

API, Terraform and CLI: scoped keys and webhooks
09Comparison

Flaem, Virtualizor, VirtFusion and Convoy: VPS panels side by side

All four run virtual machines. They differ in what they include beyond the VPS itself and in how they charge for the licence.

CriterionFlaemVirtualizorVirtFusionConvoy
What it isA VPS panel together with a store, billing and the panel for game servers, websites and dedicated serversA VPS panel with built-in hourly billing for machinesA KVM virtual machine panelA VPS panel on Proxmox
VirtualisationKVM and LXC on Proxmox VE 8 and 9KVM, Xen, OpenVZ, LXC, Proxmox and moreKVMProxmox
Billing and invoicesBuilt in: renewals, wallet, invoices and Polish e-invoicingHourly, for virtual machinesA separate system, for example WHMCS, Blesta or HostBillNo billing of its own, Paymenter has an extension for it
Licence and vendor priceFrom $10 a month for 3 nodes, $4 per further node, VPS $10, LXC $6, both $12, on every node at once, no client capUSD 9 per month (Premium) or USD 18 per month (Professional) per node, unlimited VPSUSD 18 per month per hypervisor with unlimited machines, non-commercial USD 50 per yearUSD 6 per month per node for commercial use, free for personal use
Moving to FlaemEvery import starts with a preview of what will move and what will notMachines in Proxmox mode adopted without a reboot, plain KVM moved in a scheduled windowMachines, plans and addresses, disks moved in a window with a pre-copy and conversionMachines adopted without a reboot, with the same VMID

Prices exclude tax, taken from the vendors' own sites.

One system instead of a panel, billing and the modules between them

The store, billing, invoices with KSeF and the panel for every service run in one Flaem installation. Flaem adopts machines from Convoy and from Virtualizor in Proxmox mode without a reboot, and from VMware ESXi, SolusVM and VirtFusion you move to Proxmox VE with seconds of downtime.

10Questions

Questions about the Proxmox VPS panel

Requirements, system images, billing and moving over from another VPS panel.

Yes. VPS and LXC containers run on Proxmox VE 8 or 9. A node without Proxmox runs game servers and websites.

Yes. Besides the base image and your templates the client can use their own system image, and they pick ISO images from your catalogue.

The graphical console and the serial terminal in the browser. The console connects through the node, not through the machine's network, so it still works.

To the second. The panel prices the difference between plans for the time left until renewal, both when the client moves up and when they move down.

Yes, as a cart option of the same plan. The client does not get their own IPv4 address and the rest of the machine works as usual.

The Convoy import adopts machines without a reboot and keeps the same VMID. From Virtualizor, machines in Proxmox mode are adopted in place and plain KVM machines are moved to a Proxmox node in a scheduled window. Every import starts with a preview of what will move and what will not.

Yes. They get a Terraform provider, a command line tool and a public API with scoped keys.

No. The agent inside the VPS lets them install apps, attach a domain with HTTPS and update the system from the panel, without a terminal.

See the VPS panel on your own Proxmox

Tell us how many Proxmox nodes you run and which panel you are moving from. In the demo we will walk through ordering, the console and billing, then work out the licence from the price list.