[cmauniada]

> Still, startups have to learn that if you're serious about being in enterprise, having a locally hosted option opens doors. Very lucrative doors.

Can you explain why that is?

I do agree with your point, having been exposed to running openstack on a custom infrastructure for my job has really taught me how much $ you can save if you do things yourself over say aws and that once I picked up the basics of compute, volumes, networking and security. My understanding increased.

I sometimes would find it difficult to keep up with all the aws lingo but doing everything myself has been a really good lesson in keeping things small and lean.

[handrous]

Usually has to do with security requirements, often dictated by the industry they're in. Health care and military contracting are both huge, and are both areas that large companies tend to end up serving even if they didn't set out to do that, with the result that lots of enterprises need to be able to satisfy a variety of security check-lists, most of which are easier to deal with if a service is self-hosted. This can include things like "must guarantee no traffic containing X goes over an insecure network" or "must guarantee no data ever transits or is stored in [LIST OF COUNTRIES]". These directives can be in conflict for different orgs, too, so it's not something you can just fix one time in your hosted version and appeal to everyone.