Server
Host vitals and disk usage for the VPS every client site shares — from dummy data.
Public address
78.141.223.14
- Dokploy
- v0.24.1
- Capacity
- 4 cores · 16.0 GB
- Root disk
- 100 GB
- Hostname · OS · kernel
- not collected
Host vitals
The machine every client site shares
CPU34%
34% across 4 cores
Memory38%
6.1 GB of 16.0 GB
Disk61%
61.0 GB of 100 GB
Uptime
41d 6h
since last reboot
Load average
1.8 · 1.4 · 1.1
1m · 5m · 15m
Snapshots
3
newest 6h old
Malware scan
Clean
last run 6h ago
Firewall
6 rules
active, default deny
Disk usage
35.7 GB used · 7.7 GB reclaimable
Docker images · 8.4 GBBuild cache · 4.2 GBVolumes · 22.0 GBContainers · 1.1 GB
Unused imagesImages no container references — The next deploy re-pulls whatever it needs.3.1 GB
Build cacheCached build layers not in use — Safe — builds repopulate it. The next build will be slower.4.2 GB
Stopped containersWritable layers of exited containers — Dokploy recreates them on the next deploy.410 MB
Everything aboveUnused images, stopped containers and build cache — Volumes are never touched — your databases are safe.7.7 GB
Busiest services
Ranked by CPU · every service with a live metrics sample
| Service | Project | Status | CPU | Memory | Network | Trend |
|---|---|---|---|---|---|---|
| worker | Client B | Deploying | 74% | 340 MB | 6.0 KB/s | |
| panel · api | Xyte | Degraded | 61% | 780 MB | 210 KB/s | |
| web | Xyte | Running | 38% | 512 MB | 84.0 KB/s | |
| api | Client D | Running | 29% | 410 MB | 31.0 KB/s | |
| postgres | Xyte | Running | 22% | 1.4 GB | 42.0 KB/s | |
| web | Client B | Running | 14% | 260 MB | 18.0 KB/s | |
| redis | Client C | Running | 6% | 96.0 MB | 4.0 KB/s | |
| web | Client C | Stopped | 0% | 0 B | 0 B/s |
Cleanup here only ever touches images, build cache and stopped containers. Volumes — where every database lives — are never in scope for these buttons.