Documentation
Zero to a reporting agent in fifteen minutes.
Written for a competent sysadmin who is short on time and slightly suspicious. No adjectives about how easy it is — just the command, and the limitations published rather than discovered.
Action library
26 actions
bundle 2026.08.1
Observed runs
25,396
222 reverted and rolled back
Irreversible actions
4
never promotable to unattended
Overview
Deployment
Operating
- Stopping KoopOne button, five seconds, every machine — and it still works when Koop itself is down.
- Configuring GuardrailRisk tiers, device groups, time windows, approval routing — and a 90-day ramp you should actually follow.
- Ticketing integrationsOne page per system, with the limitations published rather than discovered.
- Reading LedgerHow to answer “why did it do that” in under thirty seconds, and how to get it into your SIEM.
- How the agent updates itselfSigned, staged, watched for ninety seconds, and reversible for a week.
- Verifying what you installedEverything here you can check yourself, with public tools, without asking us.
- When we touch your machinesHow a release reaches your fleet, how you control the timing, and how a bad one stops itself.
- How the action library shipsThe remediations update weekly on their own key and their own pipeline. The agent updates quarterly. A bad action is gone from your fleet in five minutes without either.
- RunbooksWhen something is wrong, start here.
- What happens if it breaks somethingThe question everybody asks and almost nobody writes down. Here is the whole sequence, including the parts that are uncomfortable.