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.

1. Russian citizens who reside in Estonia or Estonian citizens who have renounced their Russian citizenship?

I apologize if this comes across as overly intrusive, however the point is important given the current geopolitical context.

2. All good, happens to everyone!

3.1. I was referring to Customer <-> GitLab latency, we've seen a fair bit of time wasted on roundtrips :(

3.2. Noted. APAC?

1. I don't think that the color of the passport is important and I, obviously, can't list all the employees here and disclose their citizenship. I'm, personally, a Russian citizen relocated to the EU far ago.

3.1. We don't provide the GitLab hosting services, only runners + pipeline jobs. You can use self-hosted GitLab or GitLab.com with our service.

3.2. We have a few customers from this region currently, so if you're from APAC and you're interested in the service, please tell us more about your requirements:

- https://discord.com/invite/wt8GzF8aG4

- [email protected]

And one more question, could you provide an insight into how you guys handle isolation between customers? Same physical cores, etc.

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.

No offense, but is this a sock puppet account?

No, but I am clearly biased /s