Search Content

Featured Content

Content Categories

Implications of Self-, Outsourced- and OEM-Hosting

The last couple of month I've been talking to manysoftware vendorsin China and Singapore and the topic of SaaS hosting is a recurring pain point highlighted by those I met.

More often than not, my attemptto reassure them that my architecture team in Redmond is now feverishly working on SaaS hosting architecture guidance does not seem to appease their anxieties and concerns. (My previous post here described the high level architecture capabilities of a SaaS hosting platform.) I can understand their phlegmatic reactions - hosting is not a core competency for mostsoftware vendorsand it is no wonder that they are looking for alternativesother thanthelaborious optionof building their own operationalcapability.

Generallyspeaking,SaaS providersmay consider the followinghosting solutions (which can also be thought of as acontinuum of options. If you've been following my posts you should now conclude that I really like the continuum way of representing architecture decisions) :

  • Software vendor selfhost and manage their own operational environment
  • Software vendorpartially or entirely outsource hosting to 3rd party hosters
  • Software vendor OEM and license software to 3rd party hosting partners

The right endspectrum of the continuum represents a software vendor'sdecision to self-host and manage its entire operational infrastructure. The other opposite end of the same continuum represents the decision to OEM and license the SaaS solution to business partners who not only take ownership oftheoperational responsibilities, but also own the customer relationships with the application tenants.The points between the two ends of the continuumrepresent decisions to outsourceone or morecomponents of the hosting infrastructure to third party hosters. For instance, a software vendor could decide to self host and operate everything except for the billing system which it outsource to a billing solution provider.

For the rest of this post, I want toshare some thoughts onthe technical and business implications brought about by the above hosting decisions.

Whensoftware vendorsself-host, they(willingly or unwillingly)become the trusted custodian of their customers' data. The customerdata include actual business data as well as workflows and business rules thatare configuredto run the customers' business processes. The software vendor is (legally and contractually) responsible for the "well being" of the hosted customer data.

Frequently, the self-hosting software vendor is actually sitting on a gold mine of information- lots of valuable business knowledge can be mined from analyzing the stored data. For instance, if the application is an inventory management SaaS application, business intelligence about best selling products of the month and supply forecasting data can be derived by doing trend analysis on the stored data. Therefore, having access to customer's data allow the software vendor to offer valua-add services and information back to the tenants, potentially for additional fee.

Technically, itmay also be possible for the software vendor to perform cross section analysis of allthe tenants' datain order togeneralize business practices used by the clients. For instance, a CRM software vendor may be able to analyse and derive from all theconfigured workflows, patterns ofsalesprocesses with the shortest sales closing period. Such knowledge may then beusedinbusiness practicesclassesoffered by the software vendor. Of course,such usage of customer dataremains a controversial topic as many tenants will be nervous about their trade secrets being published as best practices.

Publication and resale of identifiable private dataobviously violateslegal regulations and privacy laws. However,it is debateable ifderivation of business knowledge by SaaS software vendor should be permitted, especially if the mining process is non-trivial and involvesanalyzing large samples of data. Perhaps we will see more intellectual property protection discussions around this topic when SaaS adopterssee their business practices being "popularized" through their service providers. For those who are skeptical about such practices, let me remind you that the financial industry has been capitalizing oncustomer dataand behavior for a long time. (Next time you take a class on stock market trading from an ex-broker, guess where he learned all his best dog tricks.)

The second hosting model frees the software vendor from havingto build and operate all or part of the SaaS hosting infrastructure themselves. Inmost third party hosting agreements, the software vendor would still maintain access rights to their tenants' data, so there should be little contractual restriction limiting the software vendor from pursueing the business ideas mentioned above. Practically speaking, since the hosting is outsourced to third party, there may be technical barriers that needs to be taken care of before the software vendor canhave timely access to their customers' data. For instance, the hosting provider may limit when hosted datacan be bulk replicated to adata warehouse. This isbecause the hosterneeds to consider the network bandwidth impacton other hosted software vendors when massive amount of (replication) data is being transmitted over the networks.

The third hosting modelactually involves amajorshift in the software vendor's business model. In this model, the software vendor provides the solution to their hosting partners who host and resell the solution through licensing and OEM agreement with the software vendor.Profit made is often splitin varying proportions between the software vendor and the hosting partner.A key implication hereconcerns the software vendor's access (more accurately, potential lack of access) to the tenant data.In manyOEM arrangements, the custody of the customer databelongs to the partner hosters. Obviously this shift of responsibility comes with benefits and downside for the software vendor. While the software vendor is no longer responsible for the operational availability, integrityand security of the tenants' business data, the vendor is also giving up potential opportunitiesto monetize on those data assets.

In addition to value added services that could otherwise beprovided, the software vendor may also be foregoing a channel of knowledge about the application usage and users' behavior, both of whichcan be accurately obtained through the operational environment.Furthermore,successful Websites often trial test new features by deploying and making pre-released featuresavailable publicly on the Internet. Without an operational environment, the software vendor will have tofind partner hosters who will stage and trial run itsalpha and betarelease features.

Althoughthis post mayread like I'm trying to convince you that you should be self-hosting, be assured that this is not my intent. There is really no absolute right or wrong hosting model. What's importantis thatyou as asoftware vendor understands the price and reward that comes withyour hosting decisions.

It seems like a lot of good things in this worldare bitter-sweet, and now that youare awareofthe implications, you'll have to accept that the after taste of your SaaS hosting decision is no exception.

Related Salesforce Dedupe Articles

Automated Screenshots from Command Line

Learn how to capture automated screenshots of multiple web pages from the command line in one go using the rendering engine of Internet Explorer, Safari or Google...

Read more about Automated Screenshots from Command Line...

How to Choose Your Carrot - ReachForce Book Club

This week were reading and talking about Connect Directs whitepaper How to Choose Your Carrot: Effective Lead Generation Offers for High-Technology...

Read more about How to Choose Your Carrot - ReachForce Book Club...