eTouch SamePage Offers Multi-Tenancy on Premise Deployment Model
The delivery approach of a traditional on-premise product or solution is typically a single installation for each implementation you want. So if you wanted, say, completely separate wikis for departments or customers, you would install the software separately for each department. That no longer needs to be the case. eTouch now offers their SamePage enterprise wiki solution with a multi-tenancy on-premise deployment model. One installation, many wikis.

One Solution, Three Deployment Models

The eTouch SamePage wiki is an enterprise level wiki solution that provides customers and employees access a secure place to communicate, collaborate and organize their projects and other ventures. It also integrates nicely with productivity tools like MS Office, back-end databases and includes all the security necessities that any rational IT department will immediately demand.

Probably best known as a SaaS based solution, SamePage also includes an on premise version for those not quite ready to live in the cloud.

But eTouch has been listening intently to their customers and as a result are now offering a third deployment model for the SamePage wiki solution: multi-tenancy on-premise.

Multi-tenancy is a SaaS Model

That's correct. True Software as a Service (SaaS) applications are multi-tenancy. What does that mean exactly? It means that there is one copy of the application hosted on a server(s) which all customers use. Customers can only access their information -- their data and unique configuration requirements are virtually partitioned from other customers.

According to Aniruddha Gadre, CEO of eTouch Systems. "Large enterprises and umbrella organizations in particular will be able to develop customized wikis for each of their clients and track usage and activity, along with other benefits. For us, it's another service and pricing differentiator that other wiki companies don't use."

SamePage Multi-tenancy On-Premise Features

There are a number of features with this new deployment model for SamePage, many of which are also true of a SaaS solution:

Learning Opportunities

  • Increase flexibility and efficiency with horizontal scaling
  • The ability to give every department or business unit their own wiki, separately branded and secured
  • Central administration of a single instance by the IT department
  • Savings in hardware and software costs
  • Scalability and performance can be optimize for all users
  • Seamless integration with SSO services enables users to easily switch between domains (wikis)
  • The ability to offer secure extranet wikis for partners or clients


SamePage Multi-tenancy on-premise model

It's not clear how the pricing will be effected by this new deployment model. Generally you see vendors pushing on-premise solutions that are based on a single deployment/single use model. A multi-tenancy model would have to be priced differently - perhaps by wiki installed, plus a base license fee.

Regardless, if your organization wants to deploy a number of wikis and need to keep them separated, then this new offering from SamePage is definitely something to consider.

The multi-tenancy on-premise deployment model is available with version 4.1 of SamePage. Read more about the SamePage wiki and its various features and deployment models on their website.