NikPuashkin

I'm always open to discuss any security concerns, which are based on technology. However, you started here from the toxic biased comments. If my company is 3yo, I can't make it 10yo in one day, obviously, so there's no point to discuss it seriously. The age of the company is not an objective security criteria for an engineer, that's why I referred you to the CircleCI security breche.

Regarding the paper work, it's to be done yet. New company can't start from applying for ISO 9002. If you would like to discuss the technical security aspects of the solution (there are many), you're welcome to my DM or to the channel in Discord.

Can't disagree here. If you have time and a member in your team who can cook it, own hardware is worth a shot. But should get prepared for a lot of things to cook. You still have to maximize your server utilization together with security: running containers on a single host with 128 cores works seamless only if your workloads are trusted and the amount of processes is dozens, not hundreds or thousands.

It isn't about price, it's about effectiveness, so both speed and price.

The solution is architecturally different from anything on the market, including the GitHub controller you've posted here. I guess, you didn't even open the link of the post, because there is a scroll #3, which gives you quite a detailed explanation of the service tech advantage.

Good for you. Don't you think it's good to have a choice?

Self-hosted is always good, if you can afford hosting own hardware.

That's a good question for any cloud platform. I can only say, that to make it as trustful as possible:

- we encrypt all your environment variables on-flight before they're inside the isolated KVM

- we do a network isolation of customer runners and pipeline jobs in the local network

- we don't store the stdout of your pipeline jobs

- we use ephemeral filesystem in a runtime to avoid storing any data even accidentally

Each job runs in the isolated KVM, so you have the same level of isolation like with any traditional cloud instances on AWS, GCP, etc.

Well, we're in the public comments section and here is no DM, so I'm referring to the other public channel where I can be found in person ¯\_(ツ)_/¯

We have all the contacts on the main page, but if using Discord makes it amateurish, here is the good old email: [email protected]

Thank you for your interest!

1. The company is Estonian and regulated by the EU GDPR. Founders and all employees are the residents of the EU.

2. Was some stupid bug during the latest merge, already fixed, thanks a lot for finding this!

3.1. If we talk about the latency of cluster API, such a board is in our backlog atm. However, GitLab runners are clients by its nature, so it's hard to say what the API latency gives you here. Could you please elaborate?

3.2. The hardware is owned by GPU Computing OU and is placed in Tallinn, Estonia. We're working on adding US region as well.

None of the above :) We're fully independent and host everything ourselves.