Web hosting and app hosting in the same panel as your game servers and VPS
Your client buys a web hosting plan in your store and runs several sites on it: WordPress, a PrestaShop store or an app built from a git repository. Every site runs in its own container on your node, with a domain, a certificate, a database and backups, and billing goes through the same wallet as every other service.
Four environments and 20 ready application stacks
An environment is what a site runs on: static files, PHP, Node.js or Python. A stack is a ready application on top of an environment that the client sets up with a single choice. You import stacks into Flaem and enable them in the plans that should offer them.
PHP
Content management systems, stores, forums, wikis and tools, the things that usually live on classic web hosting.
- WordPress
- Joomla
- Drupal
- PrestaShop
- Grav
- Laravel
- Nextcloud
- MediaWiki
- DokuWiki
- phpBB
- Matomo
- FreshRSS
- Kanboard
- phpMyAdmin
- PHP-FPM
Node.js
JavaScript applications with their own server.
- Ghost
- Node.js
Python
Python web applications on ASGI or WSGI.
- Python ASGI
- Python WSGI
Static site
HTML, CSS and files without server-side code.
- Static site
How a stack reaches your store
- ImportYou import a ready stack into Flaem.
- EnableYou enable it in the web hosting plans that should offer it.
- Client choiceThe client picks it when creating a new site.
WordPress with an installer and updates protected by a restore point
Clients set up WordPress without a manual install, and you can sell a plan with the application ready to go. Updates stop being a gamble: right before each one, Flaem saves a restore point of the site that the client can return to if something stops working.
Installer
The client picks WordPress when creating a site and skips the manual installation.
Plans with the app included
You sell a web hosting plan with WordPress ready right after purchase.
Password shown once
The site owner sees the administrator password only once, right after installation.
Restore point
The state of the site saved right before the update.
Update
A new WordPress version installs on the client site.
Something breaks
The client notices a problem, for example with a plugin.
Domain, certificate, traffic rules and caching set up in the panel
Before a visitor request reaches the site, it passes through several layers. The client sees each of them in the panel and sets it up in a form, not in server configuration files.
WAF and CDN
An application firewall and a network of servers that deliver the site from cache closer to the visitor. Run by you as the operator or through Cloudflare.
Domain and certificate
The client attaches a domain to the site, the certificate is issued automatically and its status shows in the panel.
Traffic rules
Redirects and other rules for the site addresses set up visually, together with certificates.
Page cache
Ready pages kept in memory, so repeat visits do not run the code from scratch.
Site in a container
The site code runs in its own container, in the environment the client chose.
PHP 8.2, 8.3 and 8.4, environment variables and settings within plan limits
The client switches the PHP version for each site separately and changes six PHP settings, but only within the range you allowed in the plan. On top of that come up to 50 environment variables, including secrets that cannot be read back from the panel once saved.
Dangerous PHP directives are blocked and cannot be set from the panel.
Environment variables
Up to 50 variables per site. A secret is write-only: the panel does not show it, yet the application still receives it.
Each site also gets its own
- Cron
- Scheduled jobs set up in a form.
- Logs
- Site logs in the panel, with no hunting for them on the server.
- Files and SFTP
- A file manager, SFTP access, a file editor similar to VS Code and a terminal inside the site container.
- Selected folders
- Someone helping with the site gets access only to the folders they need.
- Databases
- Site databases with a web panel for browsing data and support for large dumps.
Applications from a git repository, built inside the client resources
The client points to a repository, and Flaem builds the application from it and runs it in the client plan. The build uses the resources the client pays for, so it does not slow down other services on the node.
- App copy
- App copy
- App copy
Built where the client pays
Compiling and installing dependencies count towards the client plan, not the spare resources of your node.
Like any other site
The finished application gets a domain, a certificate, logs and backups, just like a site from a ready stack.
Load balancer as an app
When one copy of the application is not enough, the client adds a load balancer as another app, and it spreads traffic across several copies.
Staging copy of a site, a temporary address and file change history
A change that could break something gets tested on a copy of the site first. The copy gets a temporary address, so it works without attaching a domain, and every file change on the site lands in a history it can be undone from.
- 1Site copyA single action creates a copy of the site for testing.
- 2Changes on the copyA new plugin, theme or PHP version tested with no risk to visitors.
- 3Site keeps runningVisitors see the working site on its domain the whole time.
File change history
Every file change has its own entry. The client rolls a single file back to an earlier version without restoring a whole backup.
- Changed template fileUndone
- New plugin fileUndo
- Deleted image fileUndo
Backups
Incremental backups together with databases. A backup can restore the whole site or just selected files.
Visitor statistics from logs and site, PHP and JavaScript performance
The client sees site traffic without adding a tracking script, because visitor statistics are built from server logs. When the site slows down, the panel shows where the time goes and explains why it is slow.
Where page load time goes
- Network and cache
- PHP
- Database
- JavaScript in the browser
Schematic. Segment length shows its share of page load time.
Visits from logs
Statistics are built on the server side, so the site needs no tracking script.
Real peaks
Per-second data and percentiles show peaks that an hourly average hides.
A typical week
Period comparisons and the typical week of a site tell a normal Monday apart from a problem.
Events on charts
An update, a plan change or a restart shown on the same chart as traffic and resources.
Database statistics
Database usage of the site next to PHP and memory usage.
Sites on the same nodes as games, with games served first
Web hosting needs no separate servers and no separate panel. A node in container mode runs games and sites side by side, and when resources run short, game servers come first, because players feel every delay right away.
One node, games and sites
Normal trafficSchematic of how node resources are shared.
Moving over from cPanel and DirectAdmin
Importing from an account backup moves sites with their files, domains and DNS zones, mailboxes without their messages, mail forwarders and MySQL databases. You get a dry-run report first.
Container mode or Proxmox
The node installer sets up container mode for games and sites only, or Proxmox mode, which also runs VPS and LXC containers.
Image versions per node
You decide which environment image versions run on each node.
Insight against abuse
You see the usage of every site and who is getting in whose way, so you find a site that takes resources from others without guessing.
Disk usage map
One map shows the space taken by every service on the node, backups included.
Ready offer template
A web hosting offer starts from a template as a draft with prices to confirm.
How other systems sell web hosting
Billing systems sell website hosting through a separate panel that you need to run alongside and connect with a module. In Flaem, sites run on your nodes next to games, VPS and email. Based on the vendors' own websites.
WHMCSThrough hosting panel modules. The modules included with WHMCS Cloud cover cPanel, Plesk and DirectAdmin.WHMCS Cloud: included modules
HostBillThrough integrations with cPanel, Plesk and DirectAdmin.HostBill: pricing
PaymenterThrough server extensions; the repository includes cPanel, DirectAdmin, Enhance and Plesk among others.Paymenter: repository- PterodactylGame servers in Docker containers only.pterodactyl.io
Questions about web hosting in Flaem
The most common questions from operators who want to sell websites next to games and VPS.
Yes. A web hosting plan holds several sites, and each runs in its own container with its own environment and its own share of the plan resources. You set the plan resources.
PHP 8.2, 8.3 and 8.4. The client switches the version for each site separately and changes six PHP settings within the range you allowed in the plan.
No. Once the domain points to the node, the certificate for the site is issued automatically and the client sees its status in the panel.
Right before the update, Flaem saves a restore point of the site. If something does not work afterwards, the client goes back to the state from before the update.
Yes. You protect and speed up sites with your own WAF and CDN or through Cloudflare, and client domains can keep their DNS zones in Cloudflare.
The build runs inside the client plan resources, so it uses what the client pays for, not the spare resources of the node.
Yes. A node in container mode runs games and sites side by side, and when resources run short, games come first.
Yes. The import works on an account backup and moves sites, domains with DNS zones, mailboxes without their messages, mail forwarders and MySQL databases. You get a dry-run report before anything is applied.
Related pages
- Email, domains and DNS for web hosting clients
- Storefront and offers: web plans, add-ons and coupons
- Migrating from cPanel and DirectAdmin to Flaem
- Server management without SSH: apps with a domain and HTTPS on VPS
- Hosting billing software: renewals and wallet
- Flaem licence pricing: per node, no client limit
See web hosting on your own node
In the demo we will show a web hosting purchase, a WordPress installation, attaching a domain with a certificate and rolling back to a restore point. Tell us which sites you sell today.