Salix Monitor 360 • Product update
Salix Monitor 360 update: stronger scanning, cleaner PDFs and launch polish
Written by Graeme Moignard
Published:
Last updated:
Since the last blog update on 30th May, Salix Monitor 360 has had another practical round of work. The focus has been reliability and presentation: clearer security scan output, stronger PDF exports, tidier website pages, clearer release preparation and stronger day-to-day reliability.
The aim is simple: make the product easier to understand, easier to trust and closer to something people can rely on in production.
Vulnerability scanning is getting a sharper shape
One of the bigger pieces since the last update has been the vulnerability scanning side of Salix Monitor 360. Nmap and OWASP ZAP were already part of the story, but Nuclei is now being worked into the public explanation and the app workflow as another practical scanning tool.
The important part is not simply adding another scanner. The useful part is turning scanning into something an admin can understand: choose a sensible preset, see that the scan is doing real work, get output that is readable, and then decide what genuinely needs attention.
Scanning flow
Three tools, one clearer operator experience
The goal is to let the app do the technical heavy lifting while the admin gets usable findings, not a wall of cryptic scanner output.
- Nmap for network and service discovery.
- OWASP ZAP for web application checks.
- Nuclei for template-driven vulnerability checks.
- Clearer presets and output so results lead to action, not confusion.
During this build phase, the scanning work is being used to find rough edges early and make the results easier to act on. The important launch rule is simple: security checks should produce clear findings, and anything meaningful should be fixed before the service is opened up more widely.
PDFs and help exports are getting cleaner and more professional
PDF work has also had another polish pass. A good PDF export should not expose implementation details to the reader. A customer does not need to know which PDF engine produced a handbook, and an organisation report should not randomly show Willow Software contact details where the customer context belongs.
The recent help PDF work tightened that up. Cover wording has been cleaned up, and the old “Contact” style block has been turned into something more useful for customer-facing output: “Prepared for” with the organisation name. It is a small wording change, but it helps the document feel like a proper customer report rather than a rough export.
PDF polish
The cover now behaves more like a real customer document
The PDF work is still part of the wider push towards complete, printable, branded documents: no thin placeholders, no confusing labels and no accidental wrong-brand output.
The public website is getting lighter and cleaner
The public Salix Monitor 360 website has had more work too. Screenshots and homepage visuals are being revisited, converted where sensible, and tuned so the site feels cleaner without becoming slow or bloated. WebP conversion is part of that, along with tidier carousel behaviour and another pass on the dark default theme.
The security page copy has also been brought closer to what the product actually does. Nuclei now belongs in that explanation alongside Nmap and OWASP ZAP, because the scanning story should be honest about the tools being used and the type of checks the product is growing towards.
Screenshots
More useful product visuals
The app needs marketing images that show what it actually does, not vague dashboard filler.
WebP
Smaller image weight
Image files are being prepared so the site can look better without making pages heavy.
Copy
Clearer security wording
The scanning page now has a clearer way to explain Nmap, ZAP and Nuclei together.
Companion app work is still being kept practical
The companion apps are still being treated as separate release tracks rather than one confusing bundle. Windows remains the known desktop path. Android has its own testing and store route. iPhone and iPad work will follow the Apple testing and store path when ready.
That separation matters because each platform has its own trust, signing and publishing expectations. Keeping those routes clean now should save a lot of future pain.
The current direction: tidy, check, then launch carefully
There has also been a lot of smaller product tidying around menus, settings, admin wording, website styling and upload-ready packages. Some of that work is invisible when it goes right, but it still matters. It means the product feels calmer, clearer and easier to use.
The next major milestone is the production hosting build. Before Salix Monitor 360 is opened up more widely, the launch environment needs the same careful treatment as the product itself: sensible hosting defaults, security checks, performance checks and any meaningful findings fixed before customers are asked to rely on it.
That is the useful theme of this update: not just more features, but more care around the features already there. Scan output should lead to sensible action. PDFs should look like they belong in a customer conversation. Companion apps should have clean public release paths. The website should explain the product clearly and avoid being slowed down by oversized screenshots.
Salix Monitor 360 is still very much a build in motion, but this phase is about tightening the details before launch. For monitoring software, that is exactly where the product needs to be: clearer, steadier and easier to trust.