WikiSuite | SaaS platform template

Executive summary / goal: to permit WikiSuite to be used as a template for a SaaSSoftware as a service is a software licensing and delivery model in which software is licensed on a subscription basis and is centrally hosted. It is sometimes referred to as "on-demand software", and was formerly referred to as "software plus services" by Microsoft. SaaS is typically accessed by users using a thin client via a web browser. SaaS has become a common delivery model for many business applications, including office software, messaging software, payroll processing software, DBMS software, management software, CAD software, development software, gamification, virtualization, accounting, collaboration, customer relationship management (CRM), Management Information Systems (MIS), enterprise resource planning (ERP), invoicing, human resource management (HRM), talent acquisition, content management (CM), and service desk management. SaaS has been incorporated into the strategy of nearly all leading enterprise software companies. offering. This is not just vanilla WikiSuite. Typically, a highly customized experience with domain-specific configuration / workflow and advice. Ex: ISO 9000 management platform. Typically with end user billing. x$ per month per user per service. This will be combined with WikiSuite Orchestrator

Status: planning stage

Overview:

SaaS platform template
- One part customer management (similar for all SaaS apps)
- One part the actual differentiated service
  - Can be one Tiki instance per customer (more related to intranets. Easier to spin off, better security, easier to customize)
    - And if there are diverse distinct services offered, they could also be furthermore split into different Tikis
  - Can be a common platform for all (more relevant to social networking). Tiki is missing some features for this: https://dev.tiki.org/Multi-sided-platform

Initial use case: start-ups in business incubators. Why? Many new web businesses have very similar infrastructure needs, and invest way too much time and money on them. Instead, they should re-use this platform, and focus on their market differentiator, marketing, financial viability and community management. For the incubator, this increases odds of success, and even if the startup fails, the technology is FLOSS and is available to other projects.

Tiki Trackers

The general idea is that when a feature is generic like wiki, forums, chat, videoconference or blogs: it's a feature with options from the relevant Software Components. But when it's an app/tool with a lot of variance (CRM, project management, HR management, course scheduling, etc.), we use https://tikitrackers.org/, which is designed to build database web apps. And Tiki profiles can be used to share / develop / deploy advanced configuration profiles. The tracker GUI interface permits power users and domain experts (if given permission) to tailor the app to their needs, without needing developers .

Tiki code modifications

Master Tiki for account and billing and access to slave Tiki
Each customer's data in own slave Tiki instance
Advanced configs of trackers that are on master are replicated on the slaves
- Data lives on slaves, and configs are taken from master (need migration scripts of certain changes)
- Subscribe to extra packages and special trackers and wiki pages appear.
- The override is like system configuration but goes way beyond prefs
- Perhaps we need a new concept? system trackers and system wiki pages
Federated Search can be used to aggregate data (ex.: compare my company to the average)
See also: https://dev.tiki.org/Federation

Related: Tiki as a Marketplace / multi-sided platform (another planned project)