When comparing Tiki vs BookStack, the Slant community recommends BookStack for most people. In the question“What are the best multi-user wikis?” BookStack is ranked 9th while Tiki is ranked 18th. The most important reason people chose BookStack is:
The stock interface design has a modern feel and is simple for new users to use.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro It's a full featured CMS
Tiki supports user-account management, permission management, allows managing menus, customizing layout, etc.
Pro Bitnami stack
Bitnami stack available for Cloud or install as Virtual machine.
Pro Lots of built-in features
Tiki includes tracker, chat, newsletter, forum and much, much more functionality out of the box.
Pro Free and open source
Tiki is licensed under LGPL.
Pro LDAP support
Pro Upgrades are smooth
Because all features of Tiki are supported by core developers, compared to a model where the wiki relies on third-party extensions that may or may not get upgraded along with the core codebase, the upgrades are a lot easier.
Pro Clean & simple default interface
The stock interface design has a modern feel and is simple for new users to use.
Pro Free and open source
Released under the MIT license.
Pro Full role and permissions system built in
Granular permissions can be set up for specific roles on a per-content basis and permissions will waterfall down to child content.
Pro Multilingual
Over 9 different languages are built in to BookStack which can be set at a per-profile level.
Pro Feature rich and stable
Markdown editing, syntax highlighting, WYSIWYG, keyboard shortcuts, versioning, SSO, LDAP, different roles, performant and fast developer response.
Pro Support for domain authentication
Can be deployed within an active directory environment with its features to connect over LDAP.
Pro Supports SSO using Google Apps
Very convenient when you're a company that uses Google Apps, that makes logging into Bookstack more secure and more convenient.
Cons
Con Can feel bloated
Since there's so much stuff in Tiki already built-in, it can be overwhelming if all you need is a simple wiki.
Con Limited customisability
Customisation options are limited with only the main theme color, logo and name being customisable.
Con No support for readable markup languages
The content entered through the WYSIWIG editor is stored as HTML. The HTML can be edited directly, but no other markup language is parsed. Speak ReST, Markdown, etc.
Con Limited to 2 levels of content
Bookstack implements a "Book / Chapter / Page" system which works fine, but lacks flexibility when you need to have more levels of imbrication.
Con Complicated installation
The current installation process involves many steps and may be a lot to take in for people not familiar with setting up Laravel applications.