GLWS · Hosting panels
A web-hosting control panel for organising sites and related server services.
Common uses of CyberPanel.
Install a hosting panel on a suitable clean system and check the supported distribution before running its installer.
Planning examples, not official minimum requirements.
Hosting panels
Check the current supported operating systems, deployment methods, dependencies and licence terms. What you need depends on your workload, not just the application's name.
Large datasets and busy workloads can need far more memory, storage or different hardware. Any external API or service subscriptions are separate.
Read the CyberPanel documentation ↗ (opens in a new tab)Advice specific to this application.
Check the requirements of the websites you intend to run, including language runtimes, databases and scheduled work. A hosting panel brings several services onto one machine, so allow for their combined resource use and maintenance rather than only the website files.
Keep copies of website files and consistent database exports. Record DNS and certificate requirements separately. Test a site on the destination before moving traffic, and verify the application behaves correctly before removing the previous environment.
Linux guides that help with this setup.
Read the basic resource indicators on Ubuntu 24.04 LTS and AlmaLinux 9, then identify where to investigate a slowdown.
Read guide →Allow the SSH port you actually use before enabling UFW or firewalld, then test access from another terminal.
Read guide →Create a compressed archive of your own project, verify it, and extract a test copy without overwriting the original files.
Read guide →Four steps that make the environment easier to maintain.
Read the publisher's instructions and choose a supported installation method.
Protect the dashboard, credentials and network endpoints before you expose any service.
Work out where the application keeps its state and store it separately from replaceable runtime files.
Back up the data and configuration, then check that you can restore them.
Run through it before and after you install.
$ application-checklist --name cyberpanel
[ ] Supported deployment method
[ ] Authentication and access restrictions
[ ] Independent data backup
[ ] Updates and restoration tested
root@glws:~#
Quick answers before you choose resources.
No. The configurator only saves your application preference. It does not connect to any infrastructure or run an installer.
Use the planning example as a starting point only. Check the publisher's requirements and measure the whole stack under a realistic workload.
You do. Self-hosted applications need updates, configuration and recovery planning from the operator. The publisher's documentation describes supported maintenance.
The knowledge base covers Linux access, packages, services, firewalls and backups.
Other tools you might run alongside or instead.
Website, email, DNS and database management in a hosting dashboard.
Explore application →Manage common Linux administration tasks through a modular web interface.
Explore application →A server control panel for running and managing web applications.
Explore application →A self-hosted assistant for connecting model-powered tasks with tools and messaging.
Explore application →