Use cases · Server maintenance

Clean up disk space on every server with one sentence

Disks fill up with logs, package caches and old Docker images. With Octling you type what you want once, and the AI checks every connected machine, cleans the ones that need it and reports back, one machine at a time or all of them in parallel.

How it works

1. Connect your servers. Run the one-line install command on each machine, or create a deployment pack and reuse the same command across a fleet. Linux, Windows and macOS are all supported.
2. Describe the job. For example: “Check free disk space on all devices. Where usage is above 85%, clear package caches, old journal logs and unused Docker images, then report what was freed.”
3. The AI does the work on each machine. It picks the right commands for the system it is on (apt, dnf, journalctl, docker, PowerShell on Windows), reads the results and adjusts if something fails.
4. Review the result. You get a summary per device, and every command and its output stays in the audit log.

Run it across a fleet safely

For many machines, use a batch task with “Confirm on the first device, replay on the rest”. The AI works through one device first; you review exactly which commands it ran; once you confirm, the remaining devices replay the same command sequence without asking again. Failed devices can be retried on their own.

Approval rules let you decide which commands always need a human click, and you can save a batch task as a schedule, for example a weekly cleanup on Sunday night.

Catch full disks before they cause outages

Inspection rules check your devices every 15 minutes, hourly or daily for low free disk space, sustained CPU load, missing processes, stopped services or the result of any custom command. When a rule hits, Octling can notify you and automatically start a batch task, such as the cleanup above.

Questions

Do I need to write a script or an Ansible playbook?

No. You describe the job in plain language. The AI chooses commands that fit each machine's operating system, runs them, reads the output and decides the next step.

What stops the AI from deleting something important?

Commands that match your approval rules wait for you to confirm, high-risk commands are blocked, and every command and its output is written to an audit log. In batch runs you can confirm the first device before the rest replay the same commands. Keep backups of anything critical, as you would with any admin tool.

Which machines can I connect?

Windows, macOS and Linux computers, x86_64 and ARM64 servers and cloud hosts, Raspberry Pi and other Linux boards, and Android devices. Each connects with one command.

Does the agent need root or administrator rights?

Not to connect. A temporary connection runs as your user. If you want a resident service that starts on boot and updates itself, installation asks for admin rights once. Cleanup tasks that touch system directories still need the matching permissions on that machine.