On June 1st 2019, GitLab will shut down GitHost, our hosted single-tenant offering.
We are currently not accepting new customers. GitHost will continue to operate as normal for existing customers until June 1st 2019. Any existing individual agreements that extend beyond this date will be honored.
Instead of maintaining both a shared (GitLab.com) and single-tenant managed GitLab service, we'd like to focus on GitLab.com.
GitHost will continue to operate as normal until June 1st 2019. If you'd like to maintain your GitLab instance beyond that date, you can:
Some 3rd party vendors also offer a single-tenant managed offering, such as GitLabHost.
Moving instances is currently supported by the project import/export feature. Projects can be individually exported via the web interface. An API is also available.
No, you can migrate to GitLab.com using the Free tier. You can always upgrade later if you decide you'd like the additional features of a paid tier.
Public projects on GitLab.com also benefit from Gold features for free.
See GitLab.com's pricing page for more information about GitLab.com.
Please note that some features are not supported on GitLab.com. Please see the related question in the FAQ section for more detail.
GitHost is a single-tenant solution that provides GitLab installations and CI runners as a managed service. GitLab Inc. is responsible for installing, updating, hosting, and backing up customers own private and secure GitLab instances.
GitHost will always install the latest version of GitLab when a new server is created.
No, unfortunately some features are not supported on GitHost. Specifically, the following features are not supported:
gitlab.rb file changesAmsterdam, London, San Francisco, Singapore, Toronto, New York, Frankfurt, and Bangalore.
Technically, no. Our plans are based on the underlying infrastructure templates. However, it is possible to attach an external block storage device that allows you to add up to 16TB of storage for $0.15 USD per GB per Month.
This feature is only available in our NYC1 (New York 1), SFO2 (San Francisco 2), SGP1 (Singapore), and FRA1 (Frankfurt) regions.
Yes.
Yes, if you want to use your own domain. You can purchase one from vendors such as Comodo. No, if you want a *.githost.io subdomain.
Yes.
Yes we use OmniAuth so users can sign in using Twitter, Facebook etc.
Yes.
Custom changes such as increasing the number of Unicorn workers or setting up an SMTP server for email must be done by a GitLab Service Engineer. Customers can request this by contacting GitHost Support.
SSH and HTTP.
Full backups are taken every day and stored at an offsite location. Restoring from backups can be done by customers without help from GitHost Support.
Yes, we do. And you can also hook up runners from anywhere.
Yes, you can use backup and restore but this requires the intervention of a Service Engineer.
Yes. Please see the documentation on migrating from GitLab.com.
Yes.
99.9% uptime (also see the terms).
For assistance with issues that are specific to GitHost, we offer next-business day response times. Please submit your support request through the support portal.
GitLab Enterprise subscribers will have the ability to email our Service Engineers directly for assistance with both GitHost and GitLab, and receive the benefit of the same response times and service levels that are in place for GitLab Enterprise Edition subscription.
Subscriptions plans are prorated to the nearest minute and charged monthly.
Yes. Please contact our sales team.
Please submit your request for technical support through the support portal.