What do you need?
- •A Ploi-managed server with systemd (amd64 or arm64)
- •An Opservo workspace; Free covers up to 2 servers
- •Outbound HTTPS (port 443) to api.getopservo.com. Opservo opens no inbound port
How do you install it?
- •In Opservo, click Add a new server, then Generate install command. The token in it works once and expires after one hour
- •In Ploi, create a script, set its user to root, paste the command and run it on one server
- •Or over SSH: log in as ploi, run sudo su with the sudo password Ploi emailed you, and paste the command
- •Generate a fresh command for each further server, because each token is single-use
curl -sSL https://api.getopservo.com/install.sh | sudo env OPSERVO_API_URL=https://api.getopservo.com OPSERVO_TOKEN=<token> bashFor a batch, a reusable fleet key lets one script run enrol many servers. Fleet-enrolled servers are treated as disposable: one offline for 30 minutes is archived automatically instead of raising an offline alert, so prefer one-time tokens for long-lived servers.
What do you see afterwards?
Each server gets a 0–100 health score and findings with the command that fixes them: CPU, memory, disk and load; systemd services such as nginx, PHP-FPM, MySQL and Redis; Docker containers; listening ports; security checks; kernel-log errors; and laravel.log for sites in /home/ploi/<site>. Domains and SSL expiry are read from the standard nginx config folders. For any site the agent does not list, add an uptime monitor, which checks it from outside and tracks the certificate.
Last updated 2026-10-10.