Why GitLab Premium?

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.

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.

Find bottlenecks in your code review process by understanding how long open merge requests have been in review.

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.

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.

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.

Visualize the history and current status of pipelines across projects and groups all in a single dashboard that can be customized for each user.

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.

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.

Visualize how pipelines across projects are linked together, including cross project dependencies.

Visualize cross-project environments, track change flow from development to production, track pipeline status and diagnose issues from a single dashboard.

Run GitOps-style deployments tightly integrated into GitLab

Define custom LICENSE, .gitignore, Dockerfile and .gitlab-ci.yml templates for your GitLab instance to make consistency easier.

Define custom LICENSE, .gitignore, Dockerfile and .gitlab-ci.yml templates for your GitLab instance to make consistency easier.

Restrict GitLab CI/CD deployment jobs using Kubernetes RBAC

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.

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.

Assign more than one person to an issue at a time.

Visualize multiple epics and milestones across time in a roadmap view.

Issue board lists that pull in issues in a given milestone

Plan and track features and work group level epics that collect issues together. Easily create and assign Issues directly from the Epic itself.

Assign scoped labels mutually exclusively when they have the same scope.

Promote an issue to epic to continue collaboration at a higher-level work abstraction.

Multiple Group Issue Boards, similar to Multiple Project Issue Boards

Explicitly mark issues as blocked and blocking and track their status. Blocked issues are visible in the issue card view for easy identification.

GitLab lets you manage issues using Agile practices by setting the weight of an issue.

Associate a board with a milestone, labels, an assignee, and a weight

Issue board lists that pull in issues assigned to a given user

See issue analytics at the group level.

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.

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.

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.

Automate the creation and management of iterations with iteration cadences at the group level, automatically roll issues from the previous iteration to the next, 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.

Organize a collection of related confidential issues into a confidential epic, allowing you to manage sensitive work more efficiently.

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.

Guarantee quality and standards of your code by mandating a set number of necessary approvals and predefine a list of specific approvers.

Reject new code and commits that don't comply with company policy.

Coordinate the order in which merge requests are merged within the same project and/or across different projects.

Extend the base functionality of protected branches and choose which users can push or merge to a protected branch.

Specify which person, group, or account is allowed to deploy to a given environment, allowing further protection and safety of sensitive environments.

Group owners can prevent new members from being added to projects within a group.

Users using Geolocation-aware DNS can be transparently directed to the closest server available and access repository data faster.

Fail over in minutes to another data-center.

Forward your logs to a central system.

Maintenance mode allows systems administrators to perform maintenance operations, such as preparing for a scheduled failover, with minimal disruption to end users.

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.

Configure replicated Git storage with automatic failover, strong consistency, and read distribution for improved fault tolerance and performance.

Scale GitLab services across multiple nodes to manage demand and provide redundancy. Determine the optimal architecture for your needs using reference architectures.

Supports distributed teams by running multiple registry instances across several regions and syncing between data centers.

Connect your projects hosted on GitHub and leverage the power of GitLab CI/CD pipelines to build, test, and deploy your applications easily.

Provides faster, more advanced search across your entire GitLab instance.

Mirror a repository to and from external sources. You can select which repository serves as the source, and modify which parts of the repository are copied. Branches, tags, and commits can be mirrored.

Get the support you need. Our team of highly-skilled support engineers are available to help with all of your support needs.

Provides code search across all repositories in the entire GitLab instance.

Receive support within a single business day.

A top-level Wiki for your group

Block important or secret files from being accidentally pushed to a live repository with push rules.

Reorder issues in an epic to indicate priority or intended order of implementation.

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.

Verify that a push only contains commits by the same user performing the push.

View the total weight of issues in an issue board list, at the top of the list.

When you configure GitLab CI/CD for your project, you can visualize the stages of your jobs on a pipeline graph.

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.

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.

Use fixed dates to do top-down planning of epics.

View the full history of description updates in issues, merge requests, and epics.

Restrict access at the group level to incoming traffic adhering to an IP address subnet, keeping your code secure.

Create schedules for responders to rotate on-call responsibilities.

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.

Use dynamic dates to do bottom-up planning and tracking of epics, taking into account the start and due dates its issues's milestones.

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.

Easily detect performance regressions for APIs prior to merging into master.

Easily set up a PostgreSQL database cluster with automated failover

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.

Track time for active incidents to ensure you meet your customer SLAs.

GitLab Auto DevOps knows how to deploy to Kubernetes. Other vendors have built-in mechanisms to deploy to AWS VMs, Fargate, etc.

Escalate and page responders to manually created Incidents

Add webhooks by default to all projects in a group so you can ensure they are present everywhere.

Administrators can define a password complexity policy for their GitLab instance

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.

Automatically escalate and page on-call responders to safeguard against missed alerts.

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.

Authenticate into GitLab using a smart card with a compliant X.509 certificate.

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.

Connect a group in GitLab to a SAML identity provider to manage authentication.

A Support Engineer will review and provide feedback on your upgrade plan to help ensure there aren't any surprises.

GitLab Premium gives more flexibility to synchronize with LDAP based on filters, meaning you can leverage LDAP attributes to map GitLab permissions.

Ensure that disk space usage is under control.

Authenticate users with Kerberos.

Use LDAP groups to create or remove admins from your GitLab instance.

Link multiple LDAP servers to GitLab for authentication and authorization

GitLab responds within 30 minutes when production is unavailable.

Allow configuration of a per-repository replication factor for repositories stored in the Gitaly Cluster.