Friday, February 13, 2009

Changing Traditional Deployment Models to Meet Customer Needs

When the business climate changes, customers (both current and potential) are looking for new and better options. Software providers need to be responsive; think outside of the box of typical client packages.

Take multi-tenancy, for instance. As many already know, a multi-tenant solution is utilized by multiple groups of people but is based on a single, shared infrastructure. An application is built to partition each group's data so that it is private, while operating on a shared system. It is a typical deployment model for software as a service (SaaS) customers. It means the software provider hosts the product, and customers access an external server to use it. The customer doesn’t need the infrastructure; IT support is provided by the software company.

To meet customer needs and to be responsive to financial concerns of potential customers, the SamePage team has developed a new and evolutionary deployment model. This week, we announced that SamePage will now offer multi-tenancy for on-premise enterprise customers. It will be most beneficial to large enterprises, umbrella organizations and educational institutions.

With a SamePage multi-tenancy, on-premise deployment, customers will be able to develop customized wikis for each of their clients and track usage and activity. They will have increased flexibility and efficiency with horizontal scaling of the wiki within their organization.

At the same time, we’ve minimized the needs of IT management by centralizing and streamlining everything into one wiki instance for a company.

The bottom line is that consolidation of wiki services into a single, centrally managed infrastructure can translate to significant cost savings. Hardware, network and IT overheads can be dramatically reduced.

It’s out of the ‘box’ of typical software delivery mechanisms, but unique times call for innovative measures.

Read more about the features: