Hudu
Your documentation, finally answerable.
Hudu holds the tribal knowledge — articles, assets, processes, and the relationships between them. It isn't on the board yet; the connection is being built in the open, and this page is the plan rather than a shipped feature. Once it's connected, a session will be able to pull the documented answer instead of guessing at it.
The story
What changes once it’s connected.
Everything is in Hudu. The wifi setup at the site nobody has visited in a year, the assets that tie to the client you're on the phone with, the onboarding runbook the last tech wrote and never told anyone about. It's documented; it just isn't answerable, which is why people still ask in Teams and get an answer from memory. Once Hudu is on the board, the documented version will come back inside the session — what we have written down for that client's network, which assets belong to that office, what the runbook actually says to do first.
It isn't connected yet, and the plan matters more than usual on this one, because Hudu can hold secrets as well as knowledge. The connection will be scoped to articles, assets and their relationships, with password entries excluded structurally rather than filtered out after the fact — a shape the connect page will state plainly when it exists. Connecting will take an API key you generate in Hudu and your instance URL, hosted or self-hosted alike. The full skill list and its limits get published here the day it ships.
What you’ll be able to ask
Here’s what’s coming.
Connecting
Wire it in, in an afternoon.
How connecting will work
- 01You'll generate an API key in Hudu (Admin → API Keys).
- 02Have your Hudu instance URL ready — hosted and self-hosted work the same way.
- 03The instance URL and key get entered here; password entries stay excluded by design.
Patch your stack in.
Start the Switchboard free trial against your own environment — read-only, traced answers, live in an afternoon. The apps are on the shelf when you want them.