GitLab Hosting FAQ

Frequently asked questions about GitLabGo’s Private Cloud hosting. Find out everything you need to know about compliance, security and redundancy.

All GitLabGo environments live in Amazon Web Services (AWS), the world’s most comprehensive and broadly adopted cloud platform.

No – we do not share any of the virtual infrastructure between clients. This includes the virtual machines, storage and external IP addresses. We set up dedicated virtual Private Cloud infrastructure for every GitLabGo client.

Yes. You have full control over where in the world your data resides. Your data will never leave that specified region. GitLabGo uses Amazon Web Services, and most AWS hosting regions are available for GitLabGo hosting.

Please note that we are currently unable to provide hosting in China.

GitLabGo contractually guarantees 99.9% uptime on a month-by-month basis. This means that in an average month, you are guaranteed to have no more than 45 minutes of unscheduled downtime.

In practice, the delivered uptime across the hosted estate is usually above 99.95%.

Should your experienced uptime ever fall below the guaranteed level of uptime, then service credits will be issued and applied to your next bill.

All GitLab data (including Git repository data, merge requests, pipeline builds, artefacts and container repositories) are backed up, so that they can be restored to a fresh GitLab instance.

Backups are performed every 24 hours, during low-usage periods (such as overnight). Note that this is often also known as the Recovery Point Objective (RPO).

Backups are kept for a period of 31 days, after which they are automatically deleted.

GitLabGo hosting provides a recovery time objective (RTO) of 4 hours. This means that the worst-case recovery scenario could take up to 4 hours to resolve.

 

In practice, most recovery scenarios take significantly less than 4 hours. Also, should the worst case scenario apply, please note that you would also be eligible for service credits (see “How reliable is GitLab Go?”).

When data is restored from backup, this results in a fresh GitLab instance that contains the data from the last scheduled backup. Any data created since the last backup was performed is overwritten.

Yes, and this allows you to further protect your environment from unauthorised access.

When allow-listing is applied, then only users from your dedicated office locations or VPN gateways will be able to access your GitLabGo instance. Hackers cannot even get to the login screen of your instance.

Yes, you can bring your own domain. All you need to do is point your domain at your GitLabGo instance, and we’ll take care of the rest – including HTTPS certificates. There is no extra charge for this service.

We do not yet provide runner hosting, but are currently looking into this.

Yes, you can connect your own runners to your GitLabGo instance. The only requirement is that your runner version is compatible with the version of your hosted GitLab instance.

We currently do not provide geo-replication. However, please talk to us about your needs so that we can put a solution together that matches your requirements.

GitLabGo comes with a number of support hours included as standard.

Our highly skilled support team can help you with your GitLab questions and assist with common GitLab challenges – like connecting external users directories, GitLab permissions or configuring pipeline builds. We can even help you when you lock yourself out of your own instance.

Only GitLabGo hosting staff have access to your data – and only for the purpose of managing the environment.

When your fresh GitLabGo instance is first commissioned and handed over to you, you will notice a “support” account on your instance.

By agreement with GitLab, the GitLabGo support account does not count towards your licence limit – which means that you do not pay for a licence for this account.

You are encouraged to keep this account active, to allow GitLabGo support to assist you with any questions and challenges that you may have.

Yes. All GitLabGo staff are fully vetted and background checked, and we can even provide UK security cleared staff (on request).

By agreement with GitLab, the GitLabGo support account does not count towards your licence limit – which means that you do not pay for a licence for this account.

You are encouraged to keep this account active, to allow GitLabGo support to assist you with any questions and challenges that you may have.

Yes – GitLabGo is powered by Clearvision, a fully ISO 27001 certified organisation.

For minor releases, GitLabGo’s default policy is to perform six upgrades per year, which is included in your hosting charge. Minor upgrades are automatically applied during scheduled maintenance.

For major releases, unless you specifically request an immediate upgrade, our policy is to wait for up to 2 months before your instance is upgraded. This allows us to test major releases and assess the impact on hosted environments.

Ask us anything.

Do you have any questions about GitLab hosting that we haven’t answered here?

Ask us anything