Hacker News Reader

Comment by blueflow | Hacker News Reader

We were currently evaluating using GitPod in conjunction with our on-premise GitLab instance. This move by GitPod rugpulled the idea from us since we are handling national (non US) classified data and aren't allowed to upload that data or anything related to it to Cloud companies.

Edit: Misunderstanding, we are only evaluating GitPod, we already have a on-premise Gitlab instance.

View on HN

Have you considered Coder? We provision software development environments via Terraform on your own infrastructure for Linux, macOS, Windows, X86, ARM, and of course, Kubernetes.

Our customers include financial institutions, asset management firms, hedge funds, US government agencies, professional services and outsourcing firms, retailers, insurers, software providers, and more who also confirm what you are saying.

We are seeing a move to clouds but only when the cloud is under their control where infrastructure is locked down to meet regulatory and security requirements. One prospect we were speaking with recently signed a multi-year public cloud provider agreement, but shared it will take a couple years for their GitHub Enterprise solution to pass tech risk and information security reviews before developers can even access it...

Over at https://coder.com/blog/how-our-development-team-shares-one-g... explains how we build Coder with Coder.

If you got any questions lemme know. Our source code (AGPL) can be found at https://github.com/coder/coder

ps. We are we creators and maintainers of `code-server` btw.

> Our source code (MIT) can be found at https://github.com/coder/coder

https://github.com/coder/coder/blob/v0.13.1/LICENSE

> GNU AFFERO GENERAL PUBLIC LICENSE

Is there some licensing subtlety that I'm not seeing?

No, you aren't wrong. I fucked up whilst multi-tasking (see seperate post below). Coder/Coder is AGPL. Coder/Code-Server is MIT. Doh. Thanks for the correction have updated the post. :)

GitLab team member here.

Sorry to hear about your troubles. GitLab is working on adding remote development into the DevSecOps platform. I suggest reviewing the direction page [0] and implementation planning in the main epic [1] (with child epics and issues), and add your feedback and thoughts into the epic. (via the direction page in the 'how you can help' section [2])

[0] https://about.gitlab.com/direction/create/editor/remote_deve...

[1] https://gitlab.com/groups/gitlab-org/-/epics/7419

[2] https://about.gitlab.com/direction/create/editor/remote_deve...

Does code-server[1] meet your needs? It's self hosted and has been meeting by (albeit) hobbyist needs well.

[1] https://github.com/coder/code-server

Personally i always opposed new projects like this, since we already have a big devops stack that is taking much manpower to operate and kept running reliably. So, yes, the rugpull is not in the interest of my company, but it is in my interest because i will have less operational responsibility.

Maintainer of code-server here (:wave:). A couple days ago we did a recap of the ecosystem of code-server and how people are deploying code-server to support multiple users. See https://coder.com/blog/code-server-multiple-users

Co-founder of Nimbus here (https://www.usenimbus.com/)

We also provide a remote dev environment solutions. I think in your use case is very special as you cannot leverage any cloud providers, which can potentially make it harder for you to integrate with certain solution.

We are looking for design partners. If you like to share more and have a discussion, I am very happy to learn more about use cases and make Nimbus work for your on-prem infra.

I assume GitHub Enterprise Server would also meet the requirements for being entirely on-premise and not uploading data to the clouds?

It does meet these requirements, by force. The network topology does not allow our on-premise instance to phone home.

Reply on news.ycombinator.com