# GitHub Partner Success Offering Terms

These GitHub Partner Success Offering Terms ("Terms") are effective as of November 16, 2026.

If you are a GitHub partner ("Partner" or "you") and you use GitHub's Partner Success offering ("Partner Success"), then these Terms apply. These Terms, the [GitHub Services and Channel Partner Program Terms](https://portal.github.partners/content/8a998df998a11e510198a4c8f6113700), the [GitHub Services and Channel Partner Program Guide](https://portal.github.partners/content/8a99930f9858994901985cbe948468b6), and any order form (each, an "Order Form" and collectively, the "Agreement") govern Partner Success.

Capitalized terms not defined in these Terms have the meanings given elsewhere in the Agreement.

## About Partner Success

Partner Success is a proactive support service available as an add-on for Partners with an active subscription to the Partner Support Offering (“Partner Support”). It provides an entitlement of eighty (80) proactive consulting hours per year, prorated for any partial term as set out in the applicable Order Form.

## Subscription Term and Allocation of Hours

Your Partner Success subscription is coterminous with your Partner Support subscription. If your initial Partner Success term is shorter than 12 months, your allocated hours will be adjusted on a pro rata basis to align with your then-current Partner Support subscription end date. For example, if your Partner Support subscription expires on December 31 and you add Partner Success effective July 1 (a remaining term of 184 days), your allocation will be 40 hours, calculated based on the proportion of the year remaining (184/365) and rounded to the nearest whole hour.

Your allocated hours will be specified in the applicable Order Form, and additional hours may be purchased as needed. Prepaid hours may be used for Eligible Services, as defined below and subject to availability. Prepaid hours must be used within the applicable subscription term and will not carry over to any renewal term. Any prepaid fees for unused hours are non-refundable.

## Regional Allocation

Partner must select a single Region for its Partner Success subscription, which will be specified in the applicable Order Form. For purposes of these Terms, "Region" means each of the following: (1) Europe and the Middle East; (2) Asia and Oceania; and (3) North and South America. All prepaid hours allocated under the applicable Order Form, including the eighty (80) hours described above (or any prorated amount), must be consumed in the selected Region and may not be used in, split across, or transferred to any other Region. GitHub will perform the Services in, and source the delivery engineers supporting the Services from, the selected Region.

## Eligible Services

You may use your prepaid hours for any combination of the following Eligible Services:

* **Design Reviews:** Expert feedback on Partner proposals and solution architectures to ensure alignment with best practices.
* **Problem Solving:** Hands-on help with complex Partner challenges or technical setups.
* **Train-the-Trainer:** Enablement sessions to help Partner teams teach and scale GitHub knowledge internally. These sessions are intended for Partner personnel only; end customer participation is not permitted. The maximum number of Partner participants per session is ten (10).
* **Accelerator Co-Creation:** Collaboration to design new assets and accelerators for partner solutions.

## Service Scheduling, Lead Times, and Delivery

For purposes of these Terms, ‘Services’ means the Eligible Services (and any related deliverables) performed by GitHub under Partner Success. Requests to schedule Services must be submitted at least twenty-eight (28) days in advance. GitHub will use commercially reasonable efforts to make resources available within twenty-eight (28) days from the date a request is submitted and ready for scheduling. This lead time supports capacity planning and helps manage resource availability.

If capacity allows, GitHub may provide support sooner, for example, by assigning an engineer on a short-term rotational basis (typically two (2) weeks) or by addressing smaller requests submitted through the designated Partner intake repository on an asynchronous basis.

Any changes to the delivery schedule must be agreed in writing (including by email) by authorized representatives of each party. Services must be requested in minimum increments of four (4) hours and may not exceed eight (8) hours in any single day.

## Partner Responsibilities

Partner must identify a primary responsible person (the "Primary Responsible Person") who has authority to act on Partner's behalf in matters relating to the Services and must serve as the primary interface between GitHub's project team and Partner departments participating in the Services within that Region.

Each Primary Responsible Person must:

* Obtain and provide accurate and applicable information, data, consents, decisions, and approvals without delay as required by GitHub to perform the Services;
* For Hands-On Delivery, promptly provide access, workspace, and connectivity to the systems and other facilities necessary for GitHub personnel while working at Partner locations, and help resolve and escalate Services issues within Partner's organization as necessary; and
* Identify all Partner team members with appropriate systems access who will act as GitHub's hands-on-keyboard during the Services and otherwise make personnel available to assist GitHub in performing its responsibilities.

## Partner Security Regulations (Hands-On Delivery)

Partner is responsible for protecting the privacy and security of its data, including Personal Data, and for controlling access by GitHub personnel and subcontractors. This includes conducting security check-in procedures and providing badges and a personal escort for all on-site engagements.

Partner must:

* Not share administrative credentials with GitHub employees or personnel;
* Create temporary access credentials for use by GitHub employees or personnel that are valid on the Services start date and that automatically expire upon completion of the Services; and
* Provide its security regulations to GitHub. GitHub will ensure that its personnel and subcontractors make commercially reasonable efforts to comply with Partner’s security regulations while at Partner sites or in connection with Partner systems.

Unless otherwise agreed in advance in writing (including by email) by GitHub’s Delivery Manager, GitHub personnel (including subcontractors) will observe Partner’s working hours, working rules, and holiday schedules while working on Partner premises.

## Warranties

**General.** GitHub warrants that it will perform the Services with professional care and skill. If it does not, and Partner notifies GitHub within 90 days of the date the Services were performed, GitHub will at its option and expense either: (i) re-perform the affected Services or (ii) except for dedicated resources (such as, but not limited to, Services Account Engineers), return the price Partner paid for the defective deliverables comprising the applicable Services.

Each party also represents and warrants that it will secure the permission of the other party prior to providing any source code in a manner that would subject the other party's technology or intellectual property to any other license terms or require the other party to distribute source code to any of its technologies.

The remedies above are Partner's sole remedies for breach of the warranties. Partner waives any warranty claims not made during the warranty period.

**Exclusions.** The warranties in these Terms do not apply to problems caused by accident, abuse, or use inconsistent with the Agreement, including failure to meet minimum system requirements. These warranties do not apply to Services made available by GitHub for free.

**Disclaimer.** Except for the limited warranties above and subject to applicable law, GitHub provides no other warranties. It disclaims any other express, implied or statutory warranties, including warranties of quality, title, non-infringement, merchantability, and fitness for a particular purpose.

## Intellectual Property Rights

When GitHub provides Services to Partner, each party owns all rights, title and interest to its pre-existing technology and Confidential Information (“Pre-Existing Work”), including all intellectual property rights. GitHub has a right to use Partner’s Pre-Existing Work solely to provide Services under the Agreement.

Each party will exclusively own all modifications and derivative works created under the Agreement to that party’s Pre-Existing Work (“Improvements”). Each party therefore assigns to the other party all rights, title, and interest to any Improvements it makes to the other party’s Pre-Existing work. Each party grants the other party a worldwide, non-exclusive, fully paid-up license to use, reproduce, distribute and create derivative works of its Improvements.

All new technology, written materials, or proofs of concept under the Agreement that do not include any Pre-Existing Work or Improvements (“Developments”) will be owned by GitHub. Partner assigns to GitHub all rights, title, and interest to any Developments it makes. GitHub grants Partner a worldwide, non-exclusive, fully paid-up license to use, reproduce, and create derivative works of Developments. Partner may share Developments with its end customers solely to the extent necessary for such customers’ use in connection with Partner’s offering, provided that Partner ensures such end customers are subject to written license terms that restrict the use of the Developments to their own internal business purposes only and prohibit any distribution, transfer or disclosure of the Developments to any third party. Partner will be responsible for ensuring compliance with such terms by its end customers. If GitHub releases Improvements or Developments to Partner as open source software, the open source terms will apply instead of this license grant.

## Changes to these Terms

GitHub may amend or update these Terms at any time by publishing the revised version. Subject to the following paragraph, any such changes will take effect immediately upon publication.

For any Partner who renews or purchases a new Partner Success subscription, the version of the Terms in effect at the time of renewal or purchase will apply for the duration of that subscription term, and will not change during that term.

## Termination

The Agreement will automatically end if your GitHub Services and Channel Partner Program membership (“GHPP membership”) or Partner Support subscription ends. Please note that fees paid for Partner Success are non-refundable if you terminate your GHPP membership or Partner Support subscription without cause, or if GitHub terminates your GHPP membership or Partner Support subscription for cause.