Driven by vendors such as Amazon, software license models in the cloud are often pay-as-you-go and/or subscription based licenses. The best known example is Salesforce.com—licensed according to the number of users on a subscription basis. This model works well for a full integrated service, or when replacing an existing (on-premise) software solution. It does not really work when you move an existing system to the cloud, if the organization would not be able to use their existing licenses anymore. As the number of cloud service providers has expanded, major ISVs have created new licensing models or adjusted existing ones to provide additional licensing flexibility.
Microsoft has created dedicated software license models for cloud service providers based on processor license (PL) or Subscriber Access License (SAL) based on the number of end users connected. Both of these are licensed on a monthly basis to service providers. Microsoft is also a cloud service provider, with payment for online services (Exchange OnLine, SharePoint OnLine, Office Live Meeting…) based on the number of users per month. IBM offers a long term billing plan or an hourly pay-as-you-go billing plan. Developers can use all its products in the cloud for a small monthly fee. Red Hat’s license fee for Rackspace cloud servers starts at $20 a month. The major benefit for enterprises is flexibility: you pay according to what you use.
One of the issues for organizations willing to move their core applications to the cloud is the existing investment in software licensing. Oracle and IBM allow organizations to move their existing licenses to the cloud with the Bring Your Own Software and License (BYOSL) program offered through the Amazon Elastic Compute Cloud (Amazon EC2). On March 30th 2011, Microsoft made the “license mobility” announcement extending product use rights for applications purchased under Volume License agreements with Software Assurance. This offer is limited to the following products: SQL Server, SharePoint Server, Exchange Server, Dynamic CRM, Lync Server (previously known as Office Communications Server) and Systems Center Servers. Starting July 1st 2011, organizations will be able to deploy applications hosted by cloud service providers using their own Microsoft licenses.
Three factors should be considered when multiple licensing models are available in the cloud:
- The number of users accessing the software.
- The number of the processors on the device hosting the application.
- Product use rights tied to virtualization or specific vendor rules for cloud computing environments. Oracle, for instance, has its own set of rules (http://www.oracle.com/us/corporate/pricing/cloud-licensing-070579.pdf )
As for Client Access Licenses, Named User Plus and processor licenses, the user based licenses are more effective for a few users and the processor based model is better for many users. Optimized management of both on-premise and in-the-cloud software licenses requires software asset management (SAM) processes and tools that track and apply license entitlements automatically.
With these different licensing offerings, the major ISVs will help drive more and more organizations to the cloud. Gartner projects that the percentage of organizations with the majority of their IT infrastructure in the cloud, or via SaaS will rise from 3% today to 43% in four years. Traditional license models are now available in the cloud through licenses already owned by enterprises—it enables them to leverage their software investment. The pay-as-you-go and subscription models are attractive for new services, infrastructure-as-a-service (IaaS), and other public cloud based offerings. It offers the flexibility needed by both service providers and end customers, minimizing risks and providing excellent benefits such as access to the latest versions of software products.
Has your organization moved to the cloud? What applications and license models are you using in the cloud computing environment?