Compare
RunbookHQ and Hudu
Hudu documents what you have. RunbookHQ is the procedure, the baseline, and the local confirm. Adjacent, not a replacement.
RunbookHQ
- Scripts, runbooks, standards, and reports in one organization-wide list.
- MCP from your editor with the same access you have.
- Desktop confirms before a local script run. Output never leaves that machine.
- Following a runbook is browser-local. Script runs are activity, not a run record.
Hudu
- Asset and documentation inventory: what exists at a client or site.
- Passwords, configs, and a client catalog.
- Processes and KB that can be imported as runbooks, with the source URL kept in doc_ref.
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.