RunoryAgentless Dashboard
Read server health over SSH without installing a resident Runory monitoring agent.
SERVER OPERATIONS AND DEPLOYMENT
From server health to a change you can track.
Review resources, services and logs in the same server context. Operate Docker, PM2 and Nginx, use Incident Packs for common failures, then deploy around Git, environment variables, SSL, backups and Cron. Multi-server writes use Fleet: sequential execution, pause for review and exact approval.
01
HealthCPU / memory / disk
02
DiagnoseFive Incident Packs
03
ReleaseGit + Fleet
01
Core capabilities
Incident Packs
Website, Nginx, Docker, Disk Full and Linux Service packs connect evidence, root cause and repair plans into a reviewable flow.
Deployment and Fleet history
Track stages, per-target status and results. Production writes default to sequential execution with Pause for Review.
02
In detail
01
Understand the server before acting
Dashboard brings CPU, memory, disk and service status together. Logs keep evidence near the target server, while Docker, PM2 and Nginx panels place frequent operations in predictable locations.
These features build on the established SSH connection and ServerSession. React presents interactions; Rust owns remote protocols, command boundaries and result handling.
02
Turn common failures into reviewable workflows
Incident Packs only orchestrate Native Typed Tools already in the Registry, and root cause must cite real evidence. Repair binds existing ChangeSets or Fleet ChangeSets; the Disk pack never generates or performs automatic deletion.
Git deployment can connect repository, branch, environment, build and startup stages. SSL, backups and Cron remain related but distinct. Writes require explicit approval, verification uses a real read-only check, and rollback appears only where it has been implemented.
03
Keep boundaries across multiple servers
Fleet writes run sequentially by default and pause for review at defined points. Approval binds the exact target list and each target's ChangeSet version; any change invalidates the approval.
Execution, verification and rollback remain independently visible per server. A failure on one target does not expand scope, and production writes cannot use an unrestricted parallel-all shortcut.
Frequently asked questions
Operations & deployment
Do I need a monitoring agent?+
No. The basic Dashboard works over SSH without installing a Runory agent.
Will Runory automatically delete files to free disk space?+
No. The Disk operations pack never generates or performs automatic deletion.
Does a failed deployment roll back automatically?+
Rollback is available only when it is truly implemented and explicitly approved; unsupported operations never claim rollback support.