GitLab Premium is ideal for scaling organizations and for multi team usage. Available in both SaaS and self-managed deployment options, GitLab Premium helps to enhance team productivity and collaboration through faster code reviews, advanced CI/CD, enterprise agile planning and release controls. GitLab Premium adds enterprise level features like priority support, live upgrade assistance and a technical account managers (for eligible accounts). It also adds enterprise readiness features like High Availability, Disaster Recovery for self-managed instances.
Please note this is not a comprehensive set of capabilities in GitLab Premium, visit about.gitlab.com/features for the latest. GitLab continuously adds features every month and evaluates features that can be moved to lower tiers to benefit more users.
| Increase Operational Efficiencies | Deliver Better Products Faster | Reduce Security & Compliance Risk |
|---|---|---|
| GitLab Premium introduces capabilities that allow enterprises analyze team, project and group trends to uncover patterns and setup consistent standards to improve overall productivity. | With Advanced CI/CD and faster code reviews, GitLab Premium helps you build, maintain, deploy and monitor complex application pipelines better to deliver products faster. | Release controls in GitLab Premium ensure that teams ship high quality and secure code. |
Read all case studies here
Ensure high code quality across teams through seamless code review workflows. Learn more about Faster code reviews with GitLab.
| Feature name | Value |
|---|---|
| Multiple approvers in code review | To ensure strict code review, you can require a minimum number of users to approve of a merge request before it is able to be merged. |
| Merge request reviews | For faster code review, draft multiple comments in a merge request code review, before submitting them together all at once. |
| Code Owners | Assign Code Owners to files to indicate the team members responsible for code in your project. Code owners are assigned automatically as merge request approvers. |
| Code Review Analytics | Find bottlenecks in your code review process by understanding how long open merge requests have been in review. |
| Pipelines for Merged Results | Keep master green. A special pipeline runs on the results of merged code before merging into master to detect changes that may be green on a branch but will fail master when merged. |
| Code Quality Reports | Full Code Quality reports are available on the pipeline page, showing areas of the codebase that do not meet the organization's preferred style or standards. |
| Comments in Review Apps | Shorten the feedback cycle and enable stakeholders to provide comments through a form in your review app - which is then automatically added to the related merge request . |
Build, maintain, deploy, and monitor complex pipelines. Learn more about Advanced CI/CD with GitLab.
| Feature name | Value |
|---|---|
| CI/CD Pipelines Dashboard | Visualize the history and current status of pipelines across projects and groups all in a single dashboard that can be customized for each user. |
| Multi-project pipeline graphs | Visualize how pipelines across projects are linked together, including cross project dependencies. |
| Merge Trains | Reduce pipeline queueing and waiting time with merge trains which allows parallel pipeline execution, with each pipeline building off the merge result of the previous one. |
| CI/CD for external repo | Connect your projects hosted on external services (like GitHub or Bitbucket) and leverage the power of GitLab CI/CD pipelines to build, test, and deploy your applications easily. |
| GitLab Kubernetes Agent | Manage the deployments and connection to your Kubernetes clusters in a secure and compliant way, driven by code. |
| Environments Dashboard | Visualize cross-project environments, track change flow from development to production, track pipeline status and diagnose issues from a single dashboard. |
| Group file templates | Define custom LICENSE, .gitignore, Dockerfile and .gitlab-ci.yml templates for a Group to make consistency easier. |
| Cluster Environments Global View | An overview of all the projects, environments provisioned and the numbers of pods used by each environment in a Kubernetes cluster. |
| Robust deploy and rollback bundle | Encapsulate knowledge of deploying and rolling back into something more than a script, perhaps similar to a k8s operator. Something that knows how to handle failure. e.g. if you’re deploying 7 services and one fails, you can’t just stop, you probably have to rollback the 6 that succeeded, as well as the 7th that failed. (Now, depending on implementation, it still might be a script that triggers some kind of operator). GitLab can deploy and rollback, but only via scripts with limited error handling. |
| Instance file templates | Define custom LICENSE, .gitignore, Dockerfile and .gitlab-ci.yml templates for your GitLab instance to make consistency easier. |
| Pipelines for Merge Requests | Specify when you want jobs to run only when they are in a pipeline associated with a Merge Request. Make your pipelines more efficient by running only the necessary jobs for Merge Requests. |
| Group Code Coverage Data | Tracking code coverage changes for multiple projects can be a time consuming and low value task for a team lead. GitLab provides a page that aggregates the code coverage data for a group's projects and makes it available for download. |
Plan and manage your projects, programs, and products with integrated Agile support. Learn more about Enterprise agile planning with GitLab.
| Feature name | Value |
|---|---|
| Roadmaps | Visualize multiple epics and milestones across time in a roadmap view. |
| Issue Board Milestone Lists | Issue board lists that pull in issues in a given milestone |
| Scoped Labels | Assign scoped labels mutually exclusively when they have the same scope. |
| Multiple Issue Assignees | Assign more than one person to an issue at a time. |
| Single level Epics | Plan and track features and work group level epics that collect issues together. Easily create and assign Issues directly from the Epic itself |
| Multiple Group Issue Boards | Multiple Group Issue Boards, similar to Multiple Project Issue Boards |
| Promote Issue to Epic | Promote an issue to epic to continue collaboration at a higher-level work abstraction. |
| Issue Board Configuration | Associate a board with a milestone, labels, an assignee, and a weight |
| Issue Weights | GitLab lets you manage issues using Agile practices by setting the weight of an issue. |
| Issue Analytics | See issue analytics at the group level. |
| Issue Dependencies | Explicitly mark issues as blocked and blocking and track their status. Blocked issues are visible in the issue card view for easy identification. |
| Issue Board Assignee Lists | Issue board lists that pull in issues assigned to a given user |
| Burndown Charts | GitLab provides Burndown Charts as part of Milestones and Iterations. This allows users to better track progress during a sprint or while working on a new version of their software. |
| Iterations | Create and manage iterations at the group level, view all the issues for the iteration you’re currently working on within your group or project, and enable all subgroups and projects to stay in sync on the same cadence. |
| Confidential Epics | Organize a collection of related confidential issues into a confidential epic, allowing you to manage sensitive work more efficiently. |
| Burnup Charts | With Milestone and Iteration Burnup Charts, you can better understand scope change during a sprint or while working on a new version of your software. |
| View Jira issues in GitLab | "Extends the Jira integration, adding an option to display a list of Jira issues natively inside the GitLab project, allowing developers working primarily in GitLab to remain in flow, without having to reference a second tool for tracking what work needs to get done." |
Implement controls to ensure teams ship high quality and secure code. Learn more about Release controls with GitLab.
| Feature name | Value |
|---|---|
| Approval rules for code review | Approval rules ensure that the right people review merge requests by specifying eligible approvers and the minimum number of approvals required for a merge request. |
| Merge Request Dependencies | Coordinate the order in which merge requests are merged within the same project and/or across different projects. |
| Push rules | Reject new code and commits that don't comply with company policy. |
| Required Merge Request Approvals | Guarantee quality and standards of your code by mandating a set number of necessary approvals and predefine a list of specific approvers. |
| Restrict push and merge access | Extend the base functionality of protected branches and choose which users can push or merge to a protected branch. |
| Protected Environments | Specify which person, group, or account is allowed to deploy to a given environment, allowing further protection and safety of sensitive environments. |
| Lock project membership to group | Group owners can prevent new members from being added to projects within a group. |
| Geolocation-aware DNS | Users using Geolocation-aware DNS can be transparently directed to the closest server available and access repository data faster. |
Ensure disaster recovery, high availability and load balancing of your self-managed deployment. Learn more about Self-managed reliability with GitLab.
| Feature name | Value |
|---|---|
| Disaster Recovery | Fail over in minutes to another data-center. |
| Maintenance mode | Maintenance mode allows systems administrators to perform maintenance operations, such as preparing for a scheduled failover, with minimal disruption to end users. |
| Fault-tolerant Git storage with Gitaly | Configure replicated Git storage with automatic failover, strong consistency, and read distribution for improved fault tolerance and performance. |
| Distributed cloning with GitLab Geo | Built for distributed teams, GitLab Geo helps to reduce time to clone and fetch large repos with GitLab Geo - thereby speeding up the user experience for all users regardless of location. |
| Support for Scaled Architectures | Scale GitLab services across multiple nodes to manage demand and provide redundancy. Determine the optimal architecture for your needs using reference architectures. |
| Container Registry geographic replication | Supports distributed teams by running multiple registry instances across several regions and syncing between data centers. |
| Database load balancing for PostgreSQL | Distribute read-only queries among multiple PostgreSQL database servers and reduce the load on the primary database to increase responsiveness. |
| Log forwarding | Forward your logs to a central system. |
| Feature name | Value |
|---|---|
| CI/CD for GitHub | Connect your projects hosted on GitHub and leverage the power of GitLab CI/CD pipelines to build, test, and deploy your applications easily. |
| Priority Support | Get the support you need. Our team of highly-skilled support engineers are available to help with all of your support needs. |
| Repository pull mirroring | Mirror a repository from a remote Git server to your local server, making it easy to keep local forks and replicas up to date. |
| Advanced Search | Provides faster, more advanced search across your entire GitLab instance. |
| Reorder Issues in Epic Tree | Reorder issues in an epic to indicate priority or intended order of implementation. |
| Built-in and custom project templates | When creating a new project, you can choose to kickstart your project from a predefined template that already has some working example code and CI preconfigured. In addition, you can define a custom project templates by assigning a group. Child projects of this group are available as templates when creating a new project. |
| Verified Committer | Verify that a push only contains commits by the same user performing the push. |
| Block secret file push | Block important or secret files from being accidentally pushed to a live repository with push rules. |
| Code Search | Provides code search across all repositories in the entire GitLab instance. |
| Next business day Support | Receive support within a single business day. |
| Group-level Wiki | A top-level Wiki for your group |
| Total Issue Weight per Issue Board List | View the total weight of issues in an issue board list, at the top of the list. |
| Epic Dynamic Dates | Use dynamic dates to do bottom-up planning and tracking of epics, taking into account the start and due dates its issues's milestones. |
| Track Description Changes | View the full history of description updates in issues, merge requests, and epics. |
| Browser Performance Testing | Easily detect performance regressions for web apps and pages prior to merging into master. Browser Performance Testing is included in Auto DevOps, providing automatic performance analytics of the root page with zero configuration. |
| Group Level Value Stream Analytics | GitLab provides a group dashboard that lets teams measure the time it takes to go from planning to monitoring. GitLab can provide this data because it has all the tools built-in: from the idea, to the CI, to code review, to deploy to production. |
| Epic Fixed Dates | Use fixed dates to do top-down planning of epics. |
| Service Level Agreement countdown timer | Track time for active incidents to ensure you meet your customer SLAs. |
| Cross-project jobs with artifact dependencies | Specify a job in your current project depends on the latest artifact produced by a job in another pipeline to easily set up cross-project pipelines that have artifact dependencies on each other. |
| Run pipelines in the parent project for MRs from forks | A member of the parent project with appropriate permissions can run pipelines from a forked MR using the parent project's pipeline configuration and runners. This adds another layer of security to verify that there's no malicious activity in the forked MR that could affect the parent project. |
| Load Performance Testing | Easily detect performance regressions for APIs prior to merging into master. |
| Group webhooks | Add webhooks by default to all projects in a group so you can ensure they are present everywhere. |
| Multi project pipeline visualization | When you configure GitLab CI/CD for your project, you can visualize the stages of your jobs on a pipeline graph. |
| Group-level permissions for Protected Environments | Enable large organizations to enforce separation of duties between developers and operators by setting up the appropriate configuration of the different roles. Once appropriately configured, developers are able to manage and deploy to lower-tier environments, such as development environments associated with the projects. However, developers are not allowed to deploy to higher-tier environments, such as the production environment. Operators, on the contrary, can deploy to production environments. |
| Escalation Policies | Automatically escalate and page on-call responders to safeguard against missed alerts. |
| On-call Schedule Management | Create schedules for responders to rotate on-call responsibilities. |
| Load balancer management for Blue/Green deployment | Blue/green deployment requires switching traffic from one set of servers to another. With GitLab today, you can manage of your load balancer via scripts, but it's not built in as a first-class citizen. |
| Pre-written deploy target mechanisms | GitLab Auto DevOps knows how to deploy to Kubernetes. Other vendors have built-in mechanisms to deploy to AWS VMs, Fargate, etc. |
| Smart card support | Authenticate into GitLab using a smart card with a compliant X.509 certificate. |
| Environment type | When defining an environment in .gitlab-ci.yml, in addition to the environment name, you can define the environment type, which can be one of: production, staging, testing, development, or other. |
| Associate Feature Flags with the issue(s) that is related to them | You can create a link from the issue that introduced the Feature Flag to the Feature Flag itself. That relationship is visible in the Feature Flag details. Feature Flags also support Markdown and can be referenced from any issue. |
| SAML SSO for Groups | Connect a group in GitLab to a SAML identity provider to manage authentication. |
| Live upgrade assistance | Schedule an upgrade time with GitLab. We’ll join a live screen share to help you through the process to ensure there aren't any surprises. |
| LDAP group sync filters | GitLab Premium gives more flexibility to synchronize with LDAP based on filters, meaning you can leverage LDAP attributes to map GitLab permissions. |
| LDAP group sync | GitLab Premium (Self-Managed) gives your administrators the ability to automatically sync groups and manage SSH-keys, permissions, and authentication, so you can focus on building your product, not configuring your tools. |
| Limit project size at a global, group, and project level | Ensure that disk space usage is under control. |
| Fault-tolerant PostgreSQL | Easily set up a PostgreSQL database cluster with automated failover |
| Kerberos user authentication | Authenticate users with Kerberos. |
| Create and remove admins based on an LDAP group | Use LDAP groups to create or remove admins from your GitLab instance. |
| Multiple LDAP / AD server support | Link multiple LDAP servers to GitLab for authentication and authorization |
| 24/7 uptime support | GitLab responds within 30 minutes when production is unavailable. |
| Variable replication factor | Allow configuration of a per-repository replication factor for repositories stored in the Gitaly Cluster. |
This page displays content from pricing_themes.yml and features.yml, changes can be made by proposing adjustments to that file.
