Your documentation, powering every ticket.
Neo reads your Hudu docs, client policies, and runbooks before acting on a ticket. Resolutions match your standards because they come from your standards.
What Neo does with Hudu.
Policy-aware resolutions
Neo looks up 2FA rules, onboarding templates, approved software, and device profiles per client before acting.
Your runbooks, executed
Reads your Hudu procedures for a class of ticket and runs them step-by-step.
Scoped password access
Retrieves credentials through Hudu's secure model, respects RBAC, logs every access.
Concrete work Neo handles in Hudu.
Per-client onboarding
Neo reads the client's onboarding page, applies the right groups, licenses, device profile, and signature.
Asset-aware tickets
When a ticket references a device or service, Neo pulls the asset record for context before acting.
Keeps docs current
When Neo makes a change, it can update the related Hudu record so your docs don't drift.
Live in under an hour.
Connect, configure, go. No code, no long implementation.
Connect Hudu
API key with scoped permissions. Neo inherits your Hudu roles.
Index your content
Neo indexes your companies, assets, procedures, and password folders.
Go live
Test mode first. Then let Neo read your docs before every resolution.
Questions about the Hudu integration.
Does Neo respect Hudu's permission model?+
Yes. Neo authenticates per the Hudu API token you create, and inherits exactly the permissions you grant it.
Can Neo update Hudu assets?+
Only with Write permission. You scope it per module and per asset type.
Does Neo need to read everything?+
No. Restrict it to the folders and asset types you want Neo to use. Zero access is a valid choice.
Ready to wire up Hudu?
14-day free trial. No credit card. Live in under an hour, right inside your stack.