[korijn]

It's usually a company-specific interpretation of software validation requirements (imposed by regulators) that software cannot be changed (ie updated) outside of the company's control. Web apps are fine as long as the company can host and perform upgrades/maintenance themselves.

[qubex]

Uhm, no. I assure you the powers-that-be in my firm would totally lose their marbles if highly reserved data were crossing out into some web-app hosted who-knows-where and viewable by who-knows-who.

[egeria_planning]

If you choose the on-premise options no data will ever leave your company. Administrators will install the software on a server inside your company and will be responsible for updates, backups and security of the server.

[qubex]

That’s a “more workable” solution.

Still, again, as a power user... native applications are hard to beat.

[korijn]

It's what I meant by "host".

[qubex]

A native application is a stand-alone, non-electron application whose entire stack (runtime, business logic, data engine, and information store) resides on the user’s machine.

‘Hosted’, to me at least, means that you’ve got an augmented web server somewhere on your intranet that you connect to, and that displays its interface through a browser on the user’s machine.

The two terms are mutually exclusive, in my understanding (except of course when one is speaking explicitly of “hosting a web server”, but I’m sure you catch my drift).

[korijn]

Still sounds company-specific to me! Not every company is like that.