Sustainability

·Sustainability

·Information and processes related to Sustainability and ESG

·Quick links

• ·To learn more about Sustainability at GitLab, please take our Sustainability Training course available on LevelUp and in the Handbook
• ·Join the #sustainability-esg Slack channel to follow along for updates, ask questions and provide feedback
• ·Customer asking ESG-related questions? Follow the steps outlined in the Requesting Support with Customer ESG Questions section below Sustainability Programs

·Corporate Sustainability is a business approach that enhances long term stakeholder value by implementing a strategy that considers every dimension of how a business operates when making social, environmental and economic progress.

·ESG stands for Environmental, Social and Governance and refers to the three key factors when measuring the sustainability and ethical impact of an investment in a business or company.

·At GitLab we use Sustainability and ESG interchangeably. Both terms are relevant to our work and both serve different purposes depending on the audience we interact with.

·Team Overview & Vision

·The Sustainability Team creates and maintains GitLab's Corporate Sustainability strategy and programs by driving and integrating responsible business practices and ESG regulatory compliance.

·The Sustainability team builds and maintains strong internal and external relationships to understand stakeholder expectations - including customer, investor and team members. This engagement allows us to remain customer centric and easy to do business with while meeting shareholder and team member expectations.

·The Sustainability Team has two primary functions and four corresponding programs:

·Compliance, Reporting & Climate Action

• ·Compliance & Reporting: Manages customer and prospect ESG-related questionnaires, requests for proposals, and sustainability contractual clauses. Leads annual Sustainability report and external assurance process. Monitors global ESG regulation and works cross-functionally to advance GitLab's culture of compliance with applicable ESG regulations. Responds to investor ESG rating agencies to maintain competitive ESG scoring among peers.
• ·Climate Action: Identifies and executes strategic climate programs, including annual measurement of GitLab's greenhouse gas inventory, emissions reduction target-setting, partners with Procurement to run the sustainable supplier program, identifies emissions reduction opportunities across the business, and purchases high quality carbon credits. Manages team member & customer communications related to GitLab's commitment to environmental sustainability.

·Social Impact

• ·GiveLab: GiveLab is GitLab's team member volunteer program and includes year-round volunteering, GiveLab 30 days of Impact, our annual company-wide volunteer campaign and GiveLab Champions Program. Volunteerism is an effective way to build trust through social connections - this leads to higher individual and team motivation, and greater cross-functional collaboration.
• ·GitLab for Non-Profits: GitLab's in-kind donation program. Manages social impact communications with team members and customers, while developing strategic nonprofit partnerships to advance GitLab's ESG goals and help enhance our brand reputation by demonstrating our commitment to the nonprofit community.

·Sustainability Strategy

·GitLab's Sustainability Strategy is driven by our commitment to delivering results for our customers while creating lasting value for all of our stakeholders. As our company has grown, so has our commitment to integrating sustainability throughout the business to drive innovation and contribute to a more sustainable future. We will continue to work in partnership with our stakeholders to unlock new opportunities to create value for our customers, partners, investors, team members, and communities.

·those material topics drive the programs, policies and initiatives under our strategy. Our double materiality assessment validated our focus on the following key sustainability topics, organized by theme:

·Trust and Transparency: Information Security and Data Privacy, Responsible Product Development, and Business Ethics Planet: Climate Action

·People and Communities: Talent and Engagement, Diversity, Inclusion and Belonging, and Social Impact

·Sustainability Oversight

·Board: The Nominating and Corporate Governance Committee oversees company programs relating to corporate responsibility and sustainability. Sustainability topics are reviewed at least twice per year with the committee, and with the full Board as needed.

·Sustainability Leadership: The Senior Director of Sustainability reports to the Chief Legal Officer (CLO) and Head of Corporate Affairs on an ongoing basis and updates GitLab's senior executives as needed.

·Advisory Committee: GitLab's Senior Director of Sustainability maintains an internal Sustainability Advisory Committee. This committee is a cross-functional leadership group that provides feedback on sustainability objectives, communicates sustainability information across the business, and supports regulatory and voluntary sustainability reporting.

·ESG | Sustainability Programs

·Compliance & Reporting

·Like all functions at GitLab, transparency is a core focus. Every year GitLab publishes an annual sustainability report where we share our approach to managing our key sustainability focus areas, provide updates on programs and policies, achievements to date, metrics and targets, and plans for the future.

·View our latest Sustainability Report.

·The Sustainability team works cross-functionally to prepare GitLab for compliance with ESG regulations.

·The Sustainability team also supports internal teams with customer ESG questionnaires and RFPs. Customers and prospective customers are increasingly asking about GitLab's Sustainability programs, including questions related to GitLab's climate commitments and greenhouse gas emissions. Many of our customers are also subject to ESG regulation and we expect customer ESG questions to continue to increase as they look to better align to new regulations.

·Requesting Support with Customer ESG Questions

• ·If a customer or potential customer has questions related to GitLab's ESG practices as part of an RFP, please follow the RFP process
• ·If a customer or potential customer requests information via an ESG questionnaire, please open an issue here and select the 'ESG Questionnaire' template
• ·If there's an opportunity to connect the Sustainability team directly, please reach out in the #sustainability-esg Slack channel

·Climate Action

·GitLab is committed to doing our part to minimize our environmental footprint, including working to reduce greenhouse gas (GHG) emissions associated with our operations. GitLab's stakeholders, including customers, investors, regulators, and team members expect the company to operate sustainably and to do our part to reduce our environmental footprint.

·Many of GitLab's customers have GHG reduction targets and as a vendor, GitLab's carbon emissions contribute to our customers' emissions footprints. To remain easy to transact with, GitLab needs to meet the expectations of our customers by taking action on climate change.

·GitLab's Climate Action Program consists of four pillars:

• 1Measure & Report: Every year GitLab conducts an annual greenhouse gas (GHG) inventory in alignment with the GHG Protocol, the global best practice carbon accounting standard. We publish the results of the inventory in our annual ESG report and have the data assured by a third-party.
• 2Act: GitLab is taking action to reduce our carbon emissions. As a fully remote software company, the majority of our emissions come from our suppliers. Engaging our suppliers to measure their carbon emissions and set their own reduction targets is a critical component of our reduction pathway, which is why we have set an aspirational supplier engagement target. Please see the Sustainable Procurement Program for more information. The Sustainability team continues to explore other ways to reduce emissions and is doing further analysis on additional reduction pathways.
• 3Engage: This includes engaging GitLab team members in climate education and action. In 2024, we launched the GitLab Team Member Sustainability Guide, providing actionable steps team members can take at home to minimize their environmental impact. In FY26, we launched our partnership with Mammoth Climate, a climate literacy and challenges platform, to further engage team members with educational materials, activities, and rewards
• 4Accelerate: While GitLab works to reduce our emissions, we are also committed to accelerating climate solutions by purchasing high quality carbon credits to cover a portion of our carbon footprint. We are proud to partner with Rubicon Carbon to purchase a diversified portfolio of high quality carbon credits, financing carbon removal projects that meet Rubicon's high standards of quality.

·Sustainable Procurement Program

·In FY25, GitLab set an aspirational science-aligned supplier engagement target to reduce our Scope 3 emissions: 70% of our suppliers (by emissions) will have science-aligned climate targets by FY29.

·Our sustainable procurement program includes the following initiatives:

• ·Annual emissions survey to request data from suppliers in an effort to improve the accuracy of our footprint
• ·Use strategic business reviews to understand key barriers suppliers face when measuring and reporting their emissions
• ·Provide resources and training to suppliers on how to measure and reduce their greenhouse gas emissions
• ·Provide resources and training to team members responsible for supplier selection on our new expectations of suppliers, aligned with applicable laws.

·We look forward to sharing updates on this new initiative.

·GreenDevOps

·The Green DevOps Working Group at GitLab aims to embed sustainability throughout the software development lifecycle to reduce environmental impact while unlocking operational and business value.

·Its core objectives include lowering carbon emissions and energy use, integrating green practices into business processes, enhancing customer capabilities to meet regulatory and sustainability goals, and positioning GitLab as a leader in sustainable DevOps and green software.

·Workstreams address areas such as cloud sustainability, CI/CD energy consumption tracking and reduction, community innovation and engagement, sustainable AI and procurement, and reporting. Each workstream is led by the Sustainability team and the relevant functional team member.

·Customers who are interested in providing insights and feedback on sustainability features are encouraged to contact the Sustainability Team at esg@gitlab.com for more information.

·GiveLab

·At GitLab, all team members do work that supports the company, which supports the enhancement of an open source codebase. This codebase is freely available to everyone to make better software faster and drive progress through what they build.

·But, there are also other ways to give back and many team members choose to contribute beyond GitLab. In addition to contributing to GitLab, GitLab offers additional optional pathways for team members to give back while leveraging their unique skills and passions through programs such as GiveLab, GitLab's Team Member Volunteer Program.

·GitLab encourages team members to take part in volunteer initiatives such as supporting their local communities, participating in virtual volunteer activities, and organizing volunteer activities as part of team events. Corporate volunteerism has been proven to be an effective strategy for boosting engagement, improving employee retention, and strengthening relationships at work. Volunteering with GiveLab supports team members in fostering connections and building trust among one another while positively impacting our communities.

·As of June 2026, GiveLab is a self-service program - teams are encouraged to identify volunteer opportunities that resonate with them and organize activities on their own. To get started:

• 1Browse the GiveLab Nonprofit Directory. Start by exploring the GiveLab Nonprofit Directory to find registered nonprofit organizations that align with your team's interests. The directory is a curated list of vetted organizations across a variety of causes and geographies.
• 2Choose an activity. Decide whether your team wants to volunteer in person locally or participate in a virtual activity. All in-person volunteering must be local to team members - travel to volunteer events is not reimbursable.
• 3Coordinate your event. Reach out to the nonprofit directly to confirm your team's participation and coordinate logistics.
• 4Open an issue to confirm the nonprofit meets GitLab's philanthropy policy requirements. Use the Volunteer_Support Template.
• 5Submit eligible expenses. Team members may expense up to $25 per volunteer event for eligible expenses. Submit in Navan using the "GiveLab" classification.

·If a team member is organizing a large group activity with more than 15 team members, the organizing team member may request support from the Sustainability Team to organize local or virtual volunteer opportunities on their behalf by going to the Philanthropic Requests epic and opening a new issue using the Volunteer_Support Template. Please write "yes" for the question, "Would you like the Sustainability team's help organizing the volunteer activity?" If resources allow, the Sustainability team may be able to connect organizers with a third-party service to help coordinate the activity. However, please note that any costs associated with third-party coordination or the event itself would need to be absorbed by the organizing team's budget.

·All team members and volunteer activities must adhere to the GitLab Philanthropy Policy. Team members must follow GitLab's paid time off (PTO) policy if volunteering during work hours and use the "public service/volunteer" option in Workday.

·If volunteering in person, team members may incur some expenses. Team members can expense up to a total of $25 per volunteer event for expenses incurred that meet the allowed for reimbursement criteria. All expenses should be submitted in Navan using the "GiveLab" classification. Please note that GitLab does not allow team members to travel to in-person volunteer events. All in-person volunteering should be local to the team member.

·As with all company expenses, team members must be thoughtful in spending the company's money and use best judgment to ensure that all expenses are deemed "ordinary and necessary." Team members should follow all team member expense responsibilities.

·Expenses allowed for reimbursement (for in-person volunteer events):

• ·Local travel only - mileage, train, taxi/rideshares. Must follow and comply with the current limits of our Expense Policy. Code under their individual travel category and use the "GiveLab" classification in Navan
• ·Parking for the event. Must follow and comply with the current limits of our Expense Policy. Please use the "GiveLab" classification in Navan
• ·Meal during the event. Must follow and comply with the current limits of our Expense Policy. Code under Travel-Meals for Myself and use the "GiveLab" classification in Navan

·Expenses not allowed for reimbursement:

• ·Any airfare, lodging, rental cars, coworking space, internet expenses are not allowed
• ·Any supplies or items needed for the event Donations to the nonprofit
• ·Any expenses that are not mentioned as "allowed" above are not reimbursable and there will be no exceptions

·As with our unique ways of working, GitLab and its team members have identified and sought out opportunities for impact that speak not only to our values but also to our all-remote nature. To review previous opportunities that team members participated in, visit the historical activities page.

·GiveLab 30 Days of Impact

·GiveLab 30 Days of Impact is GitLab's annual volunteer campaign created to encourage team members to foster connections, build trust among one another and embody our CREDIT values while positively impacting our communities. We have designed this program with our high-performing team culture and results for customers in mind.

·GiveLab 30 days of Impact runs annually in Q4 and our goal is to encourage as many team members as possible to volunteer over the course of 30 days. The information on GiveLab 30 Days of Impact 2025 can be found on the internal Loop page.

·Throughout the month, team members can volunteer as little as one hour of their time to make an impact. We understand that our team members are driven by many different factors, and we welcome that volunteer participation will look different for everyone. Through GiveLab 30 days of Impact we aim to offer many different ways for team members to get involved such as:

• ·Through company-sponsored virtual events
• ·Local in-person volunteer events organized by the GitLab Sustainability team, GiveLab Champions, and team members Individual volunteer pursuits
• ·Find and contribute to opportunities in the GiveLab Volunteer Directory
• ·Include a volunteer activity at an all-hands or team builder Contribute to GitLab's codebase
• ·Assist with retention and recruitment efforts

·Why GiveLab 30 Days of Impact Exists

·While GitLab encourages year-round volunteerism through GiveLab, GiveLab 30 days of Impact centralizes our efforts into an annual campaign to have a larger collective impact over a specific timeframe. Corporate volunteerism has been proven to be an effective strategy for boosting engagement, improving employee retention, and strengthening relationships at work. Additionally, this program offers volunteering opportunities around a major holiday season in many parts of the world, a time when many are seeking opportunities to give back.

·Team Member Benefits of Volunteerism

• ·Develop new skills and knowledge
• ·Expand your professional network and connections
• ·Understand the nonprofit community's needs and how your skills can help
• ·Make a meaningful difference in your community

·Importance of Volunteerism at GitLab

• ·Provide an additional option for team members to volunteer and make a positive impact beyond the impact team members make every day by contributing to GitLab - the platform and the company
• ·Provide another way for team members to embody our CREDIT values through volunteerism and social impact
• ·Expand GitLab's positive impact across communities
• ·Build trust amongst team members through social connections Boost team member engagement

·Utilizing GitLab's PTO Policy to Volunteer

·Team member participation is voluntary, should not interfere with work commitments, and time off is required to be in alignment with GitLab's PTO policy. Travel is not permitted for this program. Team Members may choose to volunteer virtually or through local in-person events. Volunteer events typically last between one and four hours. Managers play an important role in supporting team members in taking time for themselves and their families, while also ensuring accountability to results and coverage for teams and its goals. Our Results for Customers value sits at the top of our values hierarchy, and our PTO policy empowers managers to appropriately manage workloads and deliverables, while also giving team members the time away they need from work.

·How to Request Volunteer Time Off

·Team Members taking time off to volunteer should communicate time off in advance with their manager. To request volunteer time off, follow the Paid Time Off procedures outlined in our handbook and reach out to People Operations via Compass should you have any concerns. A step-by-step guide on how to request paid time off can be found here. Note that volunteer time off should be used towards acceptable volunteer activities and in adherence with our GitLab Philanthropy Policy.

·Expenses and Reimbursements for Participation

·Please see our GiveLab reimbursement policy to understand current allowances as they relate to volunteering costs.

·GiveLab Volunteer Directory

·We have created an internal GiveLab Volunteer Directory that features a list of vetted nonprofit organizations with available volunteer opportunities. Team members can search the document for virtual volunteer opportunities, opportunities to volunteer with GitLab Foundation grantees and search for local opportunities.

·We encourage all team members to contribute to our GiveLab Volunteer Directory. To recommend a nonprofit organization to add to the Directory, please open a Volunteer Recommendation Issue.

·GiveLab Champions

·The GiveLab Champions are team members who are passionate about giving back to their communities and want to encourage other team members to do the same.

·GiveLab Champions self-identify to participate in the voluntary Champions group, managed by the Sustainability team. The GiveLab Champions help activate the GiveLab signature program, but also work to organize and promote volunteer opportunities year-round.

·The importance of GiveLab Champions

·GiveLab Champions help team members build trust through social connections, build connections within their communities, and help GitLab provide meaningful opportunities for team members to give back. The GiveLab Champions ensure global voices are heard and relevant causes are represented based on where team members live. GiveLab Champions help to make GitLab a better place to work.

·Team member benefits of volunteering

• ·Champions introduce new and current team members to GitLab's culture and help to build and maintain engagement
• ·Champions help build trust through social connections
• ·Champions have the opportunity to develop professional and leadership skills, build relationships across the company and make a difference at work and in local communities
• ·Champions can network and provide positive impacts to the business

·GiveLab Champion responsibilities

• ·Recommend local Registered Nonprofit Organizations that meet GitLab's eligibility criteria for volunteer activities
• ·Help organize local volunteer events for team members to participate in
• ·Provide recommendations to the Sustainability Team for virtual volunteer opportunities Encourage team members to volunteer
• ·Help plan and execute the GiveLab signature program
• ·Participate in quarterly Champion group meetings
• ·Provide feedback to the Sustainability team on the GiveLab and Sustainability Programs

·Time commitment

·The time commitment for a GiveLab Champion is estimated to be 3-5 hours per quarter. Participation can vary throughout the year.

·Selection criteria

• ·The team member must be performing in their role and not part of any performance management process as confirmed by the People Group
• ·Must be a full-time GitLab team member. This includes team members employed through a PEO or who contract with CXC or directly with GitLab IT BV At least 3-month tenure at GitLab
• ·Approval from your direct manager and support to commit the time and to use this leadership role as a professional development opportunity
• ·A minimum one-year commitment in the role but understanding this may change to less and can be more

·Selection process

• ·Interested team members should complete the GiveLab Champions survey expressing their interest
• ·Team members must confirm that they have approval from their manager to participate
• ·The Sustainability team evaluates interest at a minimum on a monthly cadence and will reach out to the interested individual for follow up questions

·GitLab for Non-Profits

·GitLab launched GitLab for Nonprofits, an in-kind donation program in 2023. Through this program, GitLab supports Registered 501c3 (or jurisdictional equivalent) Nonprofit Organizations in good standing that align with our values by offering free licenses and seats. The program operates on a first come first served basis. Once the annual donation of 5,000 seats is met, the application will remain closed for the year.

·FAQs

·What are the benefits of the GitLab for Nonprofits program?

·GitLab is a single platform for project management, collaboration, source control management, git, automation, security, and much more. Because it is easy to use, flexible, and all in one place, it is the best choice for nonprofits to scale their work. The GitLab for Nonprofits Program gives free licenses of GitLab to registered nonprofit organizations.

·Nonprofits accepted into the program will be provided a free Ultimate license for one year (SaaS or self-managed) for up to 20 seats. Additional seats may be requested at a discounted rate. Who qualifies for the program?

·GitLab supports Registered 501c3 (or jurisdictional equivalent) Nonprofit Organizations in good standing that align with our Values. A "Registered Nonprofit Organization" is one that has been registered with the local government or authorized agency within its applicable local, state, provincial, federal or national government.

·For the calendar year 2026, we will limit the in-kind program to 5,000 seats, which was approved by finance and the board in the Philanthropy Policy. Each organization will be eligible for up to 20 seats. This will allow us to assist as many organizations as possible. This will be revisited throughout the year and adjusted as needed. Interested organizations who are new customers may request additional seats although the request may not be granted. To limit churn, current GitLab customers that apply to transition to the Nonprofit Program will not be granted a special request above the 20 seats.

·What are the terms of the GitLab for Nonprofits program?

·Upon acceptance, program members are subject to the GitLab Subscription Agreement. The decision to issue a GitLab for Nonprofits license is always at the sole discretion of GitLab. How does someone apply?

·Interested organizations need to visit the GitLab for Nonprofits page and submit the application. How are applications processed?

·Nonprofits apply on the GitLab for Nonprofits page. Once the application link is clicked, the organiztion will need to log in or create an account. Once that is complete, the organization will automatically be redirected to Goodstack for verification. Upon successfull verification and eligibility, the organization will receive an email with a code and instructions to redeem their product.

·Please allow up to 15 business days for the application and verification process.

·Must Nonprofits renew their memberships?

·Yes. All nonprofits must renew their membership annually, which involves a re-verification process. Nonprofits will submit for renewal the same way they first applied for the program. Where can members receive support?

·While GitLab for Nonprofits Program benefits do not include product support, program members can receive help with GitLab in a number of ways. In general, we recommend the following:

• ·Send questions or issues requiring immediate attention or sensitive information to the GitLab for Nonprofits team at Nonprofits@GitLab.com
• ·Review GitLab Docs for answers to general product-related questions
• ·Post questions in the GitLab Forum, where community members and GitLab team members can review and discuss them
• ·File bug reports and breaking behaviors as issues for product teams to review and address

·I'm a GitLab Team Member and I have a customer applying for the program. What do I do?

• ·If the nonprofit requires less than 20 seats, please point the Nonprofit to the GitLab for Nonprofits page to learn about the program, eligibility and application. If the nonprofit requires more than 20 seats, this will be a sales-assisted process. Reach out in the Slack channel #gitlab-for-nonprofits
• ·If the Nonprofit has questions on the eligibility or status of an application, please advise them to reach out to nonprofits@gitlab.com. Or team members can inquire about the status of an application in #gitlab-for-nonprofits
• ·If you have a question or concern about the customer churn, please raise this in #gitlab-for-nonprofits slack channel and a Sustainability team member will contact you

·Philanthropic Requests

·Information on how GitLab Inc. supports Registered Nonprofit Organizations can be found in the Philanthropy Policy.

·Please note that for all Philanthropic Requests, including requests for GitLab to join as a member to an association, program or organization, approval by the Sustainability team and CLO is required as defined by the Oversight Responsibility section of the Policy.

·If you would like to submit a philanthropic request, please follow the instructions based on your request type.

·Monetary Contributions

·There are two ways that team members can submit a request for monetary support:

• 1Request funding from the Sustainability team to support a Registered Nonprofit Organization OR (not currently accepting applications - see instructions below on submitting a non-profit for future consideration)
• 2Request utilizing department or TMRG budget to support a Registered Nonprofit Organization

·If you are requesting funding from the Sustainability team to support a Registered Nonprofit Organization, please note that at this time, we are not accepting applications. If you would like to submit a Nonprofit Organization to be considered for support in the future, please go to the Philanthropic Requests epic and open a new issue using the Monetary_Support Template. You will be notified if there is a future opportunity.

·If you have a department or TMRG budget that you would like to utilize to support a Registered Nonprofit Organization, please go to the Philanthropic Requests epic and open a new issue using the Monetary_Support Template. Please tag your manager to approve the request if you are submitting on behalf of your department. If you are submitting a request on behalf of a TMRG or DIB, please add the DIB DRI as a reviewer. Please allow a minimum of 10 working days for review.

·The team member submitting the issue is responsible for obtaining proper approvals and working with Accounts Payable to issue the payment. Please tag the individuals in the approver section of the issue. Once approvals are completed, the team member requesting the donation needs to obtain an invoice from the non-profit that contains the bank payment details and submit this to AP@GitLab.com.

·Membership Requests (non-monetary)

·For requests related to GitLab Membership of Association, Program or Organization, and includes terms, conditions and/or obligations on GitLab that must be executed, please follow the below process. Open an issue using the Membership Request Issue Template. Complete and attach the necessary information. Note: If you are submitting a request on behalf of a TMRG or DIB, please add the DIB DRI as a reviewer.

·NOTE: For any request(s) that require payment, please be certain to follow applicable ESG & Procurement processes.

·Matching Gifts Program

·At this time, GitLab does not offer a matching gifts program.

·Earth Month

·GitLab FY26 Earth Month Campaign

·GitLab Fiscal Year 2023 (FY23) ESG Report

·Message From Our Chief Executive Officer Welcome to GitLab's inaugural Environmental, Social, ...

·Sustainability Training

·Sustainability Training for GitLab team members

·Team Member Sustainability Guide

·GitLab's Team Member Sustainability Guide for Remote Work

·Last modified September 13, 2026: Rename HelpLab to Compass across handbook content (bee431b5) View page source - Edit this page - please contribute.