Outbound enrollment
The agent reaches your configured HTTPS API from the VPS. You do not need to provide cloud credentials or SSH private keys to the dashboard.
Server management
Your server. A clearer view of its health.
Connect an existing Linux VPS and review what its agent actually reports: heartbeat freshness, system details, resource measurements, and detected FFmpeg availability.
Available
Start with a clear workflow.
- 1Register your server with a name; provider and public host are optional.
- 2Install the agent on the VPS using its short-lived setup file.
- 3Review the first heartbeat and detected system details.
In your workspace
The details that make a difference.
Know what each part does before adding it to your publishing routine.
Freshness is visible
Review the last heartbeat separately from measurement timestamps. Missing measurements stay unavailable, and old metrics are marked stale instead of implying current health.
Persistent service and access control
The source-build installer configures a dedicated systemd service. Setup credentials are exchanged once for a server-specific credential, with rotation and revocation controls.
Current capability
What to expect today.
A heartbeat proves the agent reported in; it does not prove streaming readiness. Refresh status reloads recorded information rather than pinging your VPS. Remote setup needs an API address the VPS can reach over HTTPS.
More product questionsPut it into practice.
Follow a focused guide, prepare a short test, and review the signals that matter before committing to a longer broadcast.
Take the next step
Make room for your next broadcast.
Bring your server, source video, and destinations into one workspace. Start with a short test and grow from there.