On this page:


For each of the software solutions, there's general information (e.g. manufacturer, costs, market representation), as well as a general description ("management summary") of its functions. A classification may be made with regard to their type:

  • Complete solution: The software includes all the features for an intranet
  • Universal platform: the software "can also intranet"
  • Suite: Several software (maybe a mix of cloud and local installation) complementary functionality for intranet

Some solutions follow a best-of-breed approach as others follow a all-in-one approach. But after all considered solutions should correspond to what is considered an Intranet.

The criteria are categorized with respect to the use of the intranet (e.g.' communication', ' office/collaboration'). There are no mandatory or optional criteria as this strongly depends on the intended use by a company. Criteria are to be considered "soft" as different viewpoints may lead to different judgments on a criterion. Sometimes criteria are not fulfilled by the intranet solution itself but maybe by another solution or product from the same (or another vendor).

Unless stated differently criteria evaluation should be based on the solution's state after installation but before additional implementation of other solutions (except more or less configuration).

Many of the solutions have a history, by which they determine usage with respect to corporate culture for a (1.0 vs. 2.0) or of different applications are particularly well suited (such as CRM or CMS).

No information about a criterion just means that. The solution may or may not fulfill this criterion but there is no information for it at the given point.


  • Price (license), when possible and appropriate, price per user per month is shown
  • Maintenance fees (for e.g. updates, support)

Additional information may be given about Implementation effort (time + expenses)

For on-premise installations costs for hardware are not considered.

Architecture (infrastructure/integration)

General description of the solution's infrastructure and possible intregrations, eg.

  • On premise, cloud (SaaS) 
  • Integration of Exchange/Outlook/notes
  • Backup in portable formats (E.g., XML)
  • Tools for app development and deployment
  • Interfaces/connection E.g. ERP, CRP, BI
  • API for own development
  • Marketplace / Appstore (E.g. third-party)
  • Scalability
  • How often does the software change to a new major version (approx. very x years)
  • Migration effort with major version change (low < 10 days; 10 days <= medium >= 50 days; high >= 50 days)

Ease of use



Organisational communication

Interaction & community

Office & collaboration

Documents (files)



VendorCompany name (with link to company's homepage)
HeadquartersLocation of headquarters
Area servedCountries, continents the company offers the solution to
Number of employees 
Foundation year 
Revenue$ or € (year)


Transparency describes how instantly and transparently someone gets a complete overview of the solution, the solutions ecosystem and the company. It is important to be able to identify essential information instantly and without large additional research. Under transparency, we summarize how transparent the vendor provides information.

  • Pricing
  • System requirements (e.g. operating system, server-side scripting, databases)
  • Sources for support
  • Marketplace
  • Information about the vendor



<div id="disqus_thread"></div>
     *  LEARN WHY DEFINING THESE VARIABLES IS IMPORTANT: https://disqus.com/admin/universalcode/#configuration-variables
    var disqus_config = function () {
        this.page.url = window.location.href;  // Replace PAGE_URL with your page's canonical URL variable
        this.page.identifier =  $("[name='ajs-page-id']").attr("content"); // Replace PAGE_IDENTIFIER with your page's unique identifier variable
    (function() {  // DON'T EDIT BELOW THIS LINE
        var d = document, s = d.createElement('script');
        s.src = '//intranetcompass.disqus.com/embed.js';
        s.setAttribute('data-timestamp', +new Date());
        (d.head || d.body).appendChild(s);
<noscript>Please enable JavaScript to view the <a href="https://disqus.com/?ref_noscript" rel="nofollow">comments powered by Disqus.</a></noscript>