Changes

| MediaWiki can be, and is, integrated with a wide variety of other systems. Most importantly for the Enterprise user, a whole open authentication framework allows MediaWiki to be integrated with just about any existing authentication system. Because MediaWiki is open source software, with rich internal and external APIs, you can see exactly how you should integrate new functionality, new systems, etc. In contrast, Confluence is a closed system that supports only what is built into the system. "If you attempt to use an unsupported or custom JDBC driver collaborative editing will fail. You must use a supported driver." <ref>https://confluence.atlassian.com/doc/database-jdbc-drivers-171742.html</ref>

 Atlassian likes to brag about how integrated Confluence is with their other systems (BitBucket, JIRA, Bamboo, FishEye, Crucible, HipChat). While it's true that these can might be integrated (<ref>On their '''own installation''' of Confluence, there is an ''[https://confluence.atlassian.com/confkb/page-and work well out -space-operations-troubleshooting-211648541.html error displaying integrated content]'' from JIRA at the bottom of the box)page.</ref>, these extra products come at extra cost. Integrating Confluence with any product that is not sold by Atlassian is a different question.

| With 32,795,351 registered users on Wikipedia alone <ref>https://en.wikipedia.org/wiki/Wikipedia:Statistics</ref>, there is a good chance your staff and new hires have used MediaWiki before. With options to edit in WYSIWYG, wiki markup, and other advanced options, MediaWiki is just as accessible and easy to use for the Sales Manager as it is for the Engineering Intern. The mobile website and other desktop clients give many ways to search, view, and edit. Technical users might find it easy to use an IDE such as Emacs or Vim to edit text files without a browser. MediaWiki has interfaces to allow you to edit from a git repository <ref>https://www.mediawiki.org/wiki/Git-remote-mediawiki</ref>, or from desktop clients like LibreOffice.

Confluence wiki no longer supports editing with wiki markup - a decision that takes away ease of use for advanced users. Advanced Search macros (filters) require a proprietary language, Confluence Query Language (CQL) <ref>https://confluence.atlassian.com/confcloud/search-724765412.html</ref>; while advanced search filters are built-in to MediaWiki |-! Search| {{Checkmark}}| {{Checkmark|no}}| MediaWiki Search is powered by ElasticSearch - which is built on top of Lucene. Several members of Elastic Co engineering contributed improvements to Lucene in 2017 <ref>https://www.elastic.co/blog/this-year-in-elasticsearch-and-apache-lucene-2017</ref>. Confluence Search is powered by Lucene, but doesn't have the breadth of syntax options and power of ElasticSearch<ref>Compare [https://confluence.atlassian.com/confcloud/confluence-search-syntax-724765423.html Confluence Search Syntax] with [https://en.wikipedia.org/wiki/Help:Searching MediaWiki Search Syntax]</ref> 

| Wiki {{checkmark|yes}} Any size group, organization or website. Public or private access. Open network or private network. Full end-to-end encryption available.| {{checkmark|no}} Smaller teams in a private LAN. SSL termination must be done at the gateway or proxy.<ref>Synchrony, the collaboration engine does not support HTTPS, so the communication within the application/data center must be done over plain HTTP. </ref> | With low standard limits on page indexing, and database pool connections <ref>In the latest [https://confluence.atlassian.com/doc/confluence-6-2-upgrade-notes-894219489.html release notes for v6.2], the default pool size for database connections is 15</ref>, you may have a difficult time making Confluencescale and perform in larger installations. On the other hand, MediaWiki can scale to just about any size given the proper resources. What's more, MediaWiki is capable of not just creating a knowledge resource, it can also be used for general purpose websites, catalogs, documentation etc.  Confluence is limited in making documentation since page titles must be unique across the whole space|-! SSL| discussion{{Checkmark}} | {{Checkmark|no}} | If you want to use SSL, [https://confluence.atlassian.com/doc/running-confluence-over-ssl-or-https-161203.html there are instructions for Confluence], but it's totally up to you, and not supported by Atlassian. MediaWiki distributions like QualityBox offer SSL encryption built-in to every site by default, using the LetsEncrypt Certificate Authority.