Akka Change Was To Be Expected

LightBend's use of the rights-ratchet model may have been predictable and suggests we should watch for other cases where it will eventually manifest.

The license change that LightBend applied to its Akka product last week to end its open source status was in retrospect more probable than not given the available evidence that they were using a rights-ratchet business model, just like Elastic and other before them. The rights ratchet model offers open source freedoms in the inital years of a product to secure adoption and market acceptance and then gradually removes their viability from customers as the company seeks to control their ecosystem and increase revenue.

Signs that together seem a clear warning include:

  • VC backing includes VCs who have previously advised portfolio companies to ignore the community rather than leaving money on the table.
  • Used a Contributor Agreement despite also using a license entirely suitable for use without one.
  • Change of CEO recently saw the departure of a respected open source leader who had been at the helm during the community-building years.
  • The web site does not mention open source as a customer benefit.
  • The typical 10-year cycle of the rights-ratchet model from open source to proprietary was nearly up.

Those familiar with the rights-ratchet model will undoubtedly have been preparing for the switch. Anyone else may be surprised by it - this time.