Milo
IT sentinel
A face for your all-round employee: “IT sentinel” is the suggested preset, not an obligation.
I watch over your machines and services. My round is read-only: I observe, compare with yesterday and classify. I never bother you for nothing, and I never fix anything silently.
You
“Milo, why was the website slow last night?”
Everyday work clothes.
What I do
Six verbs. Not one adjective.
Milo’s work, as it appears in your activity log. Every task ends with a report, even when there is nothing to report.
Does his round every night: disk space, memory, services, backups, security updates, certificates.
Compares with the previous night and flags drifts before they turn into outages.
Classifies every finding: all clear, keep an eye on, handle this week, urgent.
Delivers a one-page health report every Monday, three actions at most.
Diagnoses a slowdown or an outage and proposes the exact command, with the risk.
Alerts you by email and desktop notification when it’s urgent, not before.
Control
What I never do without your go-ahead.
Milo really acts on your tools. That is precisely why some actions stop in front of you, with the exact tool and the exact parameters, and wait.
The first four rules are troopio’s safety floor: they live in the daemon’s code, not in a file the agent could rewrite, and they apply whatever the autonomy level. See the Security page
- Send an email, a text message or a document to anyone other than you.
- Pay, transfer money or approve a payment.
- Delete anything outside its workspace.
- Create, change or use an access (key, password) on a new host.
- Install, update, restart, change or delete anything on the machine.
- Use sudo, or read the contents of sensitive files (keys, passwords, .env).
- Touch DNS, the hosting provider or a production deployment.
A deliverable, not a promise
This is what the work looks like.
An anonymised example of what Milo drops into your mailbox and deliverables folder. The real file carries today’s date, and your figures.
Night round of 23.09.2026
- KEEP AN EYE ON: /var volume at 82 % (78 % on 22.09). Trend: +1 %/day. Alert threshold 85 %.
- NAS backup: last run 23.09.2026 01:12, OK.
- Pending security updates: 2 (openssl, curl). Proposal: Thursday 12:00 window, no restart required.
- Certificates: none expires within 14 days. Expected services: 6/6 running.
Connected tools
What Milo works with.
No API key written into a file, no logo to take on trust: every access is named, limited to one host and revocable in one click.
The machine troopio is installed on
Local read-onlyread-only, never sudo
Hosting provider and status page (Infomaniak, Exoscale)
API key in the vaultNAS and backup logs
File dropCall to your mobile phone
Connector plannedplanned for critical incidents
- API key in the vaultyou enter the key once in the vault’s masked form; the employee never sees its value.
- File dropyou drop your exports (PDF, CSV, camt.053) into its inbox.
- Local read-onlyread-only access to the machine troopio is installed on, never sudo.
- Connector plannednative connector planned, not yet delivered: we would rather say so than promise it.
On your schedule
You dictate the sentence. It becomes a schedule.
One sentence is enough. troopio turns it into a cron expression (Europe/Zurich time zone), rephrases it for you to confirm, and runs a first test straight away.
“Every night at 02:00, Milo does his round.”
CRON0 2 * * *Report “Night round of <date>”. If all is well: one line, “all clear”.
“Every Monday at 08:00, Milo delivers the week’s health report.”
CRON0 8 * * 1One page: trends, incidents, what awaits your decision, three actions.
A scheduled run that fails three times pauses the schedule and lets you know. A run that delivers nothing is reported as such. Never silence.
Works with
He doesn’t work alone.
Milo passes on to colleagues whatever falls within their field, and says so in the report. You see who did what.
Preset ready
Milo can start this afternoon.
Fifteen minutes to create your employee and see its first deliverable. Nothing goes out without your go-ahead.