Paradraw
GitLab/GitLab Testing Agreement reads as a commitment, but nothing incorporates it into the agreement
GitLab Terms of Use · p39
Part of the agreement

GitLab Terms of Use

797 words, 50 clausesno date on the pageread 12/10/2026source

·GitLab Terms of Use

·The CURRENT TERMS OF USE (unless otherwise stated in the Table below) shall apply to (1) Customers solely using Free Software and (2) net-new and renewal purchases made on, or after, January 12, 2026. If you received an Order Form / Quote, or purchased, prior to January 12, 2026, please see the Agreement History below for the terms applicable to your purchase and/or use of GitLab software. Any GitLab Subscription purchased prior to January 12, 2026 including upgrades and additional Users purchased for that Subscription, will be governed by the Agreement in effect as of the Subscription purchase date.

·Current Terms of Use
Type of Use / ActivityApplicable Agreement
Use of any GitLab Software Offering, including Free tierSubscription Agreement
Additional Terms: Use of any GitLab Professional Services Use of any AI Functionality Use of any experimental or beta feature Agile Planning Terms EU Data Act Supplemental TermsProfessional Services Terms GitLab Duo AI Terms (formerly known as AI Functionality Terms) Testing Agreement Agile Planning Terms EU Data Act Supplemental Terms
Privacy StatementGitLab Privacy Statement
GitLab Processing Personal Data from an EnterpriseGitLab Data Processing Addendum and Standard Contractual Clauses
Request Removal of Content / DataDMCA Notice and Take Down
Use of GitLab's Website(s)Website Terms of Use
Cookies & Visiting the WebsiteGitLab Cookie Policy
External Contributions to the GitLab BlogExternal Blog Submissions Terms
Use of any GitLab services, including Software, AI Functionality, Website(s), etc.Acceptable Use Policy
Using GitLab's publicly-available APIsGitLab API Terms of Use
Partner ProgramTo enroll please visit the GitLab Partner Program Portal
GitLab Reseller / Referral PartnerMaster Partner Agreement
GitLab Integration AgreementTechnology Partner Agreement
GitLab for Education Program*GitLab for Education Program Agreement
GitLab for Open Source Program**GitLab for Open Source Program Agreement

·*Only applicable for Educational Institutions using GitLab Software for Instructional Use, or, Non-Commercial Academic Research. Please visit Program Guidelines for more information.

·**Only applicable for Open Source Organizations using GitLab Software for Open Source Software. Please visit Program Guidelines for more information.

·Agreement History

·GitLab, including GitLab Legal, is committed to transparency as part of its' values, as such we provide previous versions of our Agreements.

Legacy Agreement and Applicable DatesAgreement Location
Privacy Statement (March 19, 2024 - April 22, 2026)Legacy Privacy Statement V2
Privacy Statement (June 10, 2022 - March 18, 2024)Legacy Privacy Statement V1
Data Processing Addendum and Standard Contractual Clauses (May 20, 2024 - April 30, 2026)Legacy Data Processing Addendum and Standard Contractual Clauses
Subscription Agreement (November 12, 2025 - January 11, 2026)Legacy Subscription Agreement V7
Subscription Agreement (August 30, 2024 - November 12, 2025)Legacy Subscription Agreement V6
Subscription Agreement (August 14, 2023 - August 29, 2024)Legacy Subscription Agreement V5
Subscription Agreement (September 07, 2022 - August 13, 2023)Legacy Subscription Agreement V4
Subscription Agreement (August 1, 2021 - September 06, 2022)Legacy Subscription Agreement V3
Subscription Agreement (February 1, 2021 - July 31, 2021)Legacy Subscription Agreement V2
Subscription Agreement (January 1, 2015 - January 31, 2021)Legacy Subscription Agreement V1
Professional Services Agreement (August 30, 2024 - March 5, 2025)Legacy Professional Services Agreement V3
Professional Services Agreement (November 1, 2021 - August 29, 2024)Legacy Professional Services Agreement V2
Professional Services Agreement (January 1, 2015 - October 31, 2021)Legacy Professional Services Agreement V1
GitLab for Open Source Program Agreement (February 24, 2021 - August 19, 2022)Legacy GitLab for Open Source Program Agreement V1
Testing Agreement (February 28, 2025 - May 19, 2026)Legacy GitLab Testing Agreement V5
Testing Agreement (August 30, 2024 - February 28, 2025)Legacy GitLab Testing Agreement V4
Testing Agreement (June 30, 2023 - August 29, 2024)Legacy GitLab Testing Agreement V3
Testing Agreement (May 19, 2023 - June 29, 2023)Legacy GitLab Testing Agreement V2
Testing Agreement (April 10, 2023 - May 18, 2023)Legacy GitLab Testing Agreement V1
AI Functionality Terms (April 1, 2025 - November 12, 2025)Legacy AI Functionality Terms V4
AI Functionality Terms (August 30, 2024 - March 31, 2025)Legacy AI Functionality Terms V3
AI Functionality Terms (November 1, 2023 - August 29, 2024)Legacy AI Functionality Terms V2
AI Functionality Terms (August 14, 2023 - October 31, 2023)Legacy AI Functionality Terms V1
Agile Planning Terms (October 17, 2023 - August 29, 2024)Legacy Agile Planning Terms V1
Master Partner Agreement (May 16, 2023 - August 28, 2025)Legacy Master Partner Agreement V1
Technology Partner Agreement (February 1, 2022 - March 30, 2026)Legacy Technology Partner Agreement V1
GitLab Testing Agreement · gitlab testing agreement
Part of the agreement

GitLab Testing Agreement

1,650 words, 32 clausesupdated May 20, 2026read 12/10/2026source

·GitLab Testing Agreement

·(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) an individual acting on behalf of Customer opts to enable the Testing Features ("Effective Date"). The parties agree to the following terms and conditions related to Customer's use of the applicable Testing Feature (as defined below).

·An individual opting to enable the Testing Features represents that they have the authority to bind Customer to the terms of this Agreement. If the individual does not have such authority, they must not opt to enable the Testing Features or otherwise disable such Testing Features.

11. DEFINITIONS

1.11.1. "Testing Feature(s)" are experimental, alpha, or beta features that are not ready for production use. Testing Features are provided without, or with limited, support, as determined in GitLab's discretion. Additional details and applicable use terms incorporated herein by reference are further described here: https://docs.gitlab.com/policy/development_stages_support/.

1.21.2. "AI Assisted" means the use of, or development of, work product with the assistance of artificial intelligence (including machine learning).

1.31.3. "Generally Available Features" are Software features that are ready for production use at any scale, are fully documented and supported, and have passed the Production Readiness Review.

1.41.4. "Personal Data" means all information defined in the definition of "personal data" under General Data Protection Regulation (EU) 2016/679.

1.51.5. "Production Readiness Review" is a process that helps identify the reliability needs of a service, feature, or significant change to infrastructure for GitLab.com.

1.61.6. "Testing Period" is the period of time Customer has access to the Testing Feature, as determined at GitLab's discretion, for testing, evaluation, and Feedback (as defined below).

22. LICENSE, SCOPE, AND USE OF THE TESTING FEATURES

2.12.1. Subject to the terms of this Agreement, GitLab grants Customer a non-exclusive, non-transferable license to use the applicable Testing Feature(s) for internal use. Testing Features are governed as Free Software (as defined in the GitLab Subscription Agreement ("GLSA") available at https://about.gitlab.com/handbook/legal/subscription-agreement/ and incorporated herein), subject to the applicable provisions of the GLSA (including, but not limited to, GLSA §§ 5, 7, 10.2, 14.2). Notwithstanding the foregoing, certain Testing Features may incur fees based on use, as described in the Documentation for the applicable Testing Feature and at https://docs.gitlab.com/subscriptions/gitlab_credits/. Capitalized terms not defined herein will have the meaning in the GLSA.

2.22.2. Customer acknowledges that the applicable Testing Feature: (i) has not been made commercially available, (ii) may be unstable and could cause performance and stability issues, (iii) may not operate properly, and (iv) may contain errors, design flaws or other problems. GitLab is under no obligation to release a Testing Feature as a Generally Available Feature.

2.32.3. To the extent a Testing Feature involves the processing of Customer's Personal Data, Customer agrees and represents that it has provided all required notices to, and obtained all necessary consents from, the data subjects whose Personal Data is processed under a Testing Feature. GitLab will process Customer's Personal Data on the basis of performing this Agreement with Customer. Any sub-processors used to provide a Testing Feature will be listed at https://about.gitlab.com/privacy/subprocessors/ and all notifications of updates to that list will be done in accordance with Section 14 of the data processing addendum as set forth in the GLSA.

2.42.4. Customer's use of and access to the applicable Testing Feature is solely at its own risk. Customer acknowledges that: (i) it is responsible for any AI Assisted work product (including source code) generated using the applicable Testing Feature, including: (a) verifying the suitability and accuracy of any AI Assisted work product for the desired purpose, and (b) any suggestions Customer may incorporate from AI Assisted Testing Features or any suggestions to Customer's work product; and (ii) the Testing Feature(s) may cause unexpected results, corruption or loss of data, or other forms of loss or damage. Customer will not copy, alter, modify, reverse engineer, or attempt to derive the source code of the Testing Features.

2.52.5. The Testing Period shall commence upon the Effective Date and will automatically expire upon the earlier of (i) the conclusion of the Testing Period, or (ii) GitLab providing the applicable Testing Feature as a Generally Available Feature. If GitLab transitions a Testing Feature to a Generally Available Feature, Customer's continued use will be subject to applicable fees and commercial terms as governed by the GLSA available at https://about.gitlab.com/terms/, or such other separate written agreement between the parties governing use of GitLab Software, inclusive of a Generally Available Feature.

2.62.6. GitLab will retain all ownership and intellectual property rights related to GitLab Software, the Testing Feature(s), and any Feedback related thereto. Customer may provide input to be processed by the Testing Features ("Input"), and receive output generated and returned by the Testing Features based on the Input ("Output"). To the extent permitted by applicable law, both Input and Output shall constitute Customer Content as that term is defined in the GLSA.

33. FEEDBACK

·As part of Customer's use, testing, and evaluation of the applicable Testing Feature, Customer may provide suggestions, ideas, enhancement requests, or other recommendations ("Feedback") regarding its use of the Testing Feature and hereby irrevocably assigns all rights in such Feedback to GitLab. The parties will mutually agree (email is sufficient) on an appropriate cadence, process, and method of exchanging Feedback during the Testing Period, including use of public GitLab issues. GitLab may use any Feedback without restriction and without obligation to Customer.

44. CONFIDENTIALITY

·The parties acknowledge and agree that Confidential Information disclosed under this Agreement is subject to the confidentiality obligations of the GLSA or other applicable confidentiality agreement between the parties. GitLab Confidential Information includes, but is not limited to, Testing Features and any Feedback.

55. NO WARRANTIES

·CUSTOMER EXPRESSLY ACKNOWLEDGES AND AGREES THAT THE APPLICABLE TESTING FEATURE LICENSED HEREUNDER IS STILL IN THE TESTING PHASE, MAY CONTAIN DEFECTS, AND IS PROVIDED ON AN "AS IS" AND "AS AVAILABLE" BASIS. THE PRIMARY PURPOSE OF THIS AGREEMENT IS TO OBTAIN FEEDBACK ON PERFORMANCE AND THE IDENTIFICATION OF ANY DEFECTS OF THE TESTING FEATURE. CUSTOMER MUST SAFEGUARD IMPORTANT DATA, USE CAUTION, AND NOT RELY IN ANY WAY ON THE CORRECT FUNCTIONING AND PERFORMANCE OF THE TESTING FEATURE. GITLAB AND ITS LICENSORS DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, ALL IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. NO INFORMATION OR ADVICE, WHETHER ORAL OR WRITTEN, PROVIDED BY GITLAB DURING THE TESTING PERIOD SHALL CREATE ANY WARRANTY NOT EXPRESSLY MADE HEREIN.

66. LIMITATION OF LIABILITY

·TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, (I) IN NO EVENT WILL GITLAB BE LIABLE TO CUSTOMER FOR ANY INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES, LOSS OF REVENUE, LOSS OF DATA, ANTICIPATED PROFITS, LOST BUSINESS OR LOST SALES, WHETHER BASED IN CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, OR OTHERWISE, EVEN IF CUSTOMER HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES; (II) THE TOTAL LIABILITY OF GITLAB ARISING OUT OF OR RELATED TO THIS AGREEMENT, WHETHER BASED IN CONTRACT, TORT (INCLUDING NEGLIGENCE OR STRICT LIABILITY), OR OTHERWISE, WILL NOT EXCEED, IN THE AGGREGATE, USD $1,000.00. THE FOREGOING LIMITATIONS WILL APPLY NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL GITLAB BE LIABLE TO CUSTOMER (OR ANY THIRD PARTY INCLUDING CUSTOMER'S USERS OR LICENSEES) FOR ANY MISAPPROPRIATION, INFRINGEMENT, DILUTION OR OTHER VIOLATION OF THIRD-PARTY INTELLECTUAL PROPERTY RIGHTS ARISING OUT OF, OR IN CONNECTION WITH, CUSTOMER'S OR ITS USERS: (A) USE OF THE TESTING FEATURE, OR (B) USE, COMMERCIALIZATION, COPYING, MODIFICATION, PUBLICATION, DISTRIBUTION, LICENSING, SUBLICENSING, OR, AS APPLICABLE, SALE OF AI ASSISTED WORK PRODUCT GENERATED BY THE TESTING FEATURE.

77. TERMINATION

·Upon written notice to the other party (email is sufficient), either party may terminate this Agreement immediately for convenience. In the event the Testing Period has concluded or the Testing Feature becomes a Generally Available Feature, Customer acknowledges that continued use of the Testing Feature will be subject to additional fees and the GLSA or separate written agreement between the parties governing use of GitLab Software. Upon expiration or termination of this Agreement, all licenses granted herein shall automatically terminate and Customer shall immediately discontinue all use of the Testing Feature. Sections 2.5, 4, 5, 6, and 7, shall survive any termination or expiration of this Agreement.

88. MISCELLANEOUS

8.18.1. Except as otherwise provided in Section 2, this Agreement and the references incorporated herein comprise the complete statement of understanding of the parties and supersede and cancel all previous written or oral agreements, communications, and other understandings relating to the subject matter herein. Any conflict of terms with the GLSA shall be resolved in favor of this Agreement. This Agreement does not provide Customer a commercial license to use the Testing Feature once transitioned to a Generally Available Feature.

8.28.2. This Agreement is governed by the laws of the State of California, without regard to its conflict of laws provisions. The federal and state courts sitting in San Francisco County, California, will have proper and exclusive jurisdiction and venue with respect to any disputes arising from or related to this Agreement. The United Nations Convention of Contracts for the International Sale of Goods is expressly disclaimed by the parties with respect to this Agreement. The parties represent, warrant and covenant to adhere to all applicable laws and regulations including all export and trade compliance requirements. This Agreement is not assignable, transferable or sublicensable by either party without the other party's prior written consent.

·Last modified May 20, 2026: Update testing agreement and add legacy file (9c9651fc) View page source - Edit this page - please contribute.