Improvements
Improvements to device type classification
Bug Fixes
Fixed an issue that could cause Radar authentication to fail
Fixed an issue that could cause stale device information to appear
Bug fixes
Resolved an issue causing large API requests in some cases
Fixed an issue where the KB icon could be missing
Minor bug fixes and improvements
Improvements
Added dedicated password and OTP reveal buttons on the password details screen
Bug Fixes
Resolved an issue that could prevent login after session timeout
Various bug fixes and improvements
Improvements
Added a new server device type for distinguishing servers from workstations
Bug fixes
Deleting a device now also removes it from the network map
Duplicate port labels no longer appear on child devices in the network map
Hudu v2.43.2 is now live. This patch includes a handful of bug fixes and performance enhancements. Self-hosted environments may update at any time; updates to cloud hosted environments will begin today.
Improvements
ConnectWise setup now makes matched and unmatched company counts clickable, and save buttons are labeled “Save and Next” when another step remains
Hudu Radar device filtering keeps the current selection stable, shows an empty state when no devices match, and persists applied filters across refreshes
Added server device type to Hudu Radar
Added “Radar installed” and “Agent installed” filter options for Hudu Radar devices list
Hudu Radar updates now download the installer that matches the deployment’s file type, without prompting for file type selection
Improved keyboard accessibility for filter panels and table column selectors
Added a new MCP tool, “Show public photo”, to allow AI clients to display images from KB articles
Bug Fixes
Sorting by a date or number field then sorting by name resulted in incorrect ordering
Process runs incorrectly showing as “flagged” after process conversion for some users
MCP returning base64 data for images leading to timeouts
CSV exports for list select fields now show readable values instead of only IDs
Authors and Editors can delete files uploaded in the right-hand files panel again
Radar detected devices list not scrolling correctly on mobile view
Successful Duo MFA sign-ins not being recorded in activity logs for some users
Changing a group name reset the group's asset layout access
Increased TOTP secrets character limit
Added validations when moving folders between KBs via the API
Default SMTP settings overriding custom SMTP settings
Optimized the Assets API list endpoints so that fetching assets that have integration cards no longer slows down as the number of assets grows
ConnectWise Manage and Datto RMM integration performance improvements
Other minor bug fixes & improvements
Hey Hudu Community,
We're back with another Build a Feature post — and this one's been a long time coming.
Portal is getting a significant overhaul, and we want to share where we're headed before we ship, so we can hear from you while there's still time to adjust.
Why we're rethinking portal
The current portal works, but it's limited in ways that matter. You've told us:
SSO support is missing
Managing multiple companies or sites is painful
Access to core Hudu tools (passwords, articles, processes) isn't available
There's no search
Personal password storage isn't there
Museum access is missing
Adding records to portal is tedious
And, you're right on all of it. Here's what we're building.
What's changing
The core shift: portal users will become read-only users of the main Hudu app — the same web app your internal team uses — rather than a separate, stripped-down experience.
Portal users remain free. This isn't an upsell. You get a significantly more capable portal without any change to how portal users are billed.
Access is scoped through your existing security groups, which means admins can grant portal users access to one company or multiple — whatever fits your use case. No new system to learn.
Portal users will have access to:
My Vault (personal password storage)
All core tools — passwords, articles, processes, photos, and more
Company overview (minus quick notes, activity feed, and agreements)
Hudini
Hudu mobile app
Hudu Assist browser extension
Portal users will not have access to:
Central KB
Global view
Hudu Radar
Dashboard
Companies directory page
Hudu MCP
Bonus: things we're building alongside this
A few improvements coming in tandem that aren't portal-specific but are closely related:
Ability to disable specific core tools for your entire instance
Ability to disable specific tools for a particular group
KB folder permissions
Admin >> Groups and Admin >> Users improvements — bulk actions, sort by role, and more
We'd love your feedback on:
Does the access model make sense to you?
Is there anything you were expecting to see here that we haven't mentioned?
Are there use cases you rely on the current portal for that you're worried won't be covered by this new model?
Any concerns about migrating existing portal members to this new setup?
Drop your thoughts in the comments — we read every reply and use this feedback directly to inform what we prioritize before we ship.
I recently moved from an MSP into an Internal IT team who engages with the business like a service provider model, The documentation has a lot of room for improvement and since Hudu is self hosted, it may seem like a viable candidate to enhance out documentation position.
Looking at the docs, Hudu is missing a lot of the integrations the business would ask for, so I was wondering, is there an open API that enables us to build our own integrations?
At this stage, I am just looking for options
with the new mermaid additions in hudu I thought I'd share something I found that is helpful with visualizing mermaid stuff:
https://mermaid.live/
Just came across today and thought I'd share.
One of our gracious Reddit members, lhcw, recently rebranded their company and ported a collection of terminal color palettes to work as Hudu custom CSS themes — then generously shared the whole set with the community.
Browse and grab any of the themes at huduthemes.com.
To apply a theme:
Go to Hudu → Admin → Design → Custom CSS, paste in the CSS file of your choice, and save.
Big thanks to lhcw for building this and sharing it — this is exactly the kind of community contribution that makes Hudu better for everyone 🎨
Original post: https://www.reddit.com/r/hudu/comments/1u29dce/dropin_css_themes_for_hudu/
I'm testing migration from IT Glue to a self-hosted instance of Hudu at https://10.0.0.10, which uses the self-signed SSL certificate that comes with it. I'm running my migration from a machine on the same subnet as my Hudu instance. I'm entering https://10.0.0.10 as my Hudu Base Domain during the setup process. When running the ITGlue-Hudu-Migration-GUI.exe PowerShell is able to connect to my IT Glue API but PowerShell cannot connect to my self-hosted instance of Hudu so no data is migrated.
migrationrun.log shows:
Name : request
Value : {[Headers, System.Collections.Hashtable], [Method, GET], [Uri, https://10.0.0.10/api/v1/api_info], [ContentType, application/json; charset=utf-8]}
Name : exception
Value : The remote certificate is invalid according to the validation procedure: RemoteCertificateNameMismatch
Is there a workaround to allow the ITGlue-Hudu-Migration-GUI.exe to accept the self-signed certificate or bypass SSL validation in the PowerShell scripts?
Files migration is a powerful article conversion and sync tool that can work for any drive mapped network shares, sharepoint folders, or local files-
And now it's even easier and more powerful than ever with safe article conversion/syncing, and an easy-to-use GUI- (download)
We've included file and article content hashing so that syncing docs that live in files only updates what has changed and can be ran as many times as desired, it's no longer just a one-time job and your articles can follow your files over their lifespan.
This update also includes some less-obvious features that are really handy. Files-Migration utility now checks each file's 'Magic Bytes' to determine migration strategy, in addition to file extension. This is mostly due to the fact that not every file is what it claims to be. Sometimes you might have a docx file masquerading as a doc file.
Another neat item to note is that you can place migrated files in any folder structure you want in Hudu, and they will stay in their respective locations, even after re-syncing.
