realaravinth/debian-mirror-gitlab
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
debian-mirror-gitlab/doc/subscriptions/index.md
Pirate Praveen 7885e913d2 New upstream version 15.10.7+ds1
2023-05-27 22:25:52 +05:30

14 KiB
Raw Blame History

stage group info type
Fulfillment Purchase To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments index, reference

GitLab subscription (PREMIUM)

GitLab offers tiers of features. Your subscription determines which tier you have access to. Subscriptions are valid for 12 months.

GitLab provides special subscriptions to participants in:

Choose a GitLab subscription

When choosing a subscription, there are two factors to consider:

Choose between GitLab SaaS or GitLab self-managed

There are some differences in how a subscription applies, depending if you use GitLab SaaS or GitLab self-managed:

  • GitLab SaaS: The GitLab software-as-a-service offering. You don't need to install anything to use GitLab SaaS, you only need to sign up and start using GitLab straight away.
  • GitLab Dedicated: a single-tenant SaaS service for highly regulated and large enterprises.
  • GitLab self-managed: Install, administer, and maintain your own GitLab instance.

On a GitLab self-managed instance, a GitLab subscription provides the same set of features for all users. On GitLab SaaS, you can apply a subscription to a group namespace. You cannot apply a subscription to a personal namespace.

NOTE: Subscriptions cannot be transferred between GitLab SaaS and GitLab self-managed. A new subscription must be purchased and applied as needed.

Choose a GitLab tier

Pricing is tier-based, allowing you to choose the features which fit your budget. For information on what features are available at each tier for each product, see: GitLab self-managed feature comparison

Find your subscription

The following chart should help you determine your subscription model. Select the list item to go to the respective help page.

graph TD

A(Is your user account on GitLab.com?)
A --> B(Yes)
A --> C(No)
B --> D(fa:fa-link View your subscription on GitLab.com)
C --> E(fa:fa-link View your self-hosted subscription)

click D "./gitlab_com/index.html#view-your-gitlabcom-subscription"
click E "./self_managed/index.html#view-your-subscription"

Customers Portal

With the Customers Portal you can:

The Customers Portal is available only to customers who purchased their subscription from GitLab. If you made your purchase through a partner or reseller, you must contact them directly for assistance with your subscription.

Change account owner information

Account owner personal details are used on invoices. The account owner email address is used for the Customers Portal legacy login and license-related email.

If you have registered a Customers Portal account through a GitLab.com account, the GitLab.com account is used for login.

To change account owner information, including name, billing address, and email address:

  1. Log in to the Customers Portal.
  2. Select My account > Account details.
  3. Expand the Personal details section.
  4. Edit the personal details.
  5. Select Save changes.

If you want to transfer ownership of the Customers Portal account to another person, after you enter that person's personal details, you must also:

Change your company details

To change your company details, including company name and VAT number:

  1. Log in to the Customers Portal.
  2. Select My account > Account details.
  3. Expand the Company details section.
  4. Edit the company details.
  5. Select Save changes.

Change your payment method

Purchases in the Customers Portal require a credit card on record as a payment method. You can add multiple credit cards to your account, so that purchases for different products are charged to the correct card.

If you would like to use an alternative method to pay, please contact our Sales team.

To change your payment method:

  1. Log in to the Customers Portal.
  2. Select My account > Payment methods.
  3. Edit an existing payment method's information or Add new payment method.
  4. Select Save Changes.

Set a default payment method

Automatic renewal of a subscription is charged to your default payment method. To mark a payment method as the default:

  1. Log in to the Customers Portal.
  2. Select My account > Payment methods.
  3. Edit the selected payment method and check the Make default payment method checkbox.
  4. Select Save Changes.

Link a GitLab.com account

Follow this guideline if you have a legacy Customers Portal account and use an email and password to log in.

To link a GitLab.com account to your Customers Portal account:

  1. Log in to the Customers Portal using email and password.
  2. On the Customers Portal page, select My account > Account details.
  3. Under Your GitLab.com account, select Link account.
  4. Log in to the GitLab.com account you want to link to the Customers Portal account.

Change the linked account

To change the GitLab.com account linked to your Customers Portal account:

  1. Log in to the Customers Portal.
  2. In a separate browser tab, go to GitLab.com and ensure you are not logged in.
  3. On the Customers Portal page, select My account > Account details.
  4. Under Your GitLab.com account, select Change linked account.
  5. Log in to the GitLab.com account you want to link to the Customers Portal account.

Change Customers Portal account password

To change the password for this customers portal account:

  1. Log in to the Customers Portal.
  2. Select the My account dropdown list and select Account details.
  3. Make the required changes to the Your password section.
  4. Select Save changes.

Community program subscriptions

GitLab for Education

For qualifying non-profit educational institutions, the GitLab for Education Program provides GitLab Ultimate, plus 50,000 CI/CD minutes per month. The subscription granted under GitLab for Education can only be used for instructional use or non-commercial academic research. For more information—including instructions for applying to the program and renewing program membership—see the GitLab for Education Program page and the GitLab handbook.

GitLab for Open Source

For qualifying open source projects, the GitLab for Open Source Program provides GitLab Ultimate, plus 50,000 CI/CD minutes per month. For more information—including instructions for applying to the program and renewing program membership—see the GitLab for Open Source Program page and the GitLab handbook.

Meeting GitLab for Open Source Program requirements

To meet GitLab for Open Source Program requirements, first add an OSI-approved open source license to all projects in your namespace.

To add a license to a project:

  1. On the top bar, select Main menu > Projects and find your project.
  2. On the overview page, select Add LICENSE. If the license you want is not available as a license template, manually copy the entire, unaltered text of your chosen license into the LICENSE file. Note that GitLab defaults to All rights reserved if users do not perform this action.

Add license

Applicants must add the correct license to each project in their respective groups or namespaces. When you're sure you're using OSI-approved licenses for your projects, you can take your screenshots.

NOTE: GitLab for Open Source Program benefits apply to an entire GitLab namespace. To qualify for the GitLab for Open Source Program, all projects in an applicant's namespace must meet program requirements. Applicants submit materials related to one project in the applying namespace, and the open source program team uses that project to verify eligibility of the entire namespace.

Verification for Open Source Program

Next, take screenshots of your project to confirm that project's eligibility. You must upload three screenshots:

NOTE: Benefits of the GitLab Open Source Program apply to all projects in a GitLab namespace. All projects in an eligible namespace must meet program requirements.

Screenshot 1: License overview
  1. On the top bar, select Main menu > Projects and find your project.
  2. On the left sidebar, select your project avatar. If you haven't specified an avatar for your project, the avatar displays as a single letter.
  3. Take a screenshot of the project overview that clearly displays the license you've chosen for your project.

License overview

Screenshot 2: License contents
  1. On the top bar, select Main menu > Projects and find your project.
  2. On the left sidebar, select Repository and locate the project's LICENSE file.
  3. Take a screenshot of the contents of the file. Make sure the screenshot includes the title of the license.

License file

Screenshot 3: Publicly visible settings

To be eligible for the GitLab Open Source Program, projects must be publicly visible. To check your project's public visibility settings:

  1. On the top bar, select Main menu > Projects and find your project.
  2. From the left sidebar, select Settings > General.
  3. Expand Visibility, project features, permissions.
  4. From the Project visibility dropdown list, select Public.
  5. Select the Users can request access checkbox.
  6. Take a screenshot of this view. Include as much of the publicly visible settings as possible. Make sure to include your project's name in the upper-left of the screenshot.

Publicly visible setting

NOTE: Exceptions to this public visibility requirement apply in select circumstances (for example, in cases where a project in an applicant's namespace may hold sensitive data). Email opensource@gitlab.com with details of your use case to request written permission for exceptions.

GitLab for Startups

For qualifying startups, the GitLab for Startups program provides GitLab Ultimate, plus 50,000 CI/CD minutes per month for 12 months. For more information—including instructions for applying to the program and renewing program membership—see the GitLab for Startups Program page and the GitLab handbook.

Contact Support

We also encourage all users to search our project trackers for known issues and existing feature requests in the GitLab project.

These issues are the best avenue for getting updates on specific product plans and for communicating directly with the relevant GitLab team members.