It depends. Organizations have different data, so you need a lot of abstractions in order to fit into a certain search pattern (meaning, what are the users look

It depends. Organizations have different data, so you need a lot of abstractions in order to fit into a certain search pattern (meaning, what are the users looking for). For example, current solutions implies there is a "document" with some metadata. But what is a document in wikipedia or SO context? So is quite hard to get a an answer which satisfies both cases and you end up with cramming all kind of data together just to make a fit. So in the end, you still have to use the google model, of using the URL as a key for (data, metadata). So in this case, just let google/bing/yandex do it's job. On the other side, I saw Google Search Appliance fail spectacularly in enterprise, because the google model couldn't fit and you end using real custom search solutions. There are quite a lot of companies filling this niche at this moment and so I think Mozilla wouldn't make a dent, if decides to enter this market.