Dashboard tour
Every part of the OSS Panel dashboard — navigation, server identity, live metrics, 24-hour history and processes.
The dashboard is the panel's home screen: live health and resource usage for this server, plus whatever needs your attention.
1. The sidebar
Everything the panel does hangs off the left sidebar.
Server
| Dashboard | This screen. |
| Applications | Your sites and services — create, deploy and manage them. |
| Databases | Databases, database users and remote access. |
| System Users | The Linux accounts that own sites and can log in over SSH or SFTP. |
| Firewall | ufw rules. |
| Cron Jobs | Scheduled commands. |
| Fail2ban | Jails and banned addresses. |
| System Logs | Web server, PHP and system logs. |
| Services | Start, stop and restart what runs on the box. |
| PHP / Node.js | Installed versions, and installing more. |
| Docker | Containers, images and volumes. |
| Settings | Server, security, performance and maintenance settings. |
| Disk Cleaner | Reclaim space. |
| Backups | Schedules, history and restores. |
| Activity Log | Who did what, and when. |
| Server Sync | Reconcile the panel's record with the server's real state. |
Integrations — Git providers and object Storage for backups.
The button at the top of the content area collapses the sidebar to icons. Across the top-right of every page: a language selector, a light/dark theme toggle, and your user menu.
2. Banners
Two things appear above the page when they apply.
A restart notice — "This server needs a restart to finish applying an installed update." Kernel and library updates need a reboot to take effect. Restart now reboots the server; More options shows what is waiting and lets you schedule it instead. The panel will keep telling you until the server is restarted.
A setup prompt — "Finish setting up your server", with the number of recommended components still missing, and a Finish setup link back to the setup checklist. Dismiss it with the × once you have decided you do not want them.
3. Your first application
Until the server has an application, the dashboard explains the shape of creating one: choose a type, add essentials (domain, owner, and only the settings that type needs), then track provisioning step by step until the application is ready. Create application starts that flow.
Once applications exist, this card is replaced by their live status.
4. The server strip
Underneath: the server's name and OS, how long it has been up, its timezone, its public IP (with a copy button), the processor and the kernel.
Below that, runtimes — the versions actually installed, such as
php 8.4.26, node 24.21.0, redis 7.0.15, nginx 1.24.0 — and a service
health badge. All 4 services running means the panel's own stack is
healthy; anything else is a link to Services.
5. Right now
Five tiles, updating live — the Live badge and a timestamp show the feed is current:
| Tile | Shows |
|---|---|
| CPU | Percentage in use, and the core count. |
| Memory | Percentage and absolute use, with free memory underneath. |
| Swap | The same for swap. On a healthy server this stays at 0%. |
| Disk | Use and free space on the root filesystem. |
| Load avg | Current load against the core count, with the 5-minute figure. |
Each carries a status word — Normal until it is not.
Beneath them, Network I/O and Disk I/O chart throughput as it happens, with current in/out and read/write rates, and IOPS for the disk. Both start empty on a freshly loaded page and fill in as samples arrive over the next few seconds.
6. Last 24 hours
Server load plots queued work against how many cores the server has, at 5- and 15-minute averages. The dashed line marks the core count: sustained time above it means work is waiting for CPU.
Resource usage plots CPU, memory and disk as percentages over the same window — the view that tells you whether a problem is a spike or a trend.
7. Processes
The busiest processes right now — not every process on the server. Each row gives the command, its PID, the user it runs as, and CPU and memory share. The button at the end of a row stops that process; View all processes expands to the full list.
Stopping a process is immediate
There is no undo. Stopping a php-fpm or web server process affects live
sites. Prefer Services for anything you mean to restart cleanly.