Software · System software
System utilities
Small, dependable tools that install, check, clean and maintain the machines your business runs on.
Every IT team has a folder of fragile scripts that only one person understands. We turn them into proper tools: single-binary command-line utilities and background agents with clear options, logging, dry-run modes and installers, so routine jobs like provisioning, clean-up and health checks run the same way on every machine.
What we build
- Cross-platform CLIs in Go or Rust, shipped as one binary per platform
- Background agents and Windows services that collect inventory and health
- Installers and updaters packaged as MSI, pkg, deb and rpm
- Disk clean-up, log rotation and file archiving tools with safe defaults
- Provisioning tools that set up new laptops and servers from a profile
- PowerShell modules and Bash tooling for Windows and Linux administration
DemoInteractive · sample data
Try it live.
A working sample with made-up data. It runs in your browser; nothing is sent anywhere.
admin@ops-01:~$ fleetctl --version fleetctl 0.9.2 (linux/amd64) admin@ops-01:~$ fleetctl disk report --group web
What it does well
Dry-run first
Every destructive command can preview its changes before anything is touched.
One binary
No runtime to install: copy the tool and it runs on Windows, macOS or Linux.
Readable output
Human-friendly tables by default, and JSON output for scripts and pipelines.
Least privilege
Tools request only the permissions a task needs and log every change they make.
Self-updating
Signed releases let installed tools check for and apply new versions safely.
Shell completion
Tab completion and built-in help for Bash, Zsh, Fish and PowerShell users.
Questions
Why rewrite scripts that already work?
Scripts that work for their author often fail on a different machine, path or user. A proper tool adds argument checking, logging, error handling, tests and a dry-run mode, so anyone on the team can run it safely and see afterwards what it did.
Go or Rust for a command-line tool?
Both produce fast single binaries. Go is quicker to build and maintain for most admin tools and agents. Rust suits tools that parse large files, run in tight memory or need fine control of the system. We choose by the job; either way you get one binary per platform.
How do the tools reach our machines?
We package them for the way you already manage devices: winget, Intune, Group Policy, apt or yum repositories, Homebrew or your endpoint management tool. Updates are signed, and versions are reported so you know what each machine runs.