Big Open Source
May 2023 - Alex Alejandre

tl;dr: Open source is a moat for big tech. SaaS is the best startups can do right now.


We all love open source (far better than 500 line DLLs with license codes). Our modern ecosystem offers accelerated innovation, transparency, security and all the good stuff. But there are problems today:

  • Donating is easy, but people don’t want to pay The space is still developping. Thanks.dev looks best atm. (and I criticize big tech when it finally pays.)
  • Corporate open source becomes a vendor onramp.
  • The community shames selective licenses (AGPL/EUPL/Commons Clause) which limit larger entities from using without contribution. Relatedly, contributors often get brigaded by community entitlement and don’t say ‘No’ enough.

Today, profitable companies control decision making (what to add/exclude) in key projects, not the community. This gravity pulls projects towards extreme complexity, specialized for scale beyond what most companies will ever see - with all users paying the complexity burden. (Google’s code isn’t sufficient.) In effect Kubernetes et al. are memetic weapons, devouring mindshare and seducing the competition to lower velocity by overengineering and burning capital.

Interesting dynamics play out between big companies though. While Amazon stripmines open source to make it consumable via AWS products/features, Google champions multicloud (Kubernetes), great for a new cloud provider fighting for marketshare (against platformlocking competition.)

Standards setting 1 is another key battlefield. We already saw open standards fail. Now, open source victors standardize 2 domains on a single framework and API, a new sort of regulatory capture.

There are some nice developments like EU organs praising open source as source of independence from American vendors or the German government moving to the Libre office suite, but this doesn’t result in funding to existing projects. Where we stand, the best a fan of a new company can do is emulate the big guys and try to capture its own space but it doesn’t always work.


Update April 11, 2024: Cases like opentofu illustrate a different dynamic with even larger startups, where defensive opensourcing leads to a free-beer alternative copypasting features on a 1:1 basis (after their move to business source.). We must wait to see whether this result in a crab bucket situation, dissuading new companies from open source, killing off Hashicorp’s investment and development of Terraform etc. Opentofu issues show a request before HashiCorp’s implementation appeared, making this particular case less clear.

Updated April 11, 2024: Opentofu poses a partial counterexample, where Hashicorp’s SaaS offering is scalped by a free-beer alternative emulating it on a 1:1 basis (in response to the move to business source.) If this keeps happening, we’ll have a crab bucket situation, dissuading new companies from open source, entirely. (I have no idea what that would do to today’s SaaS exosystem though.) Opentofu issues show a request before HashiCorp’s implementation appeared, making this particular case less clear.

Updated April 27, 2024: Looking into it deeper, a clear picture’s already forming. Besides Hashicorp’s move to business source (and IBM buyout), Redis, MongoDB, Cockroach, Sentry etc. moved to source available… When this happens, open forks appear.

But who should operate and generate revenue from these open forks?


Sources:

  • The Relationship Between Open Source Software and Standard Setting - Knut Blind, Mirko Böhm

  • Standard-Setting Organizations: Patents, Price Fixing, and Per Se Legality - Patrick D. Curran

  • https://github.com/opentofu/opentofu/issues/299