2 ms·
I work for a giant global enterprise that buys from your employer, specifically for (a) indemnity and (b) “train the trainer” jumpstart expertise. I would argu
by Terretta 8y ago
I work for a giant global enterprise that buys from your employer, specifically for (a) indemnity and (b) “train the trainer” jumpstart expertise.
I would argue that to qualified engineering teams at a regulated buyer, license indemnity is the bulk of value of interest. Someone wants to use OOS, they have to go find a “liability sink”. The trick becomes finding one offering a purer upstream, and w/o vendor lock-in such as custom tooling devs have to learn to manage the system.
Given the qualifiers in that comment, many customers, including some within this firm, will find your broader ‘enterprise’ offerings of interest as well.
- jacques_chester 8y agoI don't think I explained myself very well (edit: and I am typically oversensitive to suggestions that enterprise software isn't a genuinely difficult and important undertaking). My point was that there is a lot of work that needs to be done to make software usable in an enterprise environment that is orthogonal to the license. A lot of that work is simply not a problem for most individuals. It's demonstrable that these features are orthogonal to license, because they were expected before OSS became a norm. LDAP/SAML/OAuth/OIDC/whatever integrations, online backups, auditing, accounting and usage, multi-tenancy, credential management, file integrity, mandatory access control, etc etc. There are thousands -- literally thousands -- of things that enterprises collectively want that individuals and small teams don't even think about. A lot of OSS efforts acquire these capabilities because an enterprise vendor sponsored their development. Hence my point that "a single throat to choke" is only a slice of the value we and our competitors add.