Commit 84a5e32a authored by Marcella Summers's avatar Marcella Summers
Browse files

Add new MSP Partner Program.md

parent 07157ec3
Loading
Loading
Loading
Loading
+40 −3
Original line number Diff line number Diff line
@@ -75,7 +75,7 @@ Partners in the GitLab Partner Program are included in one of two tracks; Select

#### Open Track

The Open track is designed for resellers, integrators, and other sales and services partners committed to investing in their DevSecOps practice buildout and GTM efforts. Open resale partners transact via [GitLab Authorized Distributors active in their region](/handbook/sales/field-operations/channel-operations/#distributor-requirements-and-coverage-by-geo-and-market). There is no revenue requirement for Open partners. Partners in the business of delivering professional services are also encouraged to consider earning the GitLab Professional Services (PSP) designation.
The Open track is designed for resellers, integrators, and other sales and services partners committed to investing in their DevSecOps practice buildout and GTM efforts. Open resale partners transact through [GitLab Authorized Distributors active in their region](/handbook/sales/field-operations/channel-operations/#distributor-requirements-and-coverage-by-geo-and-market). There is no revenue requirement for Open partners. Partners in the business of delivering professional services are also encouraged to consider earning the GitLab Professional Services (PSP) designation.

**Benefits for Open Partners:**

@@ -158,7 +158,44 @@ When partners complete the competency requirements and their first two service a

Maintaining the PSP Designation: Each PSP is required to have submitted at least 8 Service Attach Registrations and/or Managed Services Deal Registrations with proof of execution (POE), over the previous 12 months at their annual audit(s). Partner PSP annual audits take place based on the partner’s date of PSP achievement.

#### Partner Resale Margins & Incentives
### The GitLab Managed Service Provider (MSP) Partner Program

The GitLab Managed Service Provider (MSP) Partner Program enables qualified Managed Service Providers to deliver GitLab as a fully managed service for their customers, including deployment, ongoing platform operations, support, and customer success management.
MSPs differ from traditional resellers in that they own the end‑to‑end customer lifecycle for GitLab within a broader managed services engagement, while GitLab provides the platform, program structure, and enablement to help them scale.
This program is a strong fit for organizations that already provide managed services (for example, cloud, infrastructure, or application operations) and want to add a DevSecOps managed services offering built on GitLab’s platform.

#### Why become a GitLab MSP Partner?

MSP partners can:

- Build high‑margin, recurring revenue by combining GitLab subscription margins with their own managed services, implementation, migration, and advisory offerings.
- Deepen customer stickiness by operating GitLab day‑to‑day, driving adoption and value realization rather than participating only in the initial sale.
- Differentiate in the market with a Certified MSP designation, GitLab branding, and visibility in GitLab’s partner‑facing assets and locator, helping customers find partners with proven GitLab expertise.
- Access enablement, tools, and marketing support, including MSP‑specific guides, training, and eligibility for standard GitLab programs such as Not‑for‑Resale (NFR) licenses and Marketing Development Funds (MDF) where applicable.

#### Baseline Requirements

At a high level, prospective MSP partners should:

- Be an authorized GitLab partner in good standing at the `Select` level and hold the [Professional Services Partner](/handbook/resellers/channel-program-guide/#the-gitlab-professional-services-partner-psp-program) (PSP) designation.
- Operate an established managed services practice with active managed service customers and a track record of delivering ongoing services (for example, cloud, infrastructure, or platform operations).
- Have the ability to deploy and manage GitLab Self‑Managed environments, including secure operations, monitoring, backup, and disaster recovery capabilities.
- Provide at least business‑hours (8×5) support for their GitLab managed service customers with a defined escalation path to GitLab for eligible issues.
- Be or become an authorized GitLab partner in good standing, and agree to the MSP exhibit and applicable GitLab partner program terms.

Specific competency, certification, and performance requirements are defined in the MSP Partner Program Guide and MSP Exhibit.

#### How to Apply

- **If you’re an existing GitLab partner interested in joining the MSP program:**
Please complete the MSP application form found on the Common Requests page in the GitLab Partner Portal. Our team will review your submission and reach out with next steps.

- **If you’re not yet a GitLab partner and are interested in the MSP program:**
First submit a GitLab partner application at partners.gitlab.com. Once your partner application is approved, you can then complete the MSP application in the Partner Portal.

Requests will be reviewed within three business days, and your Ecosystem Sales Manager (ESM) will reach out to introduce you to the program and discuss fit and next steps.

### Partner Resale Margins & Incentives

The GitLab Partner Program offers financial incentives to partners who help sell and support GitLab products. Partners can earn both one-time and recurring revenue through product sales, referrals, and service delivery. For complete details, terms and conditions for GitLab program incentives, review the [GitLab Partner Program Incentive Guide](https://partners.gitlab.com/prm/api/objects/v1/asset/o8jsfw4ffvrl/_view). Margins for sales to U.S. and Canada Public Sector customers are available in the [GitLab Public Sector Partner Program Incentive Guide](https://partners.gitlab.com/prm/api/objects/v1/asset/kfcpnhxh82lr/_view). For additional questions, please contact partnersupport@gitlab.com.

@@ -257,7 +294,7 @@ GitLab Select and Distribution partners have access to the proposal-based GitLab

To receive MDF, partners must:

- Submit a proposal to GitLab via the GitLab Partner Portal
- Submit a proposal to GitLab through the GitLab Partner Portal
- Have an authorized GitLab Marketing Manager review and approve the proposal
- Promptly submit the required proof of performance documentation to GitLab 30 days following the activity