Use cases · Fleet deployment
Install and update software across dozens of machines in plain language
Store PCs, lab machines, office laptops, kiosks: getting the same software onto all of them is slow by hand and heavy with scripts. Octling connects the fleet with one install command, then lets you roll out changes by describing them.
“On every machine in the Stores group, install the latest Chrome and pin it to the taskbar”
“Check which devices are missing the VPN client and install it on them”
How it works
- Create a deployment pack: pick the group the machines should join, tags, a naming rule such as
pos-{seq}, and whether the client should run as a resident service that starts on boot and updates itself. - Hand the install command to whoever sets up the machines, or run it yourself. Each install shows up in the pack's install log with its operating system.
- Create a batch task for the group: “Install the latest printer driver, set the default printer to Front Desk, then restart the spooler.”
- Run it. Use “Confirm on the first device, replay on the rest” to check one machine before the others follow, retry the ones that failed, or save the task as a schedule.
Keep the fleet healthy afterwards
Inspection rules watch the same group for low disk space, outdated clients, stopped services, missing processes or any custom check, and can start a batch task automatically when something is wrong.
Questions
- How is this different from Ansible or a configuration management tool?
- You do not write playbooks or keep an inventory file. Machines join by running one install command, and you describe the change in plain language. The AI adapts commands to each machine's system and handles the errors it finds along the way.
- How do new machines get connected?
- Create a deployment pack and give its install command to whoever sets up the machines. Every machine that runs it joins the group and tags you chose, named by your naming rule. You can cap the number of installs and set an expiry date.
- What if the change breaks on some machines?
- Run the batch with “Confirm on the first device, replay on the rest” so you check the result on one machine before the rest follow. Failed devices are listed and can be retried on their own.
- Does it work on Windows?
- Yes. Windows, macOS and Linux, x86_64 and ARM64. Resident installs on Windows ask for UAC once; on macOS and Linux they ask for a password once.