This is a multi-part blog where we’ll look at the business case around a license enforcement system from many different angles. This article will begin the discussion surrounding the initial business case for initiating a license enforcement project. Follow-on blogs will focus on measuring the return on the investment of a licensing system after implementation.
As an ISV, moving your application into the Cloud and offering it as a service is no trivial task. How software is supplied and managed for the desktop is very different than as a service. The usage and requirements of network connectivity, scaling, authentication and authorization, as examples, are all subtly different from the Enterprise model.
Once you get past the foundation of how to supply your application as a service, you need to solve the additional problems of authorization and utilization; or “Who has access to what?” and “How much are they using?”
Ever since software systems have been around, people have been working to connect them together to get added benefit. Sometimes that leads to large integrated all-in-one systems, sometimes it leads to efforts to standardise API’s and communications protocols and it almost always leads to lots of professional services.
In the cloud though, that’s changing. One of the most innovative companies I have seen is Boomi (now Dell Boomi). Their website does a better job of explaining their value proposition, but essentially it translates communications between systems – kind of like the Babel Fish (from HHGTTG), but for software.