Sign in
Your VPS fleet, activity and resource history.
Your VPS fleet
Loading your servers…
Add a VPS
Enter its address, then enrol the read-only monitoring agent once.
Connections and connected IPs are not unique viewers. Exact online customer counts come from 8K. Network totals include SSH and backups.
Servers
| Server | Connections | CPU | Memory | Disk | Outgoing | Month outgoing | Status | Actions |
|---|
Add your first VPS to start collecting resource history.
Resource history
Show recent measurements
| Time | CPU % | Memory % | Incoming Mbps | Outgoing Mbps | Connections |
|---|
Edit planning limits
Finish monitoring setup
Download the node bundle, upload it to this VPS using your trusted SSH connection and unzip it. Open that folder and run sudo bash install-node.sh. The installer prints a public enrolment code.
No VPS root password is stored in this dashboard. Monitoring uses a restricted key and a pinned server host key.
Plan for your peak
Model bandwidth before choosing hosting. This is a scenario, not a load test.
- Outgoing video rate
- —
- Capacity with extra room
- —
- Incoming rate
- —
- 30-day outgoing transfer
- —
Port values are advertised ceilings, not guaranteed throughput. Independent VPS links may share a provider uplink. Extra IP addresses on the same VPS share its CPU, RAM and network link.
Choose the resource that is filling up
For this relay, network capacity usually matters first. Add CPU or RAM when measured usage stays high. Use a small number of independently provisioned high-bandwidth relays for a large audience, with a tested way to move viewers if one fails.
There is no automatic customer migration or purchase in this dashboard. Confirm usable bandwidth, transfer terms and your actual stream bitrate before ordering.