Each project is unique. And enterprise suites have so many features, and they evolve, so it's risky just to compare the feature set. Picking a project is a decision which will impact you over the long term. It's useful to understand the deep drive of each project. If you are working on or thinking of starting an alternative, please see Advice for alternatives
This is a play on the quote in Animal Farm by George Orwell:
All animals are equal,
but some animals are more equal than others
In general, the differences with other solutions are:
Other solutions | WikiSuite |
---|---|
Some are personal self-hosting platforms and not designed for teams. | WikiSuite is designed for teams (and you can be a team of one!) |
Some are focused on facilitating self-hosting of many apps, including apps with identical functionality. | WikiSuite is self-hosted as well but it's an enterprise suite that is very opinionated about the apps that compose it. We believe supporting more than one application for the same need adds unnecessary complexity and fragmentation. Please see: http://pluginproblems.com/ |
Some are focused on a more narrow use case (typically around file sync or web apps) | WikiSuite offers most (80%+) of the data and information management features all organizations need: OS and Network, Web and Intranet, Email and Calendar, Files and Sync, BPM and Analytics, Commerce, Chat and Video Conference, Security. |
For some, beyond ease of installation, there is little effort to provide interoperability between the apps | In WikiSuite, we are actively focusing on making all the features work well together. Ex.: A unified user experience with Bootstrap or single sign on between Openfire and Tiki Wiki CMS Groupware |
Some are file-centric. Thus, a lot of functionality is added to manage file metadata, version history, file sync, add workflows around files, etc. and they let desktop software edit the actual file. | In WikiSuite, we want to move away from files. Everything should be editable via the web interface, everything should be stored in a database. See [https://doc.tiki.org/Spreadsheet|Spreadsheet, Word Processor (Wiki), Slideshow, Diagram and Files vs web pages. |
Some are inbox (mail)-centric. | We need to move away from this model. We should be task and project-centric, and email is just one of many data formats we need to deal with. Ex: Customer Relationship Management. This being said, we are working to improve the email experience via JMAP. Also mail-centric solutions tend to also be file-centric and they add tools to manage email attachments but don't focus on making files a thing of the past. |
Some of the others listed here are not really ready or feature complete, but are added here because they share a similar vision of a unified platform to manage most of the information of your organization, using FLOSS.