How it works
Three steps. The third one is doing nothing.
Arqos is built so the setup is an afternoon and the day-to-day is silence. Here is the whole product, honestly described.
step 01
Run one command on each server
That's the entire install. One small program — about 9 MB — introduces itself with a one-time code and starts work. It takes about 60 seconds per machine.
What you don't do matters more: no VPN to set up, no firewall changes, no ports to open, no maintenance window, no reboot. Nothing about your network is touched. Your switches, routers, and storage need nothing installed at all — one machine on the network quietly checks on them for you.
$ arqos-agent enroll --token et_4f29…
[•] enrolled as device dc-01
[•] reporting every 60s
step 02
Every machine reports in, once a minute
Each report travels over the same encrypted channel your web browser uses for online banking — outbound only. Your machines call Arqos; nothing ever calls them. To the outside world, your network looks exactly as closed as it did yesterday.
A report is a short list of health numbers: how busy the processor is, how full the memory and disks are, whether the machine is up. Numbers in, numbers out — never your files, never what's on anyone's screen.
[•] report sent (cpu 11.2%, mem 31.0%, 2 disks)
[•] report sent (cpu 12.0%, mem 31.2%, 2 disks)
[•] report sent (cpu 11.7%, mem 31.1%, 2 disks)
step 03
You hear from Arqos only when something needs you
If a machine goes quiet, Arqos notices within about 2 minutes and tells you — by email today, with more channels coming. When it comes back, Arqos confirms the recovery automatically, so you never wonder whether a 2 a.m. alert still matters by morning.
The dashboard works the same way: healthy machines collapse into quiet summaries; anything unusual is already at the top when you open it. No hunting, no forty charts, no morning ritual of scrolling past green lights.
[!] dc-01 stopped reporting — alert sent 02:13
[•] dc-01 back online — resolved 02:19
[•] 13 other devices: quiet
That's the entire product. There is no step where Arqos reaches back into your network, because the software can't — a distinction your security team will appreciate, explained on the security page.
Your first server can be reporting in the next five minutes.
Early access is open to a small number of MSPs and IT teams.