4 ms·

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. Document

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.

numbsafari 4y ago
I completely agree. It’s a full non-starter for us to run this on someone else’s infrastructure. I was going to be looking hard at GitPod in 2023. That is now entirely off the table.
- kjksf 4y ago
  And you're going to use what instead? If the answer is "nothing" then you don't really need it so it was never on the table.
- jlandgraf 4y ago
  With your infrastructure you mean actual hardware? Bc we can run Gitpod Dedicated in your cloud account or ours, in the region of your choice.
  - mikenikles 4y ago
    What about multi-region for anyone who has a remote team?
  - thewataccount 4y ago
    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.
    - deleted 4y ago
      [deleted]
  - bosse 4y ago
    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.
  - RandomChance 4y ago
    Strict export control restrictions mean we have actually been unable to use ANY cloud provider so far. If you did run it in "our" cloud account you would still be on the hook for very expensive audits and background checks for everyone involved. It not even close to worth it :/
- frellus 4y ago
  same here :-( we do everything on-prem. Really disappointing.
spullara 4y ago
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?
- endigma 4y ago
  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.

numbsafari 4y ago

I completely agree. It’s a full non-starter for us to run this on someone else’s infrastructure. I was going to be looking hard at GitPod in 2023. That is now entirely off the table.

kjksf 4y ago
And you're going to use what instead? If the answer is "nothing" then you don't really need it so it was never on the table.
jlandgraf 4y ago
With your infrastructure you mean actual hardware? Bc we can run Gitpod Dedicated in your cloud account or ours, in the region of your choice.
- mikenikles 4y ago
  What about multi-region for anyone who has a remote team?
- thewataccount 4y ago
  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.
  - deleted 4y ago
    [deleted]
- bosse 4y ago
  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.
- RandomChance 4y ago
  Strict export control restrictions mean we have actually been unable to use ANY cloud provider so far. If you did run it in "our" cloud account you would still be on the hook for very expensive audits and background checks for everyone involved. It not even close to worth it :/
frellus 4y ago
same here :-( we do everything on-prem. Really disappointing.

spullara 4y ago

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?

endigma 4y ago
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.