Compare
Next to the tools you already use
RunbookHQ is the baseline, the procedure, the local confirm, and the evidence. It sits beside your documentation platform and your code host. Adjacent, not a replacement.
Hudu and IT Glue
Hudu and IT Glue
- Asset and documentation inventory: what exists at a client or site.
- Passwords, configurations, and a client catalog.
- Processes, SOPs, and KB articles.
RunbookHQ
- The procedure as ordered steps with {variables}, linked to the standard it applies and the script it runs.
- Desired-state standards with MUST / SHOULD / MAY clauses and a naming generator with a locked sequence.
- Desktop confirms before a local script run; the run is audited with host and exit code.
Runbooks → Import pulls Hudu processes or IT Glue documents in as runbooks and keeps the source URL in doc_ref. Ticket and documentation refs deep-link back, so the record of what exists stays where it is.
GitHub
GitHub
- Source code, pull requests, and CI.
- A script is a file in a repository.
RunbookHQ
- The runbook around the script: when to run it, with which parameters, and what should be true afterwards.
- Parameters parsed from PowerShell comment help, a confirm dialog on the technician's machine, and an audit row per run.
- Standards and reports that a repository has no place for.
Scripts → Import pulls a file, folder, or gist from GitHub and can stay pointed at the repository for a manual sync. The code lives in GitHub; the procedure and the evidence live here.
What this is not
- Not a PSA, wiki, inventory, or vault.
- No client catalog or working-client switcher. Restricted folders hide content; they are not a client list.
- Hosted script execution is out of scope. The confirm stays on your computer.