Yes, I remember the Docker thing, but I also remember that at least the language parsers we were interested in were only supported through some kind of plugin mechanism, which the OSS version did not support, so it was useless for us, so I didn't ever bother testing it.

So basically their "open source" offering wasn't really open source, it wasn't even open core, as you had to build it yourself, the build wasn't working for a long time and even if you managed that, some languages were enterprise-only.

Nice. How to get free marketing by strapping Open Source to your product and writing a bunch of announcements.

I’ve had a few consulting companies where they (or their VCs) want to call their software open source but have no interest in community development and want to block competitors from taking any advantage of it.

I remember looking for Sourcegraph submissions on HN, their CEO's (sqs) first submission to HN was titled "Which Open Source License Should Your Project Use If You Want to Raise VC$?"

QED.

We are using an ERP system that advertises itself as open source. What it is, is a java based server (and client) which runs their own simple language (some sort of sql like language with conditionals etc) to build your business rules, processes. That bit is open (and sits in the database). You either write it yourself or pay them to do it. They even use a dongle so they can disable your instance in case of nonpayment of the yearly service fee.

It is a good product, so we're tying to put our org in a position to pay for it. But I really don't like this model of intentionally frustrating or obfuscating whether it is open source or not, or not listing/hiding what is or isn't in enterprise vs OSS versions. For example, the fact that starting off open source (assuming you succeeded running the maze of figuring out how to run it), explicitly blocked the path to goto enterprise is a shame, and seems like a bit of a missed business opportunity.

We'll probably see more of these faux OSS projects who hoped for some community/network effect from being OSS to translate into either strong donations or considerable uptake of their enterprise/cloud/managed versions go this route.

To be clear, fully support charging for and paying for SaaS. Would just like be able to know what is in front of me when making build/buy decisions.

I've tried finding out if they still offer the free tier now that the OSS is gone, because one of their employees mentioned it on Github, but failed to find anything. I can see they have a free trial. Their own website is full of broken links and contradicting information due to the frequent licensing/product changes.

I've even found a page still mentioning the OSS version and telling you how easy it is to fire it up.

They shot themselves in the foot majorly on this one.

When you realize that one of your products isn’t being heavily used and is OSS, you don’t close source it, you keep it open!

This shows that the value add of the paid product is actually worth it to customers.

Now?

Not so much.