(Additional Terms) This Testing Agreement (“Agreement”) is between GitLab Inc. with offices at 268 Bush Street, Suite 350, San Francisco, CA 94104 (“GitLab”), and either: (i) the entity electronically accepting this Agreement; or (ii) the entity on behalf of which the Testing Features are enabled, as applicable and in either case, “Customer”. This Agreement is effective as of the earlier date on which: (i) Customer clicks to accept this Agreement within the GitLab Software; or (ii...| The GitLab Handbook
Subscription Agreement This Subscription Agreement (“Agreement”) is between GitLab Inc. with offices at 268 Bush Street, Suite 350, San Francisco, CA 94104 (or, if a different corporate entity is listed as “GitLab” on an Order Form [as defined below], (“GitLab”)), and the individual or entity signing or electronically accepting this Agreement, or any Order Form that references this Agreement (“Customer”). This Agreement is entered into on the earlier of, (a) Customer clicking ...| The GitLab Handbook
GitLab is dedicated to integrating Artificial Intelligence (“AI”) throughout the software development lifecycle by responsibly incorporating AI into our comprehensive DevSecOps platform. We believe that AI features will further our Efficiency value and continue to bring significant benefits and opportunities to re-shape the way we, and our customers, work. However, we also recognize that, without guardrails, AI features may give rise to ethical concerns. We created these principles to gui...| The GitLab Handbook
(Additional Terms) These AI Functionality Terms (“Terms’’) are between GitLab Inc. with offices at 268 Bush Street, Suite 350, San Francisco, CA 94104 (or, if a different GitLab Affiliate is listed as “GitLab” on an Order Form) (“GitLab”), and the entity accepting these Terms (“Customer”). These Terms are effective as of the earlier of (a) Customer’s acceptance of these Terms within the (i) GitLab Software or (ii) via an Order Form, or (b) Customer’s use of any AI Functi...| The GitLab Handbook
This policy helps us identify unacceptable use of our services, and applies to all users of all GitLab services including those on the Free, Premium, and Ultimate GitLab tiers. We refer to “our services” throughout – this means all services (including related websites) owned or operated by GitLab. We reserve the right to take any action we feel is appropriate to enforce this policy. We may take action to prevent use of our services which goes against the spirit of this policy, even if t...| The GitLab Handbook
GitLab.com Service Availability The calculation methodology for GitLab.com Service Availability definition is in the monitoring policy. More details on definitions of outage, and degradation are on the incident-management page Historical Service Availability Year Month Availability Comments 2025 September 100.00% 2025 August 100.00% 2025 July 99.91% 2025 June 99.84% 2025 May 99.73% 2025 April 99.97% 2025 March 100.00% 2025 February 99.99% 2025 January 99.98% 2024 December 99.95% 2024 November...| The GitLab Handbook
Purpose GitLab has adopted the ISO/IEC 27001:2022 standard for our information security management system (ISMS) and ISO/IEC 42001:2023 for our artificial intelligence management system (AIMS) to provide GitLab team members, customers and community members with a high level of assurance on the robustness of our information security policies, standards and procedures, and the strength of our control environment. The purpose of this document is to define the boundaries and objectives of GitLab...| The GitLab Handbook
Here is a complete guide to everything you need to know about how to work and communicate asynchronously in a remote work environment. Learn more!| The GitLab Handbook
