'"The economics of Open Source software are fundamentally broken,"
argues Matt Klein, a senior software engineer at Lyft (who created
Envoy). Here's a heavily-condensed version of his essay on Medium:
If we take consulting, services, and support off the table as an
option for high-growth revenue generation (the only thing VCs care
about), we are left with open core [with some subset of features
behind a paywall], software as a service, or some blurring of the
two... Everyone wants infrastructure software to be free and
continuously developed by highly skilled professional developers (who
in turn expect to make substantial salaries), but no one wants to pay
for it. The economics of this situation are unsustainable and
broken...
[W]e now come to what I have recently called "loose" open core and
SaaS. In the future, I believe the most successful OSS projects will
be primarily monetized via this method. What is it? The idea behind
"loose" open core and SaaS is that a popular OSS project can be
developed as a completely community driven project (this avoids the
conflicts of interest inherent in "pure" open core), while value added
proprietary services and software can be sold in an ecosystem that
forms around the OSS...
Unfortunately, there is an inflection point at which in some sense an
OSS project becomes too popular for its own good, and outgrows its
ability to generate enough revenue via either "pure" open core or
services and support... [B]uilding a vibrant community and then
enabling an ecosystem of "loose" open core and SaaS businesses on top
appears to me to be the only viable path forward for modern VC-backed
OSS startups.
Klein also suggests OSS foundations start providing fellowships to key
maintainers, who currently "operate under an almost feudal system of
patronage, hopping from company to company, trying to earn a living,
keep the community vibrant, and all the while stay impartial..."
"[A]s an industry, we are going to have to come to terms with the
economic reality: nothing is free, including OSS. If we want vibrant
OSS projects maintained by engineers that are well compensated and not
conflicted, we are going to have to decide that this is something
worth paying for. In my opinion, fellowships provided by OSS
foundations and funded by companies generating revenue off of the OSS
is a great way to start down this path."'
argues Matt Klein, a senior software engineer at Lyft (who created
Envoy). Here's a heavily-condensed version of his essay on Medium:
If we take consulting, services, and support off the table as an
option for high-growth revenue generation (the only thing VCs care
about), we are left with open core [with some subset of features
behind a paywall], software as a service, or some blurring of the
two... Everyone wants infrastructure software to be free and
continuously developed by highly skilled professional developers (who
in turn expect to make substantial salaries), but no one wants to pay
for it. The economics of this situation are unsustainable and
broken...
[W]e now come to what I have recently called "loose" open core and
SaaS. In the future, I believe the most successful OSS projects will
be primarily monetized via this method. What is it? The idea behind
"loose" open core and SaaS is that a popular OSS project can be
developed as a completely community driven project (this avoids the
conflicts of interest inherent in "pure" open core), while value added
proprietary services and software can be sold in an ecosystem that
forms around the OSS...
Unfortunately, there is an inflection point at which in some sense an
OSS project becomes too popular for its own good, and outgrows its
ability to generate enough revenue via either "pure" open core or
services and support... [B]uilding a vibrant community and then
enabling an ecosystem of "loose" open core and SaaS businesses on top
appears to me to be the only viable path forward for modern VC-backed
OSS startups.
Klein also suggests OSS foundations start providing fellowships to key
maintainers, who currently "operate under an almost feudal system of
patronage, hopping from company to company, trying to earn a living,
keep the community vibrant, and all the while stay impartial..."
"[A]s an industry, we are going to have to come to terms with the
economic reality: nothing is free, including OSS. If we want vibrant
OSS projects maintained by engineers that are well compensated and not
conflicted, we are going to have to decide that this is something
worth paying for. In my opinion, fellowships provided by OSS
foundations and funded by companies generating revenue off of the OSS
is a great way to start down this path."'