A reasonable requirement which leads to "run everything in VMs" is the need to support on-premise deployments. Often data-security and compliance requirements can be handled most reasonably (or at all) by allowing the enterprise client to pick where to deploy a single-tenant copy of the service. For this, I think the most reasonable approach is to only require VMs and do all the configuration yourself (preferably in some scripted / automated manner).
Of course, in this case, (unless you install a private cloud), you forgo all the convenience and advantages of a cloud infrastructure (so one can argue that this wouldn't really count as 'cloud agnostic'), but since such on-premise deployments should only be required by big enterprise clients, they should have deep enough pockets to pay for it.
You make the owner responsible. I.e. if the driver can be identified (or the owner identifies the driver) then you can fine the driver, otherwise you fine the owner.
The type of ventillators required by the most serious cases are much more complicated: as I understand it, it involves push a tube down to the lungs, and the machine breathing instead of the patient, i.e. it has to carefully monitor and regulate the pressure etc. Already the "push tube down to the lungs" part is quite a challenge: avoiding damage to the vocal cords, or to the lungs, etc.
Any suggestions for MDM for Linux laptops? Most device management solutions I have seen are for either Windows or Mac, but is there one that is accepted by auditors and is not utter garbage UX wise for the user on Linux, where the user is most likely going to want and have full admin access to their own laptop? (I.e. since the user in question is a developer, I feel a strong aversion to not trusting them to do system administration on their own laptop.)
I would assume the "engineers vs accounts" is due to the output not being intended for the coders, but the managers. I.e. you only have accounts for the managers, but you price based on how large a team they are monitoring.
(This is just a guess, I have no connection to haystack)
Of course, in this case, (unless you install a private cloud), you forgo all the convenience and advantages of a cloud infrastructure (so one can argue that this wouldn't really count as 'cloud agnostic'), but since such on-premise deployments should only be required by big enterprise clients, they should have deep enough pockets to pay for it.