History: SaaS platform template

Executive summary / goal: to permit WikiSuite to be used as a template for a SaaS 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)
    • Can be a common platform for all ( more relevant to social networking )

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, 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 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
• 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)

Related links

• https://tiki.org/FLOSS+SaaS

• White-label SaaS platform