1. our product is 100% open source, developed in the open, using the ALv2 license, open issue tracker, mailing list, code on GitHub, etc.
2. Our primary focus right now is the "on premises" deployment model (although SaaS delivery will be available)
and (2) is largely rooted in (3)
3. A tremendous focus on integration. The vibe we get from talking to users of Yammer and the other social networking products is that the largely just become sort of a "replacement for email" or maybe a complement to email. There are different reasons for that, but our thesis is that a big part of it is that the products don't lend themselves to integrating into existing workflows and processes. By comparison, we have SOA/ESB integration for real-time business event subscriptions, BPM integration to make a "social BPM" offering, Calendaring integration, and more to come.
4. A big focus on contextual computing, largely driven by use of semantic web tech. As "content" of various types passes through the system, we do semantic concept extraction, clustering / classification, etc., so we can show you - for a given piece of content, business event, person, task, etc. - all of the related (people|content|documents|events|etc).
5. Open standards focused: all our integration points are based on open standards, including RSS, Atom, ActivityStrea.ms, RDF, FOAF, and the like.
Other than that, it's basically the same thing. :-)
The major areas where we differ are:
1. our product is 100% open source, developed in the open, using the ALv2 license, open issue tracker, mailing list, code on GitHub, etc.
2. Our primary focus right now is the "on premises" deployment model (although SaaS delivery will be available)
and (2) is largely rooted in (3)
3. A tremendous focus on integration. The vibe we get from talking to users of Yammer and the other social networking products is that the largely just become sort of a "replacement for email" or maybe a complement to email. There are different reasons for that, but our thesis is that a big part of it is that the products don't lend themselves to integrating into existing workflows and processes. By comparison, we have SOA/ESB integration for real-time business event subscriptions, BPM integration to make a "social BPM" offering, Calendaring integration, and more to come.
4. A big focus on contextual computing, largely driven by use of semantic web tech. As "content" of various types passes through the system, we do semantic concept extraction, clustering / classification, etc., so we can show you - for a given piece of content, business event, person, task, etc. - all of the related (people|content|documents|events|etc).
5. Open standards focused: all our integration points are based on open standards, including RSS, Atom, ActivityStrea.ms, RDF, FOAF, and the like.
Other than that, it's basically the same thing. :-)