> In the second post, we discussed how there is actually quite a bit of overlap between SaaS and Open Core and to draw a distinction, we would assume the Open Core software is primarily being delivered on-premises for comparison purposes.<p>Hmm, that might be convenient for your analysis, but it seems an unsafe assumption and artificial categorization to me. I think an increasing number of "open core" efforts, possibly most of them, are trying to monetize the non-open-source portions via SaaS. In fact, as we saw in the Amazon/ElasticSearch fight, one of the main motivations for not using a FLOSS license for some or all of your software is to prevent SaaS competitors from using the software you are producing.<p>I tried to look at your list of companies analyzed categorized "Open Core" to see how many of them offer a SaaS, but I realized that for these companies I was unfamiliar with it was hard to figure that out quickly from their web pages. Let alone then figure out if they were <i>primarily</i> delivering as SaaS if they offered an on-premises option (as even Github does). But that would seem to be neccessary to validate your assumptions.