I understand why they've done it, but I now consider this DOA. Open source without self hosting capability is just crowdsourcing your engineering team. Documented and supported or bust. The cloud is a prison.
I'm a random developer that would be using it currently for local use.
I cannot/will not consider a solution that results in you directly managing or hosting my code/projects. I know many companies that would also take issue because of this.
Also I understand you're pivoting your customer base to enterprises and not the random hobbyist - but obviously I cannot afford enterprise pricing.
That's why many of us are sad to see this no longer be an option for us.
We've been working on platforms in sensitive environments that cannot run in public cloud due to compliance requirements, so we have been transitioning our traditional on-premises solutions to private clouds with modern capabilities where the goal is to provide a great developer experience. We had plans on using Gitpod's on-premises solution, but with this change it is no longer an available option for us.
Maybe I am misunderstanding but I think they are ending commercial support for self-hosted and the source is still available and you can run it if you want to?
With a project like this, it doesn't matter if it's technically open source if they don't make it practical to self host intentionally. There are so many components and nuances in such a complicated system that figuring it out or documenting it yourself through reading source is again, free engineering work for them.
Not supporting self-hosting is a cost-based decision, saying "well I'll figure it out and do it anyway" is just encouraging companies with open source offerings to act like this. Open source is only have the equation to make something self-hostable in any practical sense, the other half being accessibility.