AI security & operations for MSPs

Hudu

Documentation is the difference between a generic recommendation and one that fits this client.

What Hal reads
Documentation, runbooks, network maps and asset records.
What it enables
Advice that matches how this client is actually built, and answers to questions your team would otherwise have to look up.
How it connects
A Hudu API key you create, withholding password viewing, deletion and export. Hal only reads with it. Read-only by architecture →
Setup
The key, the company mapping and the steps: in the docs →
A chat exchange in the Hal portal: the documented after-hours access procedure for a client site, read out of that client's Hudu runbooks including the MDF location, where the rotating door code is kept and the alarm panel timing
Your own documentation, answered back. The building contact, the MDF and the 45-second alarm window, from the runbook your team wrote. The door code itself stays in your Hudu vault, which Hal does not read; the runbook tells you which entry.

See what Hal surfaces on your own clients.

No deck. Ask us anything first. When you want to see Hal on your own tenants, we sign a short evaluation agreement and stand up your instance; you connect one tenant, Hal watches it for 14 days, and we walk you through what he found.

Book a walkthrough Pricing
  1. 01You ask us your questions. No deck, no demo dataset.
  2. 02You sign a short evaluation agreement, and we stand up your own instance.
  3. 03You connect one tenant from your own admin console. Hal watches it for 14 days.
  4. 04We walk through what he found. Keep going month to month, or revoke the scopes yourself and stop.