How did I suggest Tiki Wiki for intranet application?

My manager asked me to suggest a wiki software for intranet usage. Following is how I have gone
through the steps and ended up suggesting Tiki Wiki.

 Self-host / SaaS
o Decided to go with on-premise / self-host software due to the conceived risk of keeping
confidential materials in SaaS and not yet ready to open Active Directory for AuthN and
AuthZ purposes. Online search will give a good start if one wants to go in SaaS route
(example-1, example-2).
 AuthN – mechanism to securely identify users (Active Directory based)
 AuthZ – mechanism to determine what level of access a particular authenticated
user should have to secured resources (Active Directory Security Group)
o In on-premise / self-host software, decided to go with open source + self-host, which
gives benefit of cost, easy customization with community, AuthN + AuthZ and controls
the risk of secured documents.
 Many on-premise/self-host commercial software is available (e.g.: SharePoint
2016, IBM Connections v6, Intranet connections, bitrix24)
 Multi-language support is essential considering our office branches are outside USA as well.
 Software code base
o Once decided to go with Self-host + open source, wanted to narrow down on the
software code base because that will help us to customize easier with the current
engineering team without requiring them to re-skill / add extra skill for maintenance. So,
decided to go with PHP & MySQL based. Also wanted to have some active code
development either through dedicated engineers / through GitHub.
 Ref-1; Ref-2 – for comparing features
 Many were developed in Perl / Java / PHP + text file based / PHP + MySQL.
 LDAP / Active Directory
o AuthN and AuthZ are mandatory to move away from file folder based content
management to portal based.
 WikiSuite
o http://wikisuite.org is a Free / Libre / Open Source software (FLOSS) enterprise suite.
o This suite has Tiki as the core software for CMS solution. It is a stand-alone software
with support for LDAP, developed in PHP+MySQL including multiple language support.
In addition, it has great community support - AWS images and other web hosting
services.

So, suggested to go with Tiki for doing proof of concept with a small number of people to find out
whether it can support most of our primary use cases for intranet or not.