@notverypunny said in Hardware Management Solutions:
@dustinb3403 How severe is the data isolation requirement? From a view / workflow / alerting standpoint things can be broken out by client / site etc with maps and / or dashboards but yeah, most of the centralized logger / ticketing / MSP / rmm-y type solutions will use a common database behind the scenes. From a data isolation standpoint, if you've got multiple clients and sites pushing to a common email address there's the same potential for data intermingling in that common repository as a shared database.... Just some food for thought.
It's a semi-quazy requirement that the data at least be separated into their own "customer". While overlap is expected, I can't have system Y from one customer populate details or mix with Customer B.



