How it works
Add a key. We check daily. You approve fixes.
-
1
Add a key
Add your server and paste our public key into authorized_keys for a dedicated user. We give you the exact line, limited to our scanners' fixed IP addresses, and an optional sudoers file that allows only the read-only commands the checks need. Then we test the connection and take a first baseline.
-
2
We check daily
Every day we connect, collect facts with read-only commands, and compare them with the previous run. AI agents investigate what is new or changed, and a second agent verifies each finding before it reaches you. You get an alert only for things that matter, with the evidence attached.
-
3
You approve fixes
When something needs fixing we propose the exact commands, the risk, and how to roll back. Nothing runs until you approve it. Fixes use a separate key, take a baseline first, verify afterwards, and every command lands in the audit log.
Change over time is the signal
Every run is saved and compared with the one before. "A new PHP file in uploads since yesterday" is far more useful than "a PHP file in uploads", and attackers can fake a file's modified time but not when it was created.
People change servers too
Reboots, deploys, package updates and config edits by your team show up as changes, not as attacks. We don't fight your operators.
Facts first, AI second
Plain, repeatable checks run on every server every day, which keeps results consistent and costs predictable. AI agents add judgment: they investigate (still read-only), connect findings across servers, and explain what happened and where the hole is.
Use it from the terminal
The same checks run from the hc command-line tool, for
incident response or a quick look before you change something.
$ hc check --host web-1
Connecting as handscheck@web-1 (read-only) · Ubuntu 24.04 · 3 sites
✔ system 2 security updates pending · kernel 6.8.0
✔ users no new accounts · sudo intact
✖ persistence new systemd unit since yesterday, not from a package:
dbus-socket-helper.service → /usr/sbin/authd
✖ malware shop.example.com: PHP file in wp-content/uploads/2026/10/
created 02:54 UTC, modified time set back to 2023
! wordpress shop.example.com: new admin "wp-support" (registered date copied from user #1)
✔ exposure no directory listings, no backups in web roots
✔ health p95 response 410 ms · PHP-FPM workers 12/40
3 findings (2 critical, 1 high) · verified · 2 fixes proposed for your approval
Next: hc findings show 1
Want to know exactly what we can and can't do on your server?
Read how we handle access and keys.